Feature Request: Custom Command-Line String Builder

Issue #3726 new
gt46l created an issue

So I've been writing a bunch of dos scripts recently to help me manage the command lines for the various older and more niche systems that require a lot of if/thens and command like switches. Specifically for systems like TRS-80 (coco), Atari Adam, C64, BBC micro, Acorn Arch/Electron, Daphne/Singe, systems where they have 4+ media formats like cassettes, floppies, carts, cds, hard drives etc. or the command lines are very distinct.

Now I know Launchbox has the ability to store custom command line strings for each ROM and I would just use it, but what is preventing me from doing that is ease of use over an entire set.

Here is what I propose:

Have a UI screen that is just a bulk listing of the "custom command lines" found on the emu tab of a Rom's properties. Have the listing for an entire rom set based on whatever filter desired. Presumably by system, but maybe also by name or other aspects.

Then you have that list of command lines in a listbox with maybe a few ID columns like System Name, LB db ID/name, Rom file Name, and Command Line. Make the list multi-selectable and provide a text box for the user to build a string for the batch they select. Have an overwrite, or "append" choice so you can select a batch and populate them, then select a new batch and then append, and so on.

Optionally, also provide an extract button that spits that listing out to a csv, or an import button that takes a csv and match say the filename in csv being imported to the filename field in LB, and where they match update the command line. I think this feature would help people with these type of systems immensely. I know it will save me a lot of building these scripts, and people could possibly share these listings with each other so that the less technical users can play even the most challenging systems to emulate.

The system auditor screen is very close to this, maybe you could just make these updates to it? Hopefully this wouldn't be a paid bigbox feature, but I wouldn't blame you for making it so, perhaps the import export piece anyway.

BTW, thank you for the great product!!!

Comments (1)

  1. Log in to comment