02-01-2008, 06:02 PM
Here's an apparent bug in Project 4.1 on Windows XP Pro.
When I use the undo and redo buttons, the system doesn't jog the screen over to where the undo operation is taking place. You have to guess and hope that you're undoing things to the right point. Worst of all, there are times when the undo operation erases the history of the redo operation. In other software applications it's possible to undo several changes as a cue to show or remind you what's being undone.
These two bugs -- especially taken together -- make it virtually impossible to rely on the undo/redo operation to help save you from inadvertent changes or to take you back a few steps to start over. This buggy operation makes these buttons a disaster waiting to happen -- three times already I've fallen prey to them. I "rolled the dice" and chose to undo several changes hoping that one more step would re-activate the "redo" button's memory. No such luck.
Each time I sit here with a pit in my stomach wondering, "What the heck did the program just change?"
And I just found one more bug with the undo/redo operation:
If you take any change, undo it, redo it, undo it, redo it, etc., etc., you'll find that sometimes it takes one click to undo the operation, other times it takes two clicks. Combine this with the fact that sometimes you have to guess if you're undoing the right operation and your project quickly becomes an unknown mess.
Is there an online bug tracker somewhere for these applications? Sure would help to know things like this ahead of time.
Thanks,
Tim
When I use the undo and redo buttons, the system doesn't jog the screen over to where the undo operation is taking place. You have to guess and hope that you're undoing things to the right point. Worst of all, there are times when the undo operation erases the history of the redo operation. In other software applications it's possible to undo several changes as a cue to show or remind you what's being undone.
These two bugs -- especially taken together -- make it virtually impossible to rely on the undo/redo operation to help save you from inadvertent changes or to take you back a few steps to start over. This buggy operation makes these buttons a disaster waiting to happen -- three times already I've fallen prey to them. I "rolled the dice" and chose to undo several changes hoping that one more step would re-activate the "redo" button's memory. No such luck.
Each time I sit here with a pit in my stomach wondering, "What the heck did the program just change?"
And I just found one more bug with the undo/redo operation:
If you take any change, undo it, redo it, undo it, redo it, etc., etc., you'll find that sometimes it takes one click to undo the operation, other times it takes two clicks. Combine this with the fact that sometimes you have to guess if you're undoing the right operation and your project quickly becomes an unknown mess.
Is there an online bug tracker somewhere for these applications? Sure would help to know things like this ahead of time.
Thanks,
Tim