Windows: Ability to select the installation destination folder?

[g40]

Sort of critical here as Windows is booted from a (small) virtual disk which does not have large amounts of free space on drive c:

I can probably submit a PR if the installer is comprehensible.

BTW looks like very nice work. Thanks.

[dscb57]

I also think that this is an important issue. At the same time there needs to be a secondary installation section (as found on most installers) to allow selection of drive/folder for other larger content requiring more disk space, so as not to compromise the typically small size of the C:/ drive on a Windows PC, as well as avoiding the need to use symbolic links.

[falkTX]

its not just a matter of adding a custom install folder, it needs to store that location in the registry too so that the plugin version can know where to find the main files.
then also needing some code to read that registry entry when running in plugin mode (which needs native code, the plugin cannot use Qt like the standalone can)

[g40]

@falkTX I don't get it. Why would it need a registry entry and related code if installed elsewhere? From your comment it is not needed for an install to Program Files? I can understand it being added to the Windows path but that would apply to both scenarios?
Thanks for listening.

[falkTX]

it is needed in order to find the custom install location.

if the location is fixed then we dont need it anymore since we can assume where it got installed in

[g40]

@falkTX That's not very robust. Where in the codebase is the installation folder hard-coded?

[falkTX]

for windows its in the installer, that being https://github.com/mod-audio/mod-desktop/blob/main/utils/win64/win64-installer.iss