arrrggg .. head on desktop edited the arg-file of base project, not
that of the controls ... now it's time to call it a day, tsssee
thanks for your help! and have a nice evening everybody :)
Zitat von Tom Schindl :
i run them with
okay, found something in the gradle tasks which point into direction
of some success: it sets the stubtoolkit in a vm arg:
-Djavafx.toolkit=test.com.sun.javafx.pgstub.StubToolkit
which does indeed work inside Eclipse if I add it to the runtime
config of the test. Next step would be to
i run them with
-Djava.library.path=/Users/tomschindl/OpenJFX/openjdk-jfx/build/sdk/lib
-Djavafx.toolkit=test.com.sun.javafx.pgstub.StubToolkit
Tom
On 18.11.18 17:00, Nir Lisker wrote:
> I don't recall seeing this problem. Just to be sure, did you circumvent the
> compilation error in Dialog's
Zitat von Nir Lisker :
I don't recall seeing this problem. Just to be sure, did you circumvent the
compilation error in Dialog's lambda?
yes, I did - not seeing any compile errors, nothing red but just the
app thread doesn't seem to be fired up.
On Sun, Nov 18, 2018 at 5:42 PM wrote:
I don't recall seeing this problem. Just to be sure, did you circumvent the
compilation error in Dialog's lambda?
On Sun, Nov 18, 2018 at 5:42 PM wrote:
>
> With the step-by-step debugging help provided by nlisker over at
> javafxports (https://github.com/javafxports/openjdk-jfx/issues/187 -
>
With the step-by-step debugging help provided by nlisker over at
javafxports (https://github.com/javafxports/openjdk-jfx/issues/187 -
which cleaned up some inherent misconception on my part, thanks!) I
managed to run tests in base and graphics from inside Eclipse (right
click and run
