I've been using SLADE's map editor for a good while now, I've run into a source of friction and I'm curious as to if it's intended.
For my latest ZDoom-based project I've been using a directory with loose files, as GZDoom and SLADE can both handle that just fine, with my maps in the maps/ subdirectory. It's very easy to work with, I can just copy files in with my file manager, and I have a little script that creates a PK3 for release distribution.
To edit, I select "Open Directory", select my project dir, and then browse into the maps subdir, open map01.wad in the map editor, and start working.
When I save changes in the map editor, however, the changes aren't committed to the actual file unless I alt-tab back over to SLADE's main (non map editor) window and save the map01.wad file.
I think I know why this works how it does... SLADE supported PK3-based mods before it supported working out of directories, so it treats the latter exactly like the former. And this still seems best for working with assets like image and text lumps. However I think in the specific case of maps, it would be better to save the map WAD file directly to disk, instead of requiring the extra step. When I'm in the map editor, I save reasonably frequently, and it breaks flow to have to alt-tab back to SLADE's main window and save. Also if the map editor crashes, I lose everything I've done since I last alt-tab+saved.
It's also possible I'm just Doing It Wrong and there's a better way, or this is a conscious UI design decision. Thoughts?
If you agree the save-directly-to-disk behavior is better for directories, I can create an issue on the project's github. Thanks!