diff options
| author | Sven Gothel <[email protected]> | 2013-11-17 04:55:33 +0100 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2013-11-17 04:55:33 +0100 |
| commit | 0be87f241c0f0b2f5881d9a602ce12378b8e453d (patch) | |
| tree | 801449f6fac0253b2fcd0982dc4dfcc435f2867f /src/nativewindow/native/NativewindowCommon.c | |
| parent | 88f6e0012b36ca69dedaadb4e403e2a424b20cbf (diff) | |
Fix Bug 879 - Threads deadlock in native keyboardfocus calls made form multiple threads; Fix Bug 892: Reduce Focus Hopping
Since we manage focus key traversal ourselves w/o requiring the AWT
component to have the focus[1],
we simply can drop requesting the focus for 'focus hopping' NEWT -> AWT -> NEWT[2].
Further more, 'MenuSelectionManager.defaultManager().clearSelectedPath()'
must be performed on AWT-EDT w/o blocking. Otherwise it may perform blocking tasks on AWT-EDT.
[1] Commit cb7118fc875b6722803e4b11d5681671962a8d3a
introduced function to query the next or previous 'to be focused' component:
AWTMisc.getNextFocus(..) .. etc.
[2] Focus hopping is also addressed in Bug 892
Diffstat (limited to 'src/nativewindow/native/NativewindowCommon.c')
0 files changed, 0 insertions, 0 deletions