Re: DropShadow effect kills gfx responsiveness OS-wide

2018-11-04 Thread Tom Schindl
I've never seen and don't see it slowing down other applications (I'm on a MacBook Pro 13'') but I reported the DropShadow slow down and documented the solution [1]. Tom [1] https://openjfx-dev.openjdk.java.narkive.com/I8NIK0db/bad-dropshadow-performance On 04.11.18 20:22, Nir Lisker wrote: >> >

Re: JavaFX 11.0.1-ea+1 release

2018-11-04 Thread Johan Vos
It should. I have the following: javafx.version = 11.0.1-ea Are you using an SDK or maven artifacts? For which platform? - Johan On Sun, Nov 4, 2018 at 4:07 PM Michael Paus wrote: > My application is reporting the following values for the respective > properties: > > java.runtime.version: 11.0

Re: DropShadow effect kills gfx responsiveness OS-wide

2018-11-04 Thread Nir Lisker
> > I don't have access to the OpenJDK bug tracker so I can't file a bug > report for this > You can do it at https://bugreport.java.com/bugreport/ On Sun, Nov 4, 2018 at 9:18 PM Mike Hearn wrote: > I'm on macOS High Sierra with a very new and very high end MacBook Pro. > > I have a pretty basi

DropShadow effect kills gfx responsiveness OS-wide

2018-11-04 Thread Mike Hearn
I'm on macOS High Sierra with a very new and very high end MacBook Pro. I have a pretty basic GUI that uses translucency fairly aggressively. I added a DropShadow effect to some nodes, which looks great, but to my great surprise this one line of code kills the UI performance not of my app, but oth

Re: Running JavaFX-11 applications from within Eclipse fails

2018-11-04 Thread Tom Schindl
I think the more general problem is that they don‘t run on the module-path - in the m2e case this because the modules are transitive deps and those are not supported properly Tom Von meinem iPhone gesendet > Am 04.11.2018 um 16:17 schrieb José Pereda : > > I've just noticed that this issue ha

Re: Running JavaFX-11 applications from within Eclipse fails

2018-11-04 Thread José Pereda
I've just noticed that this issue happens not only with Maven but also with Gradle projects (Gradle + Eclipse 2018-09 + Windows with Oracle JDK 1.8), running gradle tasks from Eclipse. The same proposed workaround can be applied to the build file: run { systemProperty "java.library.path", "C

Re: JavaFX 11.0.1-ea+1 release

2018-11-04 Thread Michael Paus
My application is reporting the following values for the respective properties: java.runtime.version: 11.0.1+13 java.class.version: 55.0 java.version: 11.0.1 javafx.version: 11 Shouldn't "javafx.version" follow the same naming conventions as used by "java.version"? Am 02.11.18 um 09:59 schr