Don’t make the Application class a controller. It’s a sin. There are other questions and answers which address this, but my search skills cannot find them at this time. The reason it is a sin is: You are only supposed to have one Application instance, and, by default, the loader will make a new instance, … Read more
When you use getClass().getResource(…) you are loading a resource, not specifying a path to a file. In the case where the class loader loads classes from the file system, these essentially equate to the same thing, and it does actually work (though even then there’s no technical reason it has to). When the class loader … Read more
Why your code does not work The loader creates a new AnchorPane, but you never add the new pane to a parent in the scene graph. Quick Fix Instead of: content = (AnchorPane) FXMLLoader.load(“vista2.fxml”); Write: content.getChildren().setAll(FXMLLoader.load(“vista2.fxml”)); Replacing the content children with your new vista. The content itself remains in the scene graph, so when you … Read more
Generic Resource Lookup Information This answer discusses FXML location lookup, which is really just a subset of the generic resource lookup task in Java. The resource location is passed by the calling program as input to the FXMLLoader, so the resource lookup itself is part of your calling application code and not the FXMLLoader. For … Read more
JavaFX is part of OpenJDK The JavaFX project itself is open source and is part of the OpenJDK project. However, the OpenJDK project includes many projects, including incubating projects and other projects, such as OpenJFX, whose source and implementation are not shipped as part of some JDK/JRE distributions (e.g. Oracle JDK 11+ implementations and many … Read more
In a few words: The constructor is called first, then any @FXML annotated fields are populated, then initialize() is called. This means the constructor does not have access to @FXML fields referring to components defined in the .fxml file, while initialize() does have access to them. Quoting from the Introduction to FXML: […] the controller … Read more
TL;DR: You need to make sure javafx.media is resolved as a module from the module-path. You can do this by either: Including it in the VM arguments: –add-modules javafx.controls,javafx.media Or making your own code modular, adding an appropriate requires javafx.media; directive to your module descriptor, and using –module to launch your application. If you’re not … Read more
The way it works now is, you convert your program to a module, then “link” it to all the other modules it requires. The result of this linking process is what’s known as an image. An image is actually a file tree, which includes a bin directory with one or more ready-to-run executables. This tree … Read more
The default behavior of the FXMLLoader is to create a new instance of the controller class and use that instance as the controller. Specifically, the FXMLLoader does something like: Read the root FXML element. If the root FXML element has a fx:controller attribute, then If a controller already exists, throw an exception, otherwise create an … Read more
Use Platform.runLater(…) for quick and simple operations and Task for complex and big operations . Use case for Platform.runLater(…) Use case for Task: Task Example in Ensemble App Example: Why Can’t we use Platform.runLater(…) for long calculations (Taken from below reference). Problem: Background thread which just counts from 0 to 1 million and update progress … Read more