+1 for FX Thread.
-Thor
On Oct 4, 2013, at 12:53 PM, Richard Bair wrote:
> I always disliked FX Application thread, which is why I don't use it. The
> FXAT or FAT are acronyms we ought to avoid. EDT was great for Swing because
> it was super short, but we don't want to reuse EDT because that wou
I always disliked FX Application thread, which is why I don't use it. The FXAT
or FAT are acronyms we ought to avoid. EDT was great for Swing because it was
super short, but we don't want to reuse EDT because that would be confusing.
Personally I tend to use FX Thread because it is clear that th
We are BAD. It should really be "FX Application Thread" but the "GUI",
"event" nature of the thread is critical to what it is. That's why the
terms keep getting added.
Steve
On 04/10/2013 3:36 PM, Richard Bair wrote:
Ya, "event thread", "fx thread", "ui thread", "app thread", "FX Application
Ya, "event thread", "fx thread", "ui thread", "app thread", "FX Application
thread" --- they're all the same thing. It would be better if we settled on one
name.
Richard
On Oct 4, 2013, at 12:00 PM, steve.x.northo...@oracle.com wrote:
> It's the JavaFX Application Thread. We tend to use the t
It's the JavaFX Application Thread. We tend to use the term "event
thread" and "UI thread" to indicate that the thread is a distinguished
UI thread that processes operating system events by running an event loop.
Steve
On 04/10/2013 2:45 PM, John Smith wrote:
IllegalStateException("This oper
> IllegalStateException("This operation is permitted on the event thread only")
What is the event thread?
Current warnings about thread rule violations appear to be something like below
(from:
http://stackoverflow.com/questions/12182592/javafx-2-x-swing-not-on-fx-application-thread):
Except
