Read the jira ticket i referenced in my initial reply - tooltips and context 
menus create a window instance (=glass) and calls on glass have to be made on 
the javafx thread.


Von meinem iPhone gesendet

> Am 27.04.2014 um 05:14 schrieb Felix Bembrick <>:
> Why do tooltips and context menus matter? Is it because they will later be 
> instantiated on the wrong thread when they "pop up"?
>> On 27 Apr 2014, at 7:04, Tom Schindl <> wrote:
>> If you don't use Tooltips & context menus you can construct the scenegraph 
>> in any thread.
>> Tom
>> Von meinem iPhone gesendet
>>> Am 26.04.2014 um 21:48 schrieb Tony Anecito <>:
>>> Hi Tom this is also true for Swing and the EDT. I had heard years ago jre 8 
>>> was going to address this via 2 drawing threads and modularity but jigsaw 
>>> was delayed and not sure what happened to the 2 drawing thread idea. I 
>>> really wish we could instantiate windows in memory and when needed draw 
>>> them. The user experience and perception of java would be so much better 
>>> for the client side. If someone on the java client side knows how to do 
>>> this I would love to try it to verify it.
>>> Best Regards,
>>> Tony Anecito
>>>> On Saturday, April 26, 2014 11:39 AM, Mike Hearn <> wrote:
>>>> At e(fx)clipse we have an FXML to Java translator who removes all the
>>>> reflection overhead from FXML. It does not yet support all FXML features
>>>> but we are steadily improving it and with test cases we are able to fix
>>>> problems quite fast. Maybe this is an option for you?
>>> That would be very interesting to try, yes please! Where can I find it? My
>>> project is Java 8 based so that's no problem.

Reply via email to