Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Workaroung a Java7 AWT EDT/Robot bug: Validate whether AWT-EDT is alive ↵ | Sven Gothel | 2013-06-24 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | before certain robot ops. We have experienced that w/o utilizing AWT components, i.e. NEWT tests, the AWT-EDT 'sometimes' dies. Performing AWT robot's waitForIdle() in this situation causes a deadlock, since the call will never complete it's EventQueue.invokeAndWait() call. While analyzing this issue, we created a test tool whether the the AWT EDT is still alive. This test issues EventQueue.invokeLater( .. { flag=true; } ); and polls up until 2s for the result. Turns out that the sporadic AWT-EDT issues are solved by this test itself, i.e. it probably cause it to be reinstated. (?!) We have to observe this behavior. Another proof that quantum mechanic rules also apply in the macro cosmos :) | ||||
* | TestSWTAccessor03AWTGLn: Fix SWT deadlock on Java7/Windows: Must perform AWT ↵ | Sven Gothel | 2013-06-24 | 1 | -4/+8 |
| | | | | frame close on current thread .. | ||||
* | Fix NewtCanvasAWT focus traversal for Java7 (Take 2): Commit ↵ | Sven Gothel | 2013-06-23 | 1 | -2/+2 |
| | | | | | | | | | | | | 70bf3a4ec44504b86294a332255aaae8d2e86bf4 was not sufficient. Commit 70bf3a4ec44504b86294a332255aaae8d2e86bf4 did not work out on Windows. Solution now gathers the next or previous 'to be focused' component, using the FocusTraversalPolicy of the visible/focusable/enabled container. Then we simply request it's focus. Works w/ Java7 on Linux and Windows. | ||||
* | Bug 758: Fix scripts and ant build files to work w/ Java7 (default now) ↵ | Sven Gothel | 2013-06-21 | 1 | -0/+159 |
producing Java6 bytecode ; Apply JAR Manifest tags: Sealed, Permissions and Codebase |