Replies: 1 comment 1 reply
|
This seems like a useful workflow improvement, and I would separate it into two actions:
For the import action, I would avoid treating the dropped file as a blind replacement. The editor should first validate that the .osu belongs to the same beatmap, then load it through the same beatmap model and undo/redo path used by normal editing. If the file is from another difficulty, show a clear choice to open it as a new difficulty or reject it, rather than silently replacing the current map. A safe flow would be: The validation should at least cover the beatmap identity, format/version, and whether the imported difficulty is compatible with the current song. It would also be useful to preserve a backup/undo point so importing a file from another mapper does not destroy local edits. I agree that Edit externally and Open current song folder are confusing when they currently converge on the same result. Naming the latter explicitly would make the intent clearer, while Edit externally could remain the action that launches the configured external editor. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
thought itd be amazing to have this feature for convenience since most mappers just send out .osu files esp when the .osz is too big in size so i think having a dedicated import option to drag the .osu right away to update the current map open would be awesome
i think separating "Edit externally" and adding an "Open current song folder" option instead would also bring more clarity since clicking the current former option automatically opens the song folder anyway even tho theres an "Open Folder" option after clicking "Edit externally" which is redundant lol + to match stable
All reactions