After playing around a bit more I am leaning towards the fact that the mx and fl might be the same, and the 2025 error is caused by something I am doing (or not).
If the panel has focus I can tab around it, and type, but as soon as I click a mouse anywhere in the application it dies in SystemManager on a getChildIndex fired by the mouseDownHandler. Any help is appreciated. Paul --- In flexcoders@yahoogroups.com, "aceoohay" <pa...@...> wrote: > > In reading the page; > > http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/fl/managers/FocusManager.html > > It seems like just the right tool to handle a major deficiency in Flex. > Basically the inability to create tab loops for containers. > > I use a somewhat modified version of the SuperPanel component which is an > extension of the panel component for all of the data entry forms in my > application. I envisioned creating a FocusManager in the SuperPanel, and > viola I would have a custom tab loop for each of my data entry screens. > > Unfortunately, it isn't that simple (it seldom is). I added a private > variable to the component of the type FocusManager. Flex of course wants to > add mx.managers.FocusManager, and we probably want fl.managers.FocusManager > the flash version, since the mx version generates 2025 RT errors anytime you > click on any object in the container that is assigned to a separate/custom > focusmanager. > > The full error is; > > Error #2025: The supplied DisplayObject must be a child of the caller. > > So has anyone else tried to create a flex component with a separate tab loop, > if so how did you make it work? > > Has anyone worked with the fl.managers.FocusManager component? Is it the same > as the mx.managers.FocusManager? Is it possible to get either one to do what > I want? Which is to encapsulate a tab loop with in a container. How? > > Paul >
