3

I've looked at other issues similar. What I can tell you is: This program worked a week ago. I haven't changed scenebuilder. A new JRE, as I recall, was downloaded and it is 1.8.0_101-b13. This is on Linux 64bit. In the very same program Lambda notifications still work. I did just upgrade scenebuilder to 8.2.0 from 8.0.0. But I am not actively working on a fxml file.

I believe the only change was a recent upgrade on the JDK/JRE. The default computer is the same release as the default runtime.

Walt Corey
  • 718
  • 7
  • 12

2 Answers2

5

I could have sworn another issue on this was resolved by changing the version of scenebuilder...which did not, on the surface, make sense. Although there was a new SceneBuilder out there from Gluon.

This problem is fixed by upgrading ControlsFX to version 8.40.11, up from 8.40.10.

Walt Corey
  • 718
  • 7
  • 12
0

This issue was resolved on 13 April 2016 for ControlsFX 8.40.x, but ControlsFX 8.20.x still has this problem (8.20.9 was released on 2 June 2015).

To fix the problem:

  • use ControlsFX 8.40.x or higher, or
  • use a Java version that has a two-digit minor version number (both 8u20 and 8u40 will be fine).

What is the bug? Well, ControlsFX is comparing the minor versions of Java and ControlsFX as String values: "40" is considered higher than "101" because the first character "4" is higher than "1" (source). The implemented fix parses the version strings as Integer values.

giraffe.guru
  • 480
  • 8
  • 21