Changing layer visibility clears redo history but does not add an entry to the history. 1) I feel this is inconsistent: anything that irreversibly changes history should have a history entry. 2) I feel changing visibility is not a type of thing that should change history. (alternatively, it's a user visible change so maybe it should get a history entry, but since history is linear and not treelike, I think it could be rather inconvenient to take this choice; preserving possible art redo would be more important?)
Regression of 195519 ?
If I toggle visibility in the layerbox, it doesn't get added to the undo history. I do not see the undo history being cleared. If I toggle visibility in the layer properties dialog, an undo state is added: is that what you mean?
This looks more like a previous bug when zooming the canvas would trigger a step (edit guidelines) eliminating any re-do steps and potentially deleting strokes. A simple way to reproduce is to do 4-5 strokes, undo some of them, toggle view of the layer, the redo history will be cleared and without showing any indication of any other step (as the view toggle doesn't gets recorded) this too has a potential of accidentally deleting work done without any indication of what has happened. Just build krita git master, can reproduce it as the OP.
Yeah, that's why I said redo history instead of undo history, but I guess I should have been clearer. I think what Quiralta said matches.
+ 1 I can reproduce this too Steps to reproduce 1) Open Krita and create a new document and a new layer 2) On the new layer add 5 simultaneous strokes so that each strokes get recorded as 5 action in undo history docker(open undo history docker to keep and eye on redo steps) 3) now hit ctrl z two times to undo last two strokes 4) Now just switch off the visibility of the layer. You'll notice that just by switching on and off the layer visibility we lose the ability to redo last two strokes.
This is the same issue as bug 389876 -- layer visibility isn't pushed on the undo stack, but somehow, it does set the document as modified. *** This bug has been marked as a duplicate of bug 389876 ***