Re: javafx.scene.shape.Path (memory) inefficient PathElements

2017-07-27 Thread Jim Graham
And, to clarify, the super-lazy property fix is currently only targeted to JDK10. A case would need to be made to back-port it to any update releases once it is fixed there. We haven't seen or presented such a case at this point so we are only planning to fix it in JDK10 and Tom has indicated

Re: javafx.scene.shape.Path (memory) inefficient PathElements

2017-07-27 Thread Tom Schindl
As mentionned at the beginning of the thread, in FX8 you can roll your custom implementation. I did not yet had the time to test the changes Jim made :-( Tom On 27.07.17 13:41, Jose Martinez wrote: > Just curious, did this make it to the 8u144 release? If not, any idea > which release (or when)

Re: javafx.scene.shape.Path (memory) inefficient PathElements

2017-07-27 Thread Kevin Rushforth
No, this fix hasn't yet been reviewed and pushed. When it is it will go into JDK 10. -- Kevin Jose Martinez wrote: Just curious, did this make it to the 8u144 release? If not, any idea which release (or when) we can expect it? Thank youjose On ‎Wednesday‎, ‎May‎ ‎24‎, ‎2017‎

Re: javafx.scene.shape.Path (memory) inefficient PathElements

2017-07-27 Thread Jose Martinez
Just curious, did this make it to the 8u144 release?  If not, any idea which release (or when) we can expect it? Thank youjose On ‎Wednesday‎, ‎May‎ ‎24‎, ‎2017‎ ‎08‎:‎38‎:‎41‎ ‎PM‎ ‎EDT, Jim Graham wrote: Thanks Tom, I've already posted a patch for 8180938 (lazy

[10] Review request: 8185132: window.requestAnimationFrame API is not working

2017-07-27 Thread Arunprasad Rajkumar
Hi, Please review the following changset, Webrev: http://cr.openjdk.java.net/~arajkumar/8185132/webrev Bug: https://bugs.openjdk.java.net/browse/JDK-8185132 Detailed analysis is updated as JBS comment. Thanks, Arun