diff options
author | Sven Gothel <[email protected]> | 2012-12-22 05:40:36 +0100 |
---|---|---|
committer | Sven Gothel <[email protected]> | 2012-12-22 05:40:36 +0100 |
commit | 1ae0737f34143a5ed655bd9c4d5fe9b0437c7774 (patch) | |
tree | e3e2b4b2ac8af451782fee034e63473ceddd4e6d /doc/Implementation | |
parent | 99b79930f6b25bf8b8bc29dc9a36b33717bdbf0e (diff) |
Fix Bug 642 TestJSplitPaneMixHwLw01AWT (AWT-GLCanvas); Robustness GLContext/GLDrawable
- Fix Bug 642 TestJSplitPaneMixHwLw01AWT
On Windows platform when mixing hw/lw JSplitPanel,
the GLCanvas is removed and added when splitter is moved.
The lack of robustness (see below) lead to an exception.
Note: Only w/ GLJPanel (no hw/lw mixing) the splitter can be moved
in both direction. Only here it is guaranteed that the GL component
will survive the action.
- Fix AWT-GLCanvas EDT Runnable: swapBuffer().. / display(..)
- Check drawable.isRealized() within the lock on the performing thread.
This is not possible before issuing the EDT Runnable action
since we cannot hold the lock beforehand.
- Robustness GLDrawableImpl
- boolean realized -> volatile boolean realized
- remove 'synchronized' on isRealized() and setRealized(..)
- Use dbl-checked locking on 'realized' test for swapBuffers() and setRealized(..)
- Robustness GLContextImpl
- Catch createImpl(..) exception and properly return CONTEXT_NOT_CURRENT
Diffstat (limited to 'doc/Implementation')
0 files changed, 0 insertions, 0 deletions