I'm testing out some changes to FocusManager that might solve this problem. If you attach a simple test case to the JIRA issue then we can see if it works or not, and if it does, you can monkey-patch this FocusManager into your app or upgrade to 4.11 (assuming I get it in before it gets released).
On 10/15/13 2:07 AM, "mark goldin" <[email protected]> wrote: >Where would I start from? > > >On Mon, Oct 14, 2013 at 4:59 PM, Alex Harui <[email protected]> wrote: > >> You will probably need to modify FocusManager to do that. >> >> On 10/14/13 1:12 PM, "mark goldin" <[email protected]> wrote: >> >> >My problem is what have discussed in another thread about >> >radiobuttongroups. If I have two of these then the second one will not >>get >> >a focus.I am trying to come up with a workaround that would force a >>focus >> >placed on the second radiobuttongroup. >> > >> > >> >On Mon, Oct 14, 2013 at 3:02 PM, Alex Harui <[email protected]> wrote: >> > >> >> That's the only way. To actually get focus to change you can call >> >> focusManager.getnNextFocusManagerComponent().setFocus(). You can >>also >> >> fake a KEY_FOCUS_CHANGE event and not bother calling FocusManager. >> >> >> >> On 10/14/13 12:52 PM, "mark goldin" <[email protected]> wrote: >> >> >> >> >What are ways of finding what the next focus target is going to be? >> >> >So far, I know about focusManager.getNextFocusManagerComponent(). Is >> >>there >> >> >more? >> >> > >> >> >Thanks >> >> >> >> >> >>
