https://bugs.kde.org/show_bug.cgi?id=451745
--- Comment #2 from php4...@gmail.com --- > Yeah, when Undo changes something not visible, we should show the user what > happened That is absolutely a huge part of the issue but that's not all. If that "something not visible" is "something that was done in another tab/window", that shouldn't be undoable in the first place from the current tab. Each tab should have its separate undo history (which should get destroyed when you close that tab). Think of when you edit files in multiple tabs or windows in any modern text editor (or other kind of editor, e.g. images in GIMP). Would you imagine hitting Ctrl+Z in a tab, and undoing something that was done on another file in another tab? No, right? Even if that brought focus to the affected file and scrolled to the affected position and made the (un-)changes visible (which is what happens when you undo in the current focused file), that wouldn't make it acceptable. And when you close and reopen a file, you don't expect to be able to undo stuff that was done before closing and reopening the file. Analogies don't automatically hold, but I'm pretty sure this particular analogy holds quite well here. -- You are receiving this mail because: You are watching all bug changes.
