#107 Improve save behavior of scripts on quit

open
nobody
None
5
2011-10-24
2011-10-23
No

When you close a text file with unsaved changes, you get a confirmation dialog asking whether to really close it, with choices Yes and No. This is very bad WRT usability, because the choices are very generic, and you have to read carefully the question to decide what to do: many programs do it the other way, by asking whether to save changes or not.

I suggest this dialog uses explicit button labels, like "Save", "Discard" and "Don't quit", just like what happens when you close a workspace. The question should be "Do you want to save changes?" rather than the contrary, to match the same pattern as closing workspaces.

By the way, the new distinction between "Discard" and "Don't quit" should allow you to close RKward and save changes in modified scripts in one go. At the moment, if there's one script with unsaved changes, you can only cancel the quit, save, and retry. Another point is that RKward should handle script files first, and the workspace afterwards, since saving the workspace takes time: if you save the workspace, and then notice you have unsaved changes in a script and you no longer want to quit, you've wasted time saving the workspace.

Discussion

  • Thomas Friedrichsmeier

    • labels: 673590 -->
     
  • Thomas Friedrichsmeier

    Yes, this really needs an overhaul. Thanks for your suggestions.

    I'm moving it to our RFE-tracker, though.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks