JFoenix | JavaFX Material Design Library

Since You are using PreparedStatement So you can use the addBatch() method, which internally stores all the queries and executes them combinedly rather executing one by one as you have done in the loop.

Further, it is good to use transactions here. You can use appropriate begin transaction command in the begining of the batch, then add all the relevant queries, here in your case UPDATE QUERIES, then lastly add commit command and then execute it. For any kind of error, all the updates will be rolled back and in case of successful updates, your queries will be executed at once and you don't need to use any loops for executing query one - by - one

Here is an article PreparedStatememt Batchs

Check this heading PreparedStatement Batch Updates

Hope you problem gets solved at the earliest.

It turns out that the package containing the kotlin file needs to be opened in a modular project in order for compiler plugin to generate the serializer. Adding opens in module-info.java fixed it

One possible solution would be to add a global CSS variable and change it depending on the JFXSlider current value. For example :

Here is an implementation of MessageBox, which extends the Alert class. If you want to add CSS style to beautify your window, you have to define MessageBox.setStyleSheet when loading your application (only once, it is not necessary to call it each time you want to display a MessageBox):

I figured out the answer finally.

it's in the module-info.java file

I just had to put this line of code there

The problem is here:

A JAR is just like a zip of classes, each class is the one that you can check with javap to see which JDK version they need by looking at the value of the "major version" field; see this.

If you want to ensure the classes are compiled to a specific Java version, you can use the release & target scalac options.

Like this:

There are significant issues with your use of threads in the code you posted, which I won't address here since they're not the topic of the question. However, the updateItem() method in a cell subclass is always called on the FX Application Thread, so any use of Platform.runLater() there is redundant at best.

Calling Platform.runLater() from the FX Application Thread will place the supplied Runnable into a queue to be run on the same thread at a later time (essentially when all pending things the FX Application Thread have been completed).

The updateItem() method can be called quite frequently, especially when the ListView is first displayed, and when the user is scrolling. There is (deliberately) no defined order in which specific cells have their updateItem() methods invoked, and with which parameters. Thus a cell may become empty or non-empty at essentially arbitrary times.

If the ListView implementation chooses to temporarily make a cell non-empty and then immediately make it empty, your updateItem() method will be called twice in rapid succession on the FX Application Thread. The first call will schedule a runnable to be run later that sets the graphic to the content of the FXML file. The second call will set the graphic to null. If the second call happens before the runnable posted to the queue is executed, the cell which is supposed to be empty will display the content, because the calls to setGraphic() happen in the wrong order.

Simply remove the Platform.runLater(...) from updateItem().

It is fixed now. Thanks for the help Slaw. I just have to change the module-info.java file. '''