I have a mx2004Pro form application I'm working on and the following bizarre behavior is happening:
- switch back and forth between screens, working on this and that, and over time the "visible" property for various forms revert to "true" at run-time although their property value in the design environment is still set correctly to "false". That is, when my app starts, randomly some forms start defaulting to visible. I've taken ALL code out of the project to verify this is not something with my code. It's not. Is the form application support in MX2004 just that buggy? If so, wtf????? - also, why does ONLY absolute pathing work for setting values/properties on forms in a form application? In the code layer for my main form, the top level form, I have code that is attached to a menu that has the requisite setVisible(true/false) code to show and hide various screens(forms) based on menu selections by the user. But, I've verified that ONLY absolute pathing works e.g. _root.frmMain.frmDesktop.setVisible(false); //frmMain is the top level form with a child of frmDesktop But, Since the code exists in a "code" layer for frmMain, why doesn't this work: This.frmDesktop or even, this._parent.frmDesktop when referenced from within a contained component's function handler? Thx!! Chris _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
