Kevin Rushforth"
An: "marcel Austenfeld"
Cc: openjfx-dev@openjdk.java.net
Betreff: Re: Aw: Re: "Toolkit already initialized" error with OpenJDK 11
I think I see what caused this. In FX 8 we called FXCanvas::initFx from
the constructor of every FXCanvas. It then cal
et
*Betreff:* Re: Aw: Re: "Toolkit already initialized" error with OpenJDK 11
I think I see what caused this. In FX 8 we called FXCanvas::initFx from
the constructor of every FXCanvas. It then called an internal startup
method, PlatformImpl::startup, that permits calling it when the
pse plugin (which was definitely
> the case with Java 8!).
>
> Maybee this has something to do with the new module system of Java >=9?
>
>
>
>
> Gesendet: Mittwoch, 26. September 2018 um 14:09 Uhr
> Von: "Kevin Rushforth"
> An: "marcel Austenfeld&quo
.home$/lib/javafx-swt.jar,
This worked for years and even now (with the exception of the classloader bug
analyzed by Kevin)
Gesendet: Freitag, 05. Oktober 2018 um 09:27 Uhr
Von: "Tom Schindl"
An: open
Betreff: Re: Aw: Re: Re: "Toolkit already initialized" error with Open
Gesendet:* Donnerstag, 04. Oktober 2018 um 16:44 Uhr
> *Von:* "Tom Schindl"
> *An:* openjfx-dev@openjdk.java.net
> *Betreff:* Re: Aw: Re: "Toolkit already initialized" error with OpenJDK 11
> Hi,
>
> Just to make sure I understand. Do you say that other OSGi-
I created a bug report on https://bugs.java.com/
Bug ID is: 9057517
Gesendet: Donnerstag, 04. Oktober 2018 um 16:13 Uhr
Von: "Kevin Rushforth"
An: "marcel Austenfeld"
Cc: openjfx-dev@openjdk.java.net
Betreff: Re: Aw: Re: "Toolkit already initialized" error
Kevin Rushforth"
An: "marcel Austenfeld"
Cc: openjfx-dev@openjdk.java.net
Betreff: Re: Aw: Re: "Toolkit already initialized" error with OpenJDK 11
I think I see what caused this. In FX 8 we called FXCanvas::initFx from
the constructor of every FXCanvas. It then cal
;
> Maybee this has something to do with the new module system of Java >=9?
>
>
>
>
> Gesendet: Mittwoch, 26. September 2018 um 14:09 Uhr
> Von: "Kevin Rushforth"
> An: "marcel Austenfeld" , openjfx-dev@openjdk.java.net
> Betreff: Re: &qu
nitely the case with Java 8!).
>> Maybee this has something to do with the new module system of Java >=9?
>>
>> Gesendet: Mittwoch, 26. September 2018 um 14:09 Uhr
>> Von: "Kevin Rushforth"
>> An: "marcel Austenfeld" , openjfx-dev@ope
g to do with the new module system of Java >=9?
Gesendet: Mittwoch, 26. September 2018 um 14:09 Uhr
Von: "Kevin Rushforth"
An: "marcel Austenfeld" , openjfx-dev@openjdk.java.net
Betreff: Re: "Toolkit already initialized" error with OpenJDK 11
I'm&#x
ugin (which was definitely the
case with Java 8!).
Maybee this has something to do with the new module system of Java >=9?
Gesendet: Mittwoch, 26. September 2018 um 14:09 Uhr
Von: "Kevin Rushforth"
An: "marcel Austenfeld" , openjfx-dev@openjdk.java.net
Betreff: R
Hello Kevin,
I already use Platform.setImplicitExit(false) at startup so this can't be the
problem. All SWT FXCanvas are not closed (at least at startup).
Could it be that the initialisation of the SWT FXCanvas is different and could
cause the problem.
At the moment I use as java arguments:
I'm' not aware of anything that intentionally changed between FX in JDK
8 and FX 11, but my guess is that the FX runtime is being shutdown after
your first FXCanvas exits. Try making the following call (only needed
one time) before creating your first FXCanvas:
Platform.setImplicitExit(fal
First of all congratulation to the new release and thank you for the hard work
on JavaFX.
I have a problem with JavaFX which in my case is embedded in a Rich Client
Platform of Eclipse.
I integrated several SWT FXCanvas (some with SwingNode panels as a SWT_AWT
replacement) into my app.
T
17 matches
Mail list logo
