Any comments from Adobe? I have not found any mention of this side affect while using navigation container nor in Flex component development presentation from Ely neither in help...
On 12/1/06, Sergey Kovalyov <[EMAIL PROTECTED]> wrote: > Hi All! > > I create the component using code behind technique (MXML inherited > from ActionScript class inherited from framework class, Box in my > case). The component contains children defined in MXML and has some > properties that have influence on children behavior. I call > invalidateProperties() in setters and then assign some cached values > to particular children properties in commitProperties(). Everything > works ok, until you place this component instance as a child of > navigation container, ViewStack in my case - createChildren() and > commitProperties() are called when ViewStack is created, though its > grandchildren are not created, so null pointer exception is thrown. > How to fix it? > > Sergey. >
