-
Enhancement
-
Resolution: Won't Fix
-
P3
-
None
-
None
Implementation relies on Node.contains() method that might be very time consuming (see RT-5278 and RT-5279 for example).
And pick() is actually called on each pulse.
We should not be doing more than needed.
In particular it has no sense to check whether point is in the node if the following is true:
a) Node has no childs (e.g. text nodes never have any childs)
b) Node itself is not interested in any mouse updates
This may significantly improve performance.
E.g. solving this in addition to fix for Rt-5278 improves fps for transformed text testcase from RT-5278 from 2 to 250.
And pick() is actually called on each pulse.
We should not be doing more than needed.
In particular it has no sense to check whether point is in the node if the following is true:
a) Node has no childs (e.g. text nodes never have any childs)
b) Node itself is not interested in any mouse updates
This may significantly improve performance.
E.g. solving this in addition to fix for Rt-5278 improves fps for transformed text testcase from RT-5278 from 2 to 250.
- blocks
-
-
- Closed
-
- duplicates
-
JDK-8108234 Resizing/laying out Text is way slower if the mouse cursor is over the window
-
- Closed
-
- relates to
-
-
- Closed
-
