True, this is done without multithreading. It was on my list and I never looked at it again. Thank you for the reminder.phkb wrote: ↑Thu Sep 07, 2023 5:15 am I've had a bit more of a play with OoliteStarter, and have a couple more observations.
1. The UI can become unresponsive after clicking "Install" for an OXP (particular large ones). I found myself, on several occasions, wondering if I'd clicked the button at all. You should, at least, change the mouse pointer to an hourglass if you start a process that might taken more than a second (like downloading a file). Even better would be to queue the downloads into a background process, so I can keep clicking on other OXP's to download.
I guess in early versions it was my intention to allow having multiple versions in parallel, then activating/deactivating them as the player pleases.phkb wrote: ↑Thu Sep 07, 2023 5:15 am 2. By using OoliteStarter, you effectively break the built in Expansions manager. Because you put a file version into the name of every file you download, particularly into the ManagedAddOns folder, the Expansion Manager doesn't recognise them when it tries to update to a new version, effectively putting two versions into the ManagedAddOns folder. Then, when you go back to the main menu your screen gets filled with red warnings about there being two versions of the OXP present.
My suggestion is, if you're going to do anything inside the ManagedAddOns folder, do it in the same way as the Expansion manager does. Filename is the identifier with ".oxz". If you want to keep with the "@version" in the filename, do it in the AddOns folder, so that the Expansion Manager knows not to do anything with it.
The point is, I should be able to switch back and forth between using the ingame manager and OoliteStarter, without issues.
As I do not use the in-game manager the impact did not occur to me. But I will change it to be compliant.