Export to Batch file about qzdl

[duganchen]

Well, it's not entirely up to me, but if it were then the answer is no. I'm personally trying very, very hard to keep the current codebase free of any code that isn't cross-platform.

Also, QZDL already covers most cases where I could imagine "Export to batch file" (or something similar, like "Add to Steam") being useful:

First, "Show Command Line", in the "ZDL" menu, gives you a command-line that you can copy-and-paste into a batch file, should you want one. It's no the same command that QZDL (currently) uses internally, but it's untouched from when I started contributing, and I assume it works.

In that menu, there is also "Save .zdl". That saves the list of PWADs into an ini file with the .zdl extension. The idea is that you associate .zdl files with QZDL, so that when you double-click on an .zdl file, it launches QZDL with the list of PWADs populated. If you check ""Launch *.ZDL files transparently", then double-clicking on an .zdl file with launch DOOM with those PWADs active. If you want to create a batch file (or shell script) that launches Brutal DOOM with a bunch of visor and texture mods, then create the list of PWADs in QZDL, save it as a .zdl file, and have the batch file launch QZDL with the path to that .zdl file as its argument.

[DoomRater]

I'm surprised the software is cross platform at all. Guess that shows just how far out of the loop I've been with ZDoom and GZDoom lately.

I saw the "Show command line" which is a bit of extra manual work to copy and paste into a command line. Also in Windows, you cannot highlight the text in the popup window, ergo no way to copy the command or arguments which are shown on individual lines.

It might be more appropriate for me to convert .zdl to a batch file instead, as long as the file structure stays consistent. That way any work I do can stay separate from QZDL and not affect people's ability to compile it.

[duganchen]

The text in "Show command line" is selectable now.