Not able to add JFXTextField in Scene Builder 16.0.0 #1205
Comments
|
I got the same problem :( |
j-razeed
changed the title
|
Same problem here, if I try to open an FXML file I know is OK I get some errors about properties Now if I remove all those properties, I can open the file, but all the JFX fields are blank and and have errors. |
|
use the previous version of scenebuilder. |
|
Same here. Scene Builder 15.0.0 works. |
|
There is some kind of compatibility issue btw the boths. Sinply, you have to use previous version of scene builder and everything is working fine. Here is motivation for you about the javafx: https://www.youtube.com/watch?v=IyVFcr9WqMg&list=PLsX7b5vW6uGs6WLz2bbIVOD9qQyBaF_Ds |
|
i got the same problem and need help please `java.lang.reflect.InaccessibleObjectException: Unable to make boolean java.lang.reflect.AccessibleObject.setAccessible0(boolean) accessible: module java.base does not "opens java.lang.reflect" to unnamed module @56cca052 java.lang.NullPointerException: Cannot invoke "javafx.scene.Node.getLayoutBounds()" because "this.textNode" is null |
|
as ahmadbintariq4u wrote: Use Scenebuilder 15 instead: |
I'm cannot open JFXTextFields in Scenebuilder 15 either. The jdk I have installed is jdk 11.0.11. Is there an even earlier version I can download? I tried changing 15 to 14 in the url, but the download doesn't start. |
|
Do you use jfoenix 9.0.10 in scene builder? |
|
Where can I download the previous versions of Scene Builder from? I can't find it, please help!! |
The JFXComponents work for me in SB15. Maybe try a fresh environment? |
|
@CTaszus Hello , i have SB17 and jfoenix-9.0.10 and Jtextfield dont work for me as well , so i decide to use SB15 like you, but when i install SB15 i canno't open Scene builder even with " run as admin " , like there is nothing no error but it does not open. any solution ? |
Restart you pc |
|
@CTaszus I've already did it , nothing happened |
Start the scene builder from window panel not from your file.. if your .fxml file contains error then scene builder doesn't open. Or from the editor fix the problems from the file and then try to fire scene builder. |
This is the project i made in javafx. (Motivation for you) |
Do you added JFX to your SB libs? |
Nice project, looks great. What kind of Snackbar do you use? (Stacked Boxes top right to top bottom right) |
Bootstrap |
Problem: Prior to this commit, it was not possible to build or run the desktop app on Apple's M1 (macos aarch64) architecture. Solution: This commit makes all the changes necessary to successfully build and run on M1, but some of these changes require depending on snapshots and forks of certain dependencies, so this commit shouldn't be merged to master until those fixes are officially released. The changes made here include: 1. Upgrading from JavaFX 16 to JavaFX 17. JavaFX 17 was the first release to support aarch64 binaries, and so it's required. 2. Upgrading to a version of the openjfx-gradle-plugin that contains the fix at openjfx/javafx-gradle-plugin#113 to download the correct aarch64-classified JavaFX 17 jars. NOTE: at the time of this commit, the fix has not been released, so we are now depending on a locally-built SNAPSHOT resolved from `mavenLocal()`. 3. Upgrading to a version of the JFoenix library that includes a fix for the bug documented at sshahine/JFoenix#1187. At the time of this commit, this fix has only been publihed in the 'rationalityfrontline' fork of JFoenix, and so we've temporarily updated our dependency to point to that artifact. It appears that a new version of JFoenix is being developed that will contain this fix, but it hasn't shipped yet. Notes: - Gradle dependency verification metadata has been updated to reflect the changes mentioned above, but will need further updates to capture the Linux, Windows and MacOS Intel variants of the JavaFX 17 binaries. - Building and testing has been verified to work on JDKs 11 through 17; - Running the desktop app only works on JDKs 11 through 15, however, until sshahine/JFoenix#1205 is fixed. Right now, attempting to run on JDK 16+ will result in a 'Cannot invoke "javafx.scene.Node.getLayoutBounds()" because "this.textNode" is null' error. See the above mentioned issue for details. - It was necessary to bump the minimum supported source compatibility in the Gradle build from Java 10 to Java 11 in order to be able to consume the upgraded JFoenix artifact.
Problem: Prior to this commit, it was not possible to build or run the desktop app on Apple's M1 (macos aarch64) architecture. Solution: This commit makes all the changes necessary to successfully build and run on M1, but some of these changes require depending on snapshots and forks of certain dependencies, so this commit shouldn't be merged to master until those fixes are officially released. The changes made here include: 1. Upgrading from JavaFX 16 to JavaFX 17. JavaFX 17 was the first release to support aarch64 binaries, and so it's required. 2. Upgrading to a version of the openjfx-gradle-plugin that contains the fix at openjfx/javafx-gradle-plugin#113 to download the correct aarch64-classified JavaFX 17 jars. NOTE: at the time of this commit, the fix has not been released, so we are now depending on a locally-built SNAPSHOT resolved from `mavenLocal()`. 3. Upgrading to a version of the JFoenix library that includes a fix for the bug documented at sshahine/JFoenix#1187. At the time of this commit, this fix has only been publihed in the 'rationalityfrontline' fork of JFoenix, and so we've temporarily updated our dependency to point to that artifact. It appears that a new version of JFoenix is being developed that will contain this fix, but it hasn't shipped yet. Notes: - Gradle dependency verification metadata has been updated to reflect the changes mentioned above, but will need further updates to capture the Linux, Windows and MacOS Intel variants of the JavaFX 17 binaries. - Building and testing has been verified to work on JDKs 11 through 17; - Running the desktop app only works on JDKs 11 through 15, however, until sshahine/JFoenix#1205 is fixed. Right now, attempting to run on JDK 16+ will result in a 'Cannot invoke "javafx.scene.Node.getLayoutBounds()" because "this.textNode" is null' error. See the above mentioned issue for details. - It was necessary to bump the minimum supported source compatibility in the Gradle build from Java 10 to Java 11 in order to be able to consume the upgraded JFoenix artifact.
did anyone get solve for this ? |
|
Try launching your app with the following JVM Parameter: --add-opens=java.base/java.lang.reflect=ALL-UNNAMED |
|
A bummer the devs gave up on this project |
for the motivation |
Great fix!! Thanks! |
|
not opening scene builder and not opening scene builder from intellij idea |
That worked for me, thanks @CTaszus ! That was the only mention not related to SceneBuilder. I'm using TornadoFX for my project, and I do not even use SceneBuilder, but the issue still occur. I'm using jdk17 with jfoenix 9.0.10. |
|
JFoenix has an issue with javas module system. First thing to try when scenebuilder does not work is:
[JavaOptions] |
|
I used jfoenix 9.0.1 in the dependency on intellij and same exact version in scene builder and it worked for me. |
|
How can I get older versions of Scene Builder ? |
|
@mayurrpatell |
|
@ctoabidmaqbool1 These github releases do not have binaries in them. They again redirect to Gluon website. |
|
I am working with SceneBuilder 19.0.0 / Open JDK 17 /JFoenix 9.0.10 fine. Only 2 important things:
Notice: There should be linebreaks before the java-options.
EDIT: Of course, you have to add jfoenix to scenebuilder using the JAR/FXML Manager inside scenebuilder Hope this helps! |
I am using scene builder 16.0.0 and imported jfoenix 9.0.10 controls into the builder. when I try to add JFXTextField into AnchorPane/VBox getting below error in log and control is not getting added:
'Java Message:Cannot invoke "javafx.scene.Node.getLayoutBounds()" because "this.textNode" is null'
The text was updated successfully, but these errors were encountered: