This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Redo is disabled when you save the file | ||
|---|---|---|---|
| Product: | editor | Reporter: | Petr Dvorak <joshis> |
| Component: | Actions/Menu/Toolbar | Assignee: | issues@editor <issues> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | CC: | jbecicka, jglick, karmaflute, pjiricka, tmysik |
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 48427 | ||
| Bug Blocks: | |||
|
Description
Petr Dvorak
2008-06-30 09:58:40 UTC
Not sure why it behaves the way how it behaves. I would certainly expect either both undo/redo to get disabled (ie. saving clears the undo/redo manager) or both of them to stay enabled (ie. the undo/redo manager is not affected by saving). I think this chould be fixed/resolved in the 6.5 release version - you can't redo your changes once you save a file,
this is not very handy sometimes...
> I would certainly expect either both undo/redo to get disabled (ie. saving clears the undo/redo manager) or both
> of them to stay enabled (ie. the undo/redo manager is not affected by saving).
The second possibility is what I would expect...
Well, I believe the problem is that save event is currently considered an editor event, therefore creating a "new
branch" in the event history (as if you started typing something)...
This issue depends on issue 21237 (each undoable edit needs to be wrapped and the save points marked inside the wrapper instead of creation of extra save edits that cause the rest of undo queue to be cleared) and also on the current remove-trailing-WS functionality because it adds extra edits for the removed WS at save time. This is more tricky to resolve (unless we would remove the whole functionality) - please see my comment in issue 13063 of a possible solution (unfortunately it's too late to start to implement that now during stabilization phase since I already know that there would be additional non-trivial changes necessary at least for java and probably other modules too). BTW I've tested other java IDEs and I've seen redo disabled after save too. Also any additional work-at-save-time requests e.g. doing some sort of reformat at save time etc. lead to the same problem so I'm wondering whether we shouldn't relax this requirement completely. OK, let's postpone it for a while...
> BTW I've tested other java IDEs and I've seen redo disabled after save too.
Well, it is possible - they might have the same defect.
Try something simpler: gedit or OpenOffice Writer. Undo/Redo remains enabled after save. This is what a text (code)
editor should do IMO, but I don't want to push it too hard... I just thought it should be simple to fix:-/...
*** Issue 154652 has been marked as a duplicate of this issue. *** *** Issue 170830 has been marked as a duplicate of this issue. *** My vote for this Duplicates 120981 168303 138591 21237 *** Bug 168303 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 21237 *** since so long why this haven't fix it... it really frustrated.. I think this is very high priority for this. Redo and Undo always use for testing coding purpose, after undo and save not able to redo, it is really frustrated. Hopefully Netbean team can take care for this kind of basic need. I can't believe NB doesn't support this basic editing feature. In web development it is very often the case one tries things out and then discard them. Well, not possible with NB... Folks, this defect has been duplicated to issue #21237. I think you should be adding your comments there. Thanks a lot *** This bug has been marked as a duplicate of bug 21237 *** |