https://bugs.kde.org/show_bug.cgi?id=417406
--- Comment #3 from lemp...@gmail.com --- (In reply to Ahab Greybeard from comment #2) > re. "Example: If stack size set to 10, I do 12 strokes, click on empty to > clear everything last 10 strokes disappear while the first 2 are left on the > canvas." > > This is what I'd expect. You can't undo deeper than the stack size. The > first two strokes are no longer recorded on the stack. > > re. "then I clicked on empty and out of 2 remaining strokes 1 disappeared > and 1 stayed. I tried again, this time both strokes disappeared." > > I haven't seen that behaviour after a couple of tries. If it's a random > thing, roughly what percentage of the time have you seen it happening? I see, I'd expect the same behaviour Photoshop has with the same function when it returns the document to its initial stage (let's say you save your work, come back to it later, load the doc make changes and even if you go over the undo stack limit you can always come back to the doc before changes quickly in that particular session), that's my bad if that's not how it is meant to work (I think I saw the same functionality in some other programs but definitely my bad). When it comes to the second part, it's really hard to tell how often certainly not often or at least I haven't found a way to replicate it with decent success (and considering during work I have a high number for undo stack noticing if if happens or not mid work is impossible at that point unless it's early with blank canvas), I remember something similar happening a few versions back last year when there was something wrong with undo stack but that as fixed so I'll say we can probably close this or delete this report if you know how (?) because the main part is as you say Krita functionality I failed reaching that point during my research before reporting here and the second half is so random that I don't even know where to properly start. Thank you very much and sorry to take your time on bug testing. :0 -- You are receiving this mail because: You are watching all bug changes.
