Windows Default Install Path
-
FrozenTundraDJ
- Posts: 20
- Joined: Fri Sep 28, 2018 11:09 pm
- Real Name: Austin Arbour
I would like to request that the Windows version follows best practice for the install path of using the Program Files directory rather than defaulting to C:\QLC+.
-
kproth
- Posts: 76
- Joined: Sun Jan 01, 2023 2:31 pm
- Real Name: Kevin Roth
If that were done, doesn't it also default to savings its .qxw files into the application's directory? That would have to change too, since you can't write to the Program Files directory without admin rights. And, does the installer place the start menu shortcut under the shared start menu folder or the user-specific one?
-
GGGss
- Posts: 3014
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Austin,
I am very happy with the non-program-files approach of QLC+.
In the other case, you will erratic start looking in c:\program_data (hidden directory) for the fixture definitons, input defintions, ... This will complicate things for the user.
AND: QLC+ is a multi-O.S. solution, so you want Linux to put its file where now?
I am very happy with the non-program-files approach of QLC+.
In the other case, you will erratic start looking in c:\program_data (hidden directory) for the fixture definitons, input defintions, ... This will complicate things for the user.
AND: QLC+ is a multi-O.S. solution, so you want Linux to put its file where now?
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
janosvitok
- Posts: 1316
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
QLC+ on different platforms uses different paths, according to respective conventions.
See https://github.com/mcallegari/qlcplus/b ... es.pri#L73 and following lines.
-
kproth
- Posts: 76
- Joined: Sun Jan 01, 2023 2:31 pm
- Real Name: Kevin Roth
Actually, the install path in question is in the .nsi file used by makensis to build the installer:janosvitok wrote: ↑Mon Jun 12, 2023 12:39 pm QLC+ on different platforms uses different paths, according to respective conventions.
See https://github.com/mcallegari/qlcplus/b ... es.pri#L73 and following lines.
https://github.com/mcallegari/qlcplus/b ... t5.nsi#L19
I think the INSTALLROOT variable you linked to is only used by 'make install'...
And according to the certification requirements below, windows desktop apps are supposed to install to %ProgramFiles% (or %ProgramFiles(x86)% for 32-bit apps)...
https://learn.microsoft.com/en-us/windo ... sktop-apps
-
mcallegari
- Posts: 4683
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
I thought about this already and I think QLC+ will stay like this for these reasons:
1- the current installer can be executed without administrative priviledge which is gold on corporare PCs (for example in my workplace).
2- Limitations of #1 are:
- file associations: installer needs to modify the Windows registry which is possible only as admin
- network protocol requires access to network interfaces
3- installer can always be executed as admin (most of home PCs have a single admin user anyway) and you can opt to install QLC+ even in Program Files folder
So yes, in 2023 it is a bit awkward to install on a custom path but it has its advantages too
1- the current installer can be executed without administrative priviledge which is gold on corporare PCs (for example in my workplace).
2- Limitations of #1 are:
- file associations: installer needs to modify the Windows registry which is possible only as admin
- network protocol requires access to network interfaces
3- installer can always be executed as admin (most of home PCs have a single admin user anyway) and you can opt to install QLC+ even in Program Files folder
So yes, in 2023 it is a bit awkward to install on a custom path but it has its advantages too