diff options
| author | Sven Gothel <[email protected]> | 2010-10-29 04:00:03 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2010-10-29 04:00:03 +0200 |
| commit | fbb30f2e484b3fd0f98a32bed18c272528af7ba5 (patch) | |
| tree | f0cdf60f3f09c79da8d4be71694f6b66c29f6359 /jnlp-files/newt-awt.jnlp | |
| parent | 7e606ef39fa9d73cc7306cc0027989bc7704708d (diff) | |
Changed Lifecycle of NEWT Display/Screen (part 5)
--------------------------------------------------
Per default, creating a NEWT Display tries to reuse an existing one
to match the native platform display semantics closer.
The 'key' for a Display reuse is it's FQN.
The difference with the old 'reusage' is the removal of the TLS binding,
hence we use a global pool.
The user is able to 'override' this 'reuse' behavior with
'NewtFactory.createDisplay(String name, boolean reuse)'.
However, it is not recommended for AMD drivers (see above).
Screen's are always reused if possible.
The 'key' for a Screen reuse is it's FQN,
hence it's reuse depends on the Display reuse.
Diffstat (limited to 'jnlp-files/newt-awt.jnlp')
0 files changed, 0 insertions, 0 deletions