I think that the real problem is undoing things when you can’t possibly see that you are losing something. I can think of a few ways to fix this:
1) undo/redo only works on a single page. When you go to a new page, it would start a new set of undo/redo things. This would keep you from hitting undo and having something on another page go away.
2) have undo always switch to the page that the undo actually did something to. At least then you would know what had happened, and you could hit redo if you wanted.
3) have undo warn you that you are undoing something on a previous page (without automatically changing pages which can be distracting)
Personally, I think that going to a new page should always clear the undo stack, but that might be hard for people who scroll around their notebook a lot looking at stuff, and then when they get back to the page they were working on, they can’t undo a recent action.
Tim
supported this idea
·
I think that the real problem is undoing things when you can’t possibly see that you are losing something. I can think of a few ways to fix this:
1) undo/redo only works on a single page. When you go to a new page, it would start a new set of undo/redo things. This would keep you from hitting undo and having something on another page go away.
2) have undo always switch to the page that the undo actually did something to. At least then you would know what had happened, and you could hit redo if you wanted.
3) have undo warn you that you are undoing something on a previous page (without automatically changing pages which can be distracting)
Personally, I think that going to a new page should always clear the undo stack, but that might be hard for people who scroll around their notebook a lot looking at stuff, and then when they get back to the page they were working on, they can’t undo a recent action.