Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Save Map as..." behavior not intuitive #288

Open
elluminance opened this issue Aug 7, 2023 · 0 comments
Open

"Save Map as..." behavior not intuitive #288

elluminance opened this issue Aug 7, 2023 · 0 comments

Comments

@elluminance
Copy link
Contributor

In most programs, when one uses the "Save As" function, it changes the currently "open" file so that subsequent saves will apply to the 'saved as' file.

For example, let's assume that someone is making a map called map-1. They are done with that part of that map, and want to save it as a different file. Let's call this file map-2, thus they press the Save Map as option and save their map as map-2. Let's say they make changes to the map, and save it again - these changes will not apply to map-2's file - no, they'll apply to map-1's file.

This current behavior is simply not what one would expect when using "Save As" - it's much closer to what some other programs (i.e. GIMP, among others) might call an "export as" rather than a "save as". I like using the Save Map as... so I can make a 'template' map, from which I can make new maps that conform to the same style. Me accidentally overwriting the template map multiple times has forced me to mark the file as read only to ensure I don't accidentally overwrite the file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant