Re: RFR: 8341670: [Text, TextFlow] Public API for Text Layout Info [v5]

On Wed, 9 Oct 2024 22:41:29 GMT, Andy Goryachev wrote: >> The RichTextArea control >> ([JDK-8301121](https://bugs.openjdk.org/browse/JDK-8301121)), or any custom >> control that needs non-trivial navigation within complex or wrapped text >> needs a public API to get information about text layo

Re: RFR: 8341670: [Text, TextFlow] Public API for Text Layout Info [v5]

On Thu, 10 Oct 2024 19:23:47 GMT, Andy Goryachev wrote: >> Andy Goryachev has updated the pull request incrementally with one >> additional commit since the last revision: >> >> convert to wrapper > > One additional thought/question: > > There is a need to extract a few more data points from

Re: Is it possible to disable JavaFX shutdown hook?

when ready. Regards Jurgen On Thu, 25 Jul 2024 17:43:25 +0200, PavelTurk wrote: Hello all. JavaFX adds its own shutdown hook. That gives many problems when it is necessary to work with application, when system is shutting down, for example, if user presses CTRL+C. The first problem I desc

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

e this. In both cases the "Too many touch points reported" issue will need to be readdressed. It would be nice to see this move forward somehow. Thanks again, Jurgen On Tue, 04 Jun 2024 18:28:47 +0200, Markus Mack wrote: On Tue, 21 May 2024 14:25:51 GMT, Michael Strauß wrote:

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

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

did before. There are bound to be other applications out there that are going to find themselves in a similar position. PLEASE ! Regards Jurgen On Wed, 24 Jan 2024 15:15:31 +0200, Kevin Rushforth wrote: Thank you to Jurgen for raising the question and to Nir, John, and Michael for evaluati

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

indeed so, then could you please explain the purpose of the receiversLocked and animationTimersLocked flags, as well as the point of receivers.clone() and animationTimers.clone() all of which indicate to the contrary. Thanks, regards Jurgen On Tue, 23 Jan 2024 18:36:16 +0200, John Hendrikx

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

rame setTime animation.setCurrentTicks clipInterpolator.interpolate animation.doJumpTo sync(false) setCurrentTicks clipCore.jumpTo timeline.getStatus() clipInter

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

le( "-fx-text-fill: green" ); // This is OK memoryLabel.setText( "This is NOT okay" ); // This is NOT, move to before play Interesting API idea, however I don't think it's really needed for sensible developers. Regards Jurgen On Mon, 22 Jan 2024 22:53:48

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

ay this could happen. Furthermore it doesn't appear as though the animation code can be left in some strange inconsistent state as a result of this. Jurgen On Mon, 22 Jan 2024 17:58:20 +0200, John Hendrikx wrote: This seems like a reasonable use case, and perhaps this was the

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

http://javafx.com/fxml/1"; fx:controller="TestView"> On Sat, 20 Jan 2024 17:08:41 +0200, Nir Lisker wrote: Hi Jurgen, What I'm confused about the most is what it is you are actually trying to do that necessitates the use of anim

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

hen during the pulse the method was invoked. If play is invoked just before the next pulse then the 'animation' could be running, or if stop is invoked just as a pulse completes then it will not be executing. Otherwise the 'animation' will only actually be (not) executing in the next pulse. Hope this clarifies things. Regards Jurgen

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

propriate place, however the test case will require it) 2. Changing the arrays in AbstractPrimaryTimer to be CopyOnWriteArrayList(s) and removing previously supporting array code. 3. Adding a test based on the one supplied in JDK-8159048 to check that a NPE isn't thrown anymore. Hope t

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

mes occur but not put a burden on the existing code in the wild and allow views to be loaded with Task call() without worries. Thanks, regards Jurgen On 8/18/2023 4:17 PM, Kevin Rushforth wrote: As a heads-up for app developers who use JavaFX animation (including Animation, along w

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

not put a burden on the existing code in the wild and allow views to be loaded with Task call() without worries. Thanks, regards Jurgen On 8/18/2023 4:17 PM, Kevin Rushforth wrote: As a heads-up for app developers who use JavaFX animation (including Animation, along with any subclasses, and An

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

irect result of fixing JDK-8249737 RuntimeException: Too many touch points reported. (https://bugs.openjdk.java.net/browse/JDK-8249737) Please reopen both of these issues. Thanks, Jurgen

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

49737 RuntimeException: Too many touch points reported. (https://bugs.openjdk.java.net/browse/JDK-8249737) Please reopen both of these issues. Thanks, Jurgen