Story:
A user saves their current interactions history to a file on their desktop named "history.hist". A few days later, they do the same thing. Because their desktop is cluttered with files, they don't notice that there is already a file with that same name, so they reuse it.
DrJava should alert them that a file with the same name already exists, and ask if the user really wants to overwrite it. Currently, DrJava silently overwrites the file without a warning or a way to avert disaster.
Logged In: YES
user_id=429731
While addressing this, be sure to reuse the code from the
regular save dialog, if possible. (I don't remember how it
works off the top of my head, but I know we do prompt before
overwriting a definitions file.) Refactor if necessary.
Logged In: YES
user_id=429731
Any progress on this yet? I'd like to get it finished up.
Logged In: YES
user_id=429731
I'm going to reassign this to me and finish it up so it's
fixed for the stable release.
Logged In: YES
user_id=429731
History.writeToFile wasn't checking for
selector.verifyOverwrite() the way DefaultGlobalModel does
when saving a file. It does now, and there's a test to make
sure it does.