Undo annoyance

[X.]

Is this just me but I am annoyed by this "feature" of the Undo:

When you undo something in a diagram that is hidden (for instance because it is in another case), you only get the "ghost contour" of what is restored. That's not very useful and I am wondering whether this is worth a suggestion (could not find one specific to that point).

Example:

WTH is that and where is it? Should I stop undoing and check all the cases to figure out where this stuff is hidden (and then how do I go back to the original case I was looking at?).

[smercurio_fc]

---

@X. wrote:

Is this just me but I am annoyed by this "feature" of the Undo:

---

It's just you.

I've seen that all the time, and frankly, it's never bothered me. What would you prefer it to do? Switch to the case?

[X.]

I don't know. I am just pointing the annoyance. Other shall do the brainstorming.

I am just saying: what do I learn from this ghost contour? OK, let me rephrase this: what do YOU learn from it?

[smercurio_fc]

I don't really expect to learn anything from it. Clearly I had deleted something in that case, moved to another case, and did something else. I already know I deleted it, so it showing me the contour just indicates it's at that step in the sequence. OK. I don't really need it to show me anything else.

I'm just saying it doesn't really annoy me, and you just asked whether it annoys others. It might, but not me. Maybe I'm just feeling lackadaisical today. 

Maybe it would help if we had an Undo window showing the undo steps? Sort of like the one in Paint.Net. I think there may have been an idea about it, but I'm not sure. There were a lot of ideas tossed around regarding Undo.

[Darin.K]

You could certainly request that changing visible case (or event) operations are added to the undo buffer.

[X.]

I had browsed this thread  before I decided to rant. Of course I totally support the corresponding suggestion. But that would clearly be a major rework... How long did we look for the Undo? LV 5? I am not sure I will still be programming when this stuff is going to show up 🙂

[X.]

@ Darin.K: Care to expand?

[Darin.K]

Pretty simple.  Right now changing the visible case or event does not add to the undo buffer.  So if you delete an object, change visible case, undo you only undo the delete operation.  It sounds like you would prefer the first undo to change back to the original case and then have a second undo undelete the object.

It is always a balance between polluting the buffer and missing out on key steps.

[X.]

Yeah, I guess it would do the trick. After all, every move of an object is tracked...

[LV_Pro]

But it would even add another level of confusion " (and then how do I go back to the original case I was looking at?)", where at least you navigated back to the case, rather than mysteriously being transported through an unknown number of case.