diff options
author | Sven Gothel <[email protected]> | 2010-11-16 10:36:28 +0100 |
---|---|---|
committer | Sven Gothel <[email protected]> | 2010-11-16 10:36:28 +0100 |
commit | db4d7d198cc826bba871fea39461c3c8a2a3b1c6 (patch) | |
tree | 723c5d4958df50a2ca7443171873e6f854c745a5 /jnlp-files | |
parent | b3420aeb07f9bef1e4fe5f436524d0b3d66cfaa2 (diff) |
NEWT Lifecycle remodel: Window destroy() !
NEWT's removed:
Window: destoy(boolean unrecoverable)
Display/Screen: get/set DestroyWhenUnused(boolean)
We behave as follows:
- Window.destroy() always decr Screen's reference counter,
which issues destruction when reached zero.
Then Screen does the same for Display ..
- Window.destroy() keeps alive all references,
hence it can be always recreated via setVisible(true).
- Window.destroy() ensures Display's EDT is stopped
if display is destroyed.
- Window.invalidate() actually removes all Object reference,
hence it cannot be recreated or used after it.
This method exist to support a way to cleanup memory, GC.
All test passed on Linux/X11 and Windows
Diffstat (limited to 'jnlp-files')
0 files changed, 0 insertions, 0 deletions