Menu
▾
▴
#1162 undoing throws track heights out of whack
Draw two overlapping segments on track 1. Drag to track 2. Draw a new segment on track 4 to trigger the refresh that leaves track 3 empty and track 2 fully and correctly populated.
Now undo until there are just two segments on track 1 again.
Try to repeat the drag and refresh. It's not possible. The two segments will always behave as if they were on separate tracks from this point forth.
(This might go away with the underlying refresh problem solved, but it's worth revisiting after that is solved, to make sure there isn't some undo problem on top of the refresh problem.)
Logged In: YES
user_id=663564
Originator: YES
This is no longer repeatable, because the behavior has changed.
Draw two overlapping segments on track 1. Drag to track 2. They go to the wrong spots as detailed in another report. Drawing a segment on track 4 doesn't trigger a refresh, and they stay in the wrong spots forever as far as I can manage.
Undoing this back to the start point and repeating it doesn't seem to change anything. On subsequent drags, the two segments continue to behave as they did on the first drag.
So I think this report is no longer valid as a report of an undo problem, but probably worth leaving open until the drag problem is addressed, in case the behavior changes yet again in the interim.
Logged In: YES
user_id=663564
Originator: YES
After playing with undo and redo ad nauseam, I did wind up in a state where I couldn't undo all the way back to nothing. There were at least two operations pushed out of the stack and gone. Is that normal? I wouldn't think so, but I can't sit here and come up with a more methodical way to duplicate what just happened either, and I'm prepared to whistle and move along.
Logged In: YES
user_id=13489
Originator: NO
The command stack does have a size limit at 50 commands. If you add more than this to the stack (so that you would have to undo more than 50 times to get back to pristine), earlier commands will be dropped.
The size limit is arbitrary, we could probably reasonably make it bigger. Individual commands can be fairly large though of course (e.g. deleting a segment with lots of events in it is a large command because all the events you deleted are stored in it).
Logged In: YES
user_id=663564
Originator: YES
It suffices for me to know that I probably just hit the wall. No problem.
Logged In: YES
user_id=663564
Originator: YES
Damn that's annoying. I didn't change the status from pending, and I'm pretty sure the "new comment re-opens bug" option is turned OFF.
Rrrrrrr.
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).