No advantages using non-modal popups, just a way to get what you want. I doubt we'll have time to provide more control over tabbing, especially in a way that sort of works against accessibility rules.
If you are using ModuleLoader today, you can probably pass the ModuleLoader to PopUpManager. There'll probably be some other stuff that needs to be fixed up, but that's what I'd try first. From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of aceoohay Sent: Tuesday, September 16, 2008 12:13 PM To: [email protected] Subject: [flexcoders] Re: Flex Enhancement, TabIndex Alex: I am not sure precisely how to do what you are suggesting. What I currently do is to create modules for each panel, and use moduleloader to add them to the stage. Are you suggesting that instead I use PopUpManager instead of moduleLoader? For my existing application it seems like a lot of work, and just investigating the ramifications regarding intermodule communications and so on may be challenging. Are there any benefits/drawbacks of using non modal popups vs module loader other than the tab loop? Paul --- In [email protected]<mailto:flexcoders%40yahoogroups.com>, Alex Harui <[EMAIL PROTECTED]> wrote: > > Why not just tile the application with non-modal popups? Wouldn't that get you what you want? > > From: [email protected]<mailto:flexcoders%40yahoogroups.com> [mailto:[email protected]<mailto:flexcoders%40yahoogroups.com>] On Behalf Of aceoohay > Sent: Tuesday, September 16, 2008 6:26 AM > To: [email protected]<mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Flex Enhancement, TabIndex > > > We write Client Server replacement applications using Flex. One > thing that is problematic is the handling of tabIndexing using Flex. > The problem; > > Flex use a Tab Loop for the entire application except popups. This > means if you are in panel A, reach the end using tab, it will move > to panel B, or elsewhere in your application. This is not the same > behavior that standard Client Server applications exhibit, and is > undesireable. Adding tab indexes makes the problem worse because if > you have multiple panels with overlapping tab indexes, it will > bounce back and forth between panels. > > A Solution; > > On any container object such as panel, canvas, tabnavigator, hbox, > vbox, etc. allow a new boolean attribute "tabLoopContainer" with > true and false as the allowable values. This would then cause a > local tab loop that would encompass only the objects within that > container. The default would be false, leaving the behavior as it > currently exists. Any object with a separate tab loop would only be > accessible by mouse click or programatically via set focus. > > I would like some feedback as to whether this seems reasonable, and > how I can get this in front of someone who could make it hapen. > > Paul >
