That sounds like a good way to handle it, especially since I have a better internet connection and I now have multiple instances opened at once.
One thing though, does it have to be a different switch to add a queue?
The goal is to be able to add files to the queue of a running instance in case a transfer I previously launched isn't finished yet and I have no way to know if that's the case or not.
Since I would need a new instance if the previous one got closed, simply launching it with the full parameters, checking if there's already an instance with the same id and queing the queue file if it exist or starting a new instance if it doesn't would be best.
So you'd run, for example:
Code:
FLASHFXP.EXE -id="demo" -c2 -get "some_path\auto_created_queue_file.fqf"
and then you'd run before the previous one is done uploading:
Code:
FLASHFXP.EXE -id="demo" -c2 -get "some_other_path\auto_created_queue_file.fqf"
and it would check if there's a FlashFXP instance already open with the "demo" id, add the files from "some_other_path\auto_created_queue_file.fqf" to the already running "demo" flashFXP instance and either update the running instance using the other switches(if I had specified something different) or not, depending on what you think is best(I'm fine with either).
And if there's no running instance, it would simply start a new one after checking using the parameters specified in the second command.
If it has to be a different switch like your example, we'd also need a way to check if an instance with a specific id is already running and have some kind of feedback to know the answer.
Edit: Or we could simply get an error return code that would let us know there isn't one running now that I think about it since it would check when launched anyway.