Hello Leonardo,
I removed different forms step by step so that the forms I removed first
stayed in the app. Then the NetConnection Debugger worked well. So I
couldn't specify a form which detains the Debugger doing its job.
I also removed a big form with datagrid and cell renderer within
comboboxes and checkboxes and filled the "hole" with 5 blank forms.
I got the impression that it has something to do with the amount and
complexity of controls. If I remove the heavy form with datagrid and the
cell renderer the NetConnection Debugger works fine. This form is the
first I developed and additional followed. If I let the heavy form
inside the app and want the debugger to work, I have to remove about 5
forms with less controls and eventhandlers.
My version of Flash MX Professional is 7.2 and the lizensing version is
4.0.0.32
I took a look ad macromedias home and found an update to 7.2 which I own.
Macromedia Flash Remoting for Flash MX 2004 ActionScript 2.0
(flashremoting_comp_as20-win-de.exe) show the file-version 5.0.0.0 and
on macromedias home it is dated as June 7, 2004
Since the first use of NetconnectionDebugger I found out that I often
have to restart it. Something I could live with. The Software Licensing
for Studio MX 2004 Pro allows to install it on two machines (work and
home). So I did it and had the same problems.
To take a look at Peformance of my System. I have an AMD XP 2200 with
512 MB RAM, no errors about memory are given and the system runs stable.
I'll make another test in the evening. Testing it on a machine with 1GB
of Memory.
Best Regards,
Carsten W.
[quoted text, click to view] Leonardo Braga wrote:
> Hello carstenw,
>
> Try to check if the forms that you remove that solves the problem, have
> any code that intervenes with the FlashComm objetcs.
>
> Check if the most new updates are applied to the FCS AND to the Flash
> Environment.
>
> Other test is: remove some forms and include the double empty forms (or
> even more) and make a test. If the problem occur in this case, check if
> you have enought memory or another thing that could cause performance
> problems.
>
> I have never seen a performance problem that unable a developer to use
> the NetDebugger before.
> If you identiy the problem, let me know - I'm really curious.
>
> I hope it helps. Good luck.
> Leonardo Braga Nogueira
> Brazil.
>
> carstenw wrote:
>
>> Hello,
>>
>> I developed a formular based MX 2004 Professional application (product
>> calculator) with at the moment 10 forms, 5 DataSets an a lot of
>> controls on each page.
>>
>> Up to yesterday the NetConnection Debugger worked with my app. Now
>> it'll only work if I remove some Formulars. But so I can't continue my
>> working.
>>
>> Any suggestions ?
>>
>> Thanks.
>> carstenw
>