https://bugs.kde.org/show_bug.cgi?id=430605
--- Comment #5 from stephen <tgdev...@gmail.com> --- (In reply to Tiar from comment #4) > I guess that might be because it's waiting for the transformation to finish. Then optimizations are awaited. Better ergonomics as well : a loading gauge that shows the progress of the operation from 0 to 100% before allowing the user to interact with the app again. The chances for the bug to happen are high when you quickly move pixels in a selected area to a different position then immediately deselect. -- You are receiving this mail because: You are watching all bug changes.
