-
Sub-task
-
Resolution: Fixed
-
P4
-
internal
-
x86_64
-
os_x
Blitting in Main thread has 2 problems:
1) Adds lot of delay and degrades performance.
2) We will be unable to block the RenderQueue before blitting.
Using setNeedsDisplay and then blitting in Appkit thread is better option and it resolves both the issues
1) Adds lot of delay and degrades performance.
2) We will be unable to block the RenderQueue before blitting.
Using setNeedsDisplay and then blitting in Appkit thread is better option and it resolves both the issues
- relates to
-
JDK-8227664 Disable additional RQ.flushNow() that hogs the AWT-EventQueue thread
- Closed
-
JDK-8230921 Improve in responsiveness after enabling setNeedsDisplay
- Closed
-
JDK-8230849 Remove scheduleBlitAllModifiedLayers code after setNeedsDisplay
- Resolved
-
JDK-8230789 Call setNeedsDisplay when we are drawing child layers recursively
- Resolved