Skip to content

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

@elluminance

Description

@elluminance

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions