Hi, Clemens.
On 23.01.2015 2:18, Clemens Eisserer wrote:
The D3D & OpenGL pipelines have some code to work around the issue by
performing a sync for blits which are equal to the blits of Swing's
backbuffer operations.
Actually it will do this for any blits to the window, because the swing
can use different paint strategy(w/ or w/o buffer) or the user can draw
something to the window directly via BufferStrategy.
My plan was to introduce flush-points in AWT to get the content on
screen where appropriate instead of guessing in the pipeline which
operations could be backbuffer blits. However I am not even sure this
is feasable, so it will take some time for to figure out a sane way.
Best regards and thanks for your investigations, Clemens
--
Best regards, Sergey.