Hi Christophe,

 

I bet the bug is because you have the constructor doing initial value assignment.  Joe Berkovitz posted a very detailed account of how Flex will screw you up if you do this in your VOs because the constructor is actually called AFTER all the variables have been assigned.  Pete then gave an explanation as to why we do this, which I forget.  In any case, it sucks.  So in your VO objects make sure that you don’t assign default values to the properties in your constructor (or if you must put checks in the constructor to make sure the value hasn’t already been defined).

 

HTH,

Matt

 


From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Christoph Guse
Sent: Wednesday, June 08, 2005 10:36 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] complex Remote Objects

 

Hi Peter,

I still have the problem with my complex Remote Objects. Here is some code and other stuff:



Yahoo! Groups Links

Reply via email to