Bump?
2013/9/23 Cosma Colanicchia
> Opened the issue FLEX-33772 and attached a sample app and a patch.
>
> I've only been able to test it as a monkey patch in some sample apps and
> in the application where the problem was first noticed, I hope that someone
> could be able to review it.
>
> Tha
Opened the issue FLEX-33772 and attached a sample app and a patch.
I've only been able to test it as a monkey patch in some sample apps and in
the application where the problem was first noticed, I hope that someone
could be able to review it.
Thanks!
2013/9/20 Alex Harui
> You can follow
You can follow the monkey patching method for trying out new versions of
FocusManager.
FWIW, I think the last time someone had this problem, I suggested that
they use a Checkbox instead of RadioButton and use the RadioButtonSkin on
the Checkbox. Then have their own logic that unselects the other
I like "text pictures" :) but here is a snippet:
http://pastebin.com/sYeHQKFQ
I'd like to attemp a fix, must find the time to setup my environment
(cannot rebuild the whole framework for each try).
2013/9/20 Alex Harui
> I didn't see that in your 'text picture', but yes you are correct, the
>
I didn't see that in your 'text picture', but yes you are correct, the
FocusManager does not handle that condition. You're welcome to try to fix
it.
-Alex
On 9/20/13 8:05 AM, "Cosma Colanicchia" wrote:
>Absolutely, but if there are other controls "interleaved" with the radio
>buttons of the sa
This is the simplest way to reproduce it:
[X] choice A
[text input (maybe enabled when choice A is selected, to enter further
info)]
[ ] choice B
[other controls]
In this situation, when tab goes like this: choice A -> text input ->
choice A -> (no way to reach other controls).
This is be
Absolutely, but if there are other controls "interleaved" with the radio
buttons of the same group, when the focus leave this interleaved components
the focus is "moved back" to the selected button... even if this is
"before" in the computed tab loop, actually creating a closed tab loop that
is imp
The default behavior on Windows is/was that you tab to a group of radio
buttons which will focus the selected one or the first one if none are
selected, then use arrow keys to move between them. Another tab moves you
to the next/previous control or group.
The Flex FocusManager attempts to replica
Hi list, maybe I found an issue with keyobard focus manager.
I have a situation like this (hope you get the pic):
[previous controls]
[radio A] [radio B]
[radio A1] [radio B1] [text input]
[radio A2] [radio B2]
[next
