JavaFX | JavaFX projects , mostly samples and examples

As correctly guessed in the comments, the deprecation warning comes from the javafx issue. There is an open issue about this:

In the current stable version, I get warning when I run this.

This is what I came up with, try it and see if it is what you want.

You may need to change some things to reach your final desired layout, but hopefully this addresses your immediate wrapping issue.

I think the BASELINE_CENTER alignment on the outer VBox was confusing things, but I changed a couple of other things, so it may have been something else.

From the Javadoc:

• Row/Column Sizing

  By default, rows and columns will be sized to fit their content; a column will be wide enough to accommodate the widest child, ...

The label in row 0 column 1 forces that column to be wider.

You probably want the label to be centered and span all 3 columns.

The FXML Manager plugin might be what you are looking for:

• go to File -> Settings -> Plugins -> Marketplace and search & install FXML Manager:

• after installing it, you may use the update controller option:

The Mina library 2.8.0 isn’t modular as far as I can tell, so it will probably be easier to access and use it if you have no module info.

Create a non modular app without a module info.java file. Place your application code and the Mina libraries and dependencies on the class path. Add JavaFX modules through command line switches as those need to be accessed via the module path, not the class path.

Refer to the relevant documentation on non-modular applications at openjfx.io getting started.

File->Settings->Tools->Emulator, and uncheck Launch in a tool window Then they will open in their own stand alone windows again.

The GraphicsContext begins with the default BlendMode, and all forms of drawImage() use the current mode. In contrast, PixelWriter methods replace values, ignoring the BlendMode.

The example below lets you experiment with the supported BlendMode values to see the effect. Related examples are shown here and here.

The long execution time comes from the fact that each child of a Parent registers a listener with the disabled and treeVisible properties of that Parent. The way JavaFX is currently implemented, these listeners are stored in an array (i.e. a list structure). Adding the listeners is relatively low cost because the new listener is simply inserted at the end of the array, with an occasional resize of the array. However, when you remove a child from its Parent and the listeners are removed, the array needs to be linearly searched so that the correct listener is found and removed. This happens for each removed child individually.

So, when you clear the children list of the Group you are triggering 1,000,000 linear searches for both properties, resulting in a total of 2,000,000 linear searches. And to make things worse, the listener to be removed is either--depending on the order the children are removed--always at the end of the array, in which case there's 2,000,000 worst case linear searches, or always at the start of the array, in which case there's 2,000,000 best case linear searches, but where each individual removal results in all remaining elements having to be shifted over by one.

There are at least two solutions/workarounds:

1. Don't display 1,000,000 nodes. If you can, try to only display nodes for the data that can actually be seen by the user. For example, the virtualized controls such as ListView and TableView only display about 1-20 cells at any given time.

2. Don't clear the children of the Group. Instead, just replace the old Group with a new Group. If needed, you can prepare the new Group in a background thread.

   Doing it that way, it took 3.5 seconds on my computer to create another Group with 1,000,000 children and then replace the old Group with the new Group. However, there was still a bit of a lag spike due to all the new nodes that needed to be rendered at once.

   If you don't need to populate the new Group then you don't even need a thread. In that case, the swap took about 0.27 seconds on my computer.

Using the hint from @jewelsea I was able to use a custom chain. I've done this from a "catcher" Pane which is added to the front of the StackPane. This then builds a chain using all the children, in reverse order, excluding itself.