Yes, I ended up removing the "implements IFocusManagerComplexComponent" and
playing with focusEnabled and hasFocusableChildren properties in the
external and in internal components instead to obtain the intended
behaviour.
Thank for your help - maybe we could add some more detail in
the IFocusMana
The FocusManager doesn't want to know about internal focus targets, it
really only wants to know about the "component". For example, in
mx:TextInput, the internal focus target (stage.focus) is a TextField, but
from the developer's and FocusManager's perspective, the focus is on the
wrapping TextIn
See [1] for the method I was talking about...
https://github.com/apache/flex-sdk/blob/trunk/frameworks/projects/framework/src/mx/managers/FocusManager.as#L1336
2013/5/7 Cosma Colanicchia
> Thanks Alex.
>
> In my test I was never preventing it, but the tab focus movement to the
> next component
Thanks Alex.
In my test I was never preventing it, but the tab focus movement to the
next component was not worked (I expected to always move forward, at
least): for some reason, the internal focus target was not part of the
FocusManager tab loop candidates. I saw that, in this case, the
FocusMana
That interface is, in fact, only for the initial assignment of focus to the
component that wraps multiple targets. That wrapping component must then
manage tab focus on its own by handling the keyFocusChange event and calling
preventDefault on it when it wants to keep focus on one of the wrapped
c
Anyone know something about this interface ([1] on github)?
Its asdoc states "the IFocusManagerComplexComponent interface defines the
interface that components that can have more than one internal focus target
should implement in order to receive focus from the FocusManager" - so I
tried to implem
