diff options
| author | Sven Gothel <[email protected]> | 2012-12-02 03:59:13 +0100 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2012-12-02 03:59:13 +0100 |
| commit | f0f58e120817b57ed3fb70c238001579a68e4064 (patch) | |
| tree | 4e0fc6e85785ae19a14d9db9feffd7a5fe859ff2 /doc/jsr-231-changelog-1.1.0.html | |
| parent | b6f54d1714597ba2799160569b56139277db9e07 (diff) | |
Fix Bug 643: SWT 'display.asyncExec(Runnable runnable)' runnable not executed on Windows
Turns out that the NEWT Windows impl. didn't properly validated the client region @ WM_PAINT
and hence 'exhausted' the message pipeline, i.e. never reached an IDLE state.
The latter caused SWT to never reach a point where deferred asyncExec(..) Runnables
got processed.
Besides this SWT effect, this also caused a NEWT window on Windows to always repaint itself (?).
Diffstat (limited to 'doc/jsr-231-changelog-1.1.0.html')
0 files changed, 0 insertions, 0 deletions