 |
Btw, maybe that's useful for you, it's possible to bind a shortcut to your away0.map copy save routine. In the console, type: bind "SaveToAway0" "SaveMapCopyAs c:\games\darkmod\fms\away0\maps\away0.map" Then you can find that "SaveToAway0" command in the shortcut list in Edit > Keyboard shortcuts. (The path needs to be the absolute path name, not a FM-relative path.) |
 |
greebo, thanks for quick fix. It's good to know about the bind command. I haven't used the DR console yet, so should look in to that and what's available. It would be nice if the bound-version of SaveMapCopyAs could handle FM relative, along these lines: bind "SaveToAway0" "SaveMapCopyAs shortname.map" where "shortname" is any specified string without path delimiters or wild cards; path to current FM project is assumed. bind "SaveToAway0" "SaveMapCopyAs *.map" uses <path to current FM project>/<FM>.map bind "SaveToAway0" "SaveMapCopyAs" ditto While I'm riffing on possible related DR feature requests, I've always wondered why, if I use Open to navigate to a map file that is not the current project, DR doesn't warn me then (or at least later at save/save-as time) that the current project and current map don't match, and offer to change the current project. (If it does this now under 2.13, ignore me) More than once I've found I've generated files to the wrong project. Yeah, I know, I should make these separate bugtracker posts. I'm being a slacker this a.m. |
|
|
Yes, agreed. Feel free to open a new issue request about upgrading the SaveMapCopyAs to be able to deal with a project relative path. |
- Anonymous
