Re: Is it possible to disable JavaFX shutdown hook?

Hi Pavel Not sure if this will help in your situation but you can try using "primaryStage.setOnCloseRequest" where you can run any cleanup code needed. If you want to cancel the close request completely then just consume the WindowEvent and then later issue Platform.exit() when ready. Reg

Re: RFR: 8289115: Touch events is not dispatched after upgrade to JAVAFX17+

Thank you Michael, Jose, Florian, and Markus In my mind the "Too many touch points reported" exception fix (#394) appears to not be the correct fix for that issue and is what caused this regression. There seems to be two possible paths forward, either revert #394 or integrate this. In bot

Touch events are not dispatched after upgrade to JavaFX 17

Hi All Can JDK-8289115 (Touch events are not dispatched after upgrade to JavaFX 17) please get some attention again for the next release. Thanks, regards Jurgen

Re: Integrated: 8324658: Allow animation play/start/stop/pause methods to be called on any thread

A big THANK YOU to everybody that was part of this process. It's very much appreciated ! Regards Jurgen On Tue, 30 Jan 2024 11:27:44 +0200, Nir Lisker wrote: On Fri, 26 Jan 2024 23:59:50 GMT, Nir Lisker wrote: Added a utility method to run code on the FX thread if it's not already, and

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced USE CASE

t;>adding multithread support. - Nir On Mon, Jan 22, 2024, 12:59 Jurgen Doll wrote: Here's an example as requested by Nir: public class FxTimeLineTest extends Application { private BorderPane bp = new BorderPane( new Label("Loading") ); public static void main(

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced USE CASE

wrote: On 23/01/2024 16:56, Jurgen Doll wrote: Hi John and others, I don't think we are entirely on the same page, so here's the objective. The Goal: To determine if the FX animation thread and a SINGLE other thread can access Animation in a >>safe manner wrt play, stop, a

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced USE CASE

Hi John and others, I don't think we are entirely on the same page, so here's the objective. The Goal: To determine if the FX animation thread and a SINGLE other thread can access Animation in a safe manner wrt play, stop, and resume. Non Goal: Multi-threaded access of Animation play, stop,

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced

Hi Michael starting an animation on a background thread would only be safe if the object graph affected by the animation is not accessed on the background thread after calling the play() method. Any access may potentially corrupt internal state. Agreed. Actually we should drive this further an

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced USE CASE

I've been delving into the usage of `aborted` and `inTimePulse` as mentioned by John and gleaned the following: 1. stop makes a best effort to abort the 'animation' if it is in the process of execution. 2. `aborted` and `inTimePulse` are reset with every pulse. As to the options that John m

HEADS-UP: Threading restriction for Animation play, pause, stop now enforced USE CASE

Here's an example as requested by Nir: public class FxTimeLineTest extends Application { private BorderPane bp = new BorderPane( new Label("Loading") ); public static void main( String[] args ) { launch( FxTimeLineTest.class, args ); } @Override public void

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced

Hi Michael It seems we are misunderstanding one another. Firstly I agree that the animation code itself must and always has run only on the FX thread. So for example in the following code: new KeyFrame( Duration.seconds(2.5), event -> { int maxMemory = ; int usedMemory

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced

Hi Kevin I was hoping that others would way in on this fix (PR #1167), but now that we're in RDP1 with no other input coming in I decided to looked into this matter again and have found that this is not the correct solution for the following two reasons: 1. The current solution doesn't ac

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced

Thanks for the heads-up Kevin, I gave it a spin and found that generally because I use Task to load my fxml views I had problems. Some of these I could resolve by wrapping the offending line with runlater in the fxml initialise method. This reminded me though of the days when Tooltips had

Re: HEADS-UP: Threading restriction for Animation play, pause, stop now enforced

Thanks for the heads-up Kevin, I gave it a spin and found that generally because I use Task to load my fxml views I had problems. Some of these I could resolve by wrapping the offending line with runlater in the fxml initialise method. This reminded me though of the days when Tooltips had to be

Comment for JDK-8289115 - Touch events are not dispatched after upgrade to FX17

Hi Could someone please add the following lines as comment to the issue JDK-8289115 (https://bugs.openjdk.org/browse/JDK-8289115) Thank you very much. @Praveen please have another look at Capture.pptx and you'll see that *ONLY* MouseEvents are being fired and NO TouchEvents. The test cas

Comment for JDK-8289115 - Touch events are not dispatched after upgrade to FX17

Hi Could someone please add the following lines as comment to the issue JDK-8289115 (https://bugs.openjdk.org/browse/JDK-8289115) Thank you very much. @Praveen please have another look at Capture.pptx and you'll see that only MouseEvents are being fired and NO TouchEvents. The test case