https://bugs.kde.org/show_bug.cgi?id=416584
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
|hics/krita/commit/88aa1a2bd |hics/krita/commit/4d7df799d
|9d04dbb3e6cc3468de8ba81f502 |66ec8f63ef382a35dabe4b62df0
|4427 |2dfe
--- Comment #2 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit 4d7df799d66ec8f63ef382a35dabe4b62df02dfe by Dmitry Kazakov.
Committed on 12/08/2020 at 17:52.
Pushed by dkazakov into branch 'master'.
Fix first redo() after paint device color space conversion
There is a bug in all versions of Krita since November, 5th 2019.
BUG
===
1) Change image color space from RGBA to GrayA.
2) Undo with Ctrl+Z
3) Redo with Ctrl+Shift+Z
The image looks as if the color space has changed back to GrayA,
but it is not so. Only the color space of the projection has changed
to GrayA, the layers are still in RGBA. It can be seen by the state
of Advanced Color Selector (it shows colors instead of shades of gray)
and in layers' properties.
WORKAROUND
==========
1) Press Undo (Ctrl+Z) and Redo (Ctrl+Shift+Z) again.
The image will enter the correct state. All further undo/redo
operations for this particular action will be executed correctly.
TECHNICAL DETAILS
=================
The bug was called by commit e39e6379564b5f6c4c72960a6e1ee3ca7716d5bd,
which caused DeviceChangeColorSpaceCommand to skip the first redo of
the operation, which was not in its design.
The bug has been caught by KisColorizeMaskTest.
CC:kimages...@kde.org
M +1 -1 libs/command/kis_command_utils.cpp
M +15 -15 libs/image/kis_paint_device_data.h
https://invent.kde.org/graphics/krita/commit/4d7df799d66ec8f63ef382a35dabe4b62df02dfe
--
You are receiving this mail because:
You are watching all bug changes.
