summaryrefslogtreecommitdiffstats
path: root/src/junit
diff options
context:
space:
mode:
authorSven Gothel <[email protected]>2010-10-29 04:00:03 +0200
committerSven Gothel <[email protected]>2010-10-29 04:00:03 +0200
commitfbb30f2e484b3fd0f98a32bed18c272528af7ba5 (patch)
treef0cdf60f3f09c79da8d4be71694f6b66c29f6359 /src/junit
parent7e606ef39fa9d73cc7306cc0027989bc7704708d (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 'src/junit')
0 files changed, 0 insertions, 0 deletions