As of today, Newt's DEFAULT threading model to handle native events is the event DISPATCH thread (EDT) model.

Newt's EDT impl. creates one EDT per NEWT Display, as the Display is a unique abstraction of a graphics device connection SERVING all of it's Screens and Windows.

EDT is being used to

• dispatch native Screen and Window events
• lifecycle Screen and Window functionality
• create / destroy
• reparenting
• native repaint CALLS (if no AnimatorControl is attached and animating)
• ..

EDT is not

• blocking your rendering with event dispatching,
• needed for pipelining your rendering commands,
• hence not HINDERING your high performance rendering in it's own thread, eg an Animator

Using EDT is not mandatory, and you can turn it off in the NewtFactory, and deal with the event dispatch manually.

As of today, Newt's default threading model to handle native events is the event dispatch thread (EDT) model.

Newt's EDT impl. creates one EDT per NEWT Display, as the Display is a unique abstraction of a graphics device connection serving all of it's Screens and Windows.

EDT is being used to

EDT is not

Using EDT is not mandatory, and you can turn it off in the NewtFactory, and deal with the event dispatch manually.