Feature Requests item #774899, was opened at 2003-07-21 04:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438938&aid=774899&group_id=44253
Category: User interface
Group: Small (< 1 pair-week)
Status: Open
Priority: 5
Submitted By: Peter Centgraf (centgraf)
Assigned to: Nobody/Anonymous (nobody)
Summary: Un-"modify" after Undo
Initial Comment:
Story:
A user opens a file and performs a modification. DrJava
sets the document's "modified" flag. The user then
regrets the change and uses "Undo" to remove it and
return to a pristine state. DrJava notices that all
changes have been undone and clears the "modified" flag.
The user then closes the document without incident.
Currently, when the user attempts to close the
document, they are warned about non-existant
modifications. This is annoying and can easily be
avoided.
Some editors go a step further and notice when a
document is in the same state as the file on disk even if
Undo was not used explicitly. I can't think of a way to
check this without doing a full string comparison on every
edit, which I think is unacceptably heavy-weight. If
someone can think of a better way to do it, or can
implement the comparison without sacrificing
performance, please implement it.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=438938&aid=774899&group_id=44253
|
