https://bugs.kde.org/show_bug.cgi?id=361448
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Latest Commit|http://commits.kde.org/krit |https://commits.kde.org/kri
|a/f114bcc1a2251d55cb3339548 |ta/58b982cbb7bfa133bbb0bab5
|9cc8d52c8f84ee6 |b163c24a9bb83d61
Status|CONFIRMED |RESOLVED
--- Comment #16 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit 58b982cbb7bfa133bbb0bab5b163c24a9bb83d61 by Dmitry Kazakov.
Committed on 19/09/2018 at 08:23.
Pushed by dkazakov into branch 'master'.
Fix flickering on Instant Preview finishing original regeneration
The problem happened mipmap regeneration. Basically, we should not
start regenerating tile mipmaps until all the updates have been
completed. Otherwise, some parts of the regenerated mipmap will
have outdated (old) content and the user will see flickering.
Now KisImage has two special signals that notify the canvas thay
a special "lod rest updates batch" is coming. The canvas will block
tile regeneration for this batch and will start it right after the
batch is completed. Therefore the user will see completely prepared
data.
Fixes T2145
CC:kimages...@kde.org
M +20 -0 libs/image/kis_image.h
M +16 -0 libs/image/kis_image_signal_router.cpp
M +3 -0 libs/image/kis_image_signal_router.h
M +19 -5 libs/image/kis_suspend_projection_updates_stroke_strategy.cpp
M +2 -0 libs/ui/canvas/kis_abstract_canvas_widget.h
M +70 -16 libs/ui/canvas/kis_canvas2.cpp
M +2 -0 libs/ui/canvas/kis_canvas2.h
M +4 -0 libs/ui/canvas/kis_qpainter_canvas.h
M +23 -0 libs/ui/canvas/kis_update_info.cpp
M +21 -0 libs/ui/canvas/kis_update_info.h
M +11 -4 libs/ui/opengl/kis_opengl_canvas2.cpp
M +1 -0 libs/ui/opengl/kis_opengl_canvas2.h
M +15 -20 libs/ui/opengl/kis_texture_tile.cpp
M +8 -4 libs/ui/opengl/kis_texture_tile.h
https://commits.kde.org/krita/58b982cbb7bfa133bbb0bab5b163c24a9bb83d61
--
You are receiving this mail because:
You are watching all bug changes.
