I'm not sure if this is the same issue as #8 because I didn't install with .msix and it installed to Program Files, not WindowsApps. I think it is the same issue as #16
If Windows is installed on an NTFS volume, by default, the 'Program Files' folder can only be modified by members of the 'Administrators' user groups.
When trying to edit Bitwig, installed to Program Files, if you try to apply a theme to Bitwig, nothing happens.
If you run it through the command line, it spits out a bunch of errors.
The only way to fix this is to run the .jar file as administrator, which is only possible through the command line.
The best solution I have is to have a shortcut which sends the java command to the command line and runs as administrator, but it's not the easiest to set up.
I'm no dev, so I'm not sure how easy this would be to fix, if even possible. But it may be a good idea to at least add a message telling the user that it can't write to it for those who just run the .jar file and see nothing happen.
I'm not sure if this is the same issue as #8 because I didn't install with .msix and it installed to Program Files, not WindowsApps. I think it is the same issue as #16
If Windows is installed on an NTFS volume, by default, the 'Program Files' folder can only be modified by members of the 'Administrators' user groups.
When trying to edit Bitwig, installed to Program Files, if you try to apply a theme to Bitwig, nothing happens.
If you run it through the command line, it spits out a bunch of errors.
The only way to fix this is to run the .jar file as administrator, which is only possible through the command line.
The best solution I have is to have a shortcut which sends the java command to the command line and runs as administrator, but it's not the easiest to set up.
I'm no dev, so I'm not sure how easy this would be to fix, if even possible. But it may be a good idea to at least add a message telling the user that it can't write to it for those who just run the .jar file and see nothing happen.