09-15-2015, 10:45 AM
Hi Mikkie,
The shortcut parameters are a remnant from the pre-Scense 5 era and they are still available for compatibility reasons. Before Scense 5 the shortcut parameters were the only way to tell Scense what to do when a Scense shortcut was clicked. The shortcut parameters were part of the command-line inside the actual shortcut (the .lnk file). The command line in the shortcut is limited in length and this caused problems. In Scense 5 the 'Enhanced Shortcut' was introduced where the shortcut details were stored in the database. The shortcut GUID was introduced as part of the command-line in the Scense shortcut so the Scense runtime could easily find the appropriate (link) parameters in the database. You can still use the shortcut parameters to pass special arguments to the application event.
About your question:
No the shortcut parameters cannot be used to set a compatibility configuration for a shortcut.
The program compatibility is not stored inside the shortcut (the .lnk file), but instead it is stored in the registry.
"HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" or it's HKLM equivalent.
You should see what is stored there and try to replicate it with a Scense registry action.
The shortcut parameters are a remnant from the pre-Scense 5 era and they are still available for compatibility reasons. Before Scense 5 the shortcut parameters were the only way to tell Scense what to do when a Scense shortcut was clicked. The shortcut parameters were part of the command-line inside the actual shortcut (the .lnk file). The command line in the shortcut is limited in length and this caused problems. In Scense 5 the 'Enhanced Shortcut' was introduced where the shortcut details were stored in the database. The shortcut GUID was introduced as part of the command-line in the Scense shortcut so the Scense runtime could easily find the appropriate (link) parameters in the database. You can still use the shortcut parameters to pass special arguments to the application event.
About your question:
No the shortcut parameters cannot be used to set a compatibility configuration for a shortcut.
The program compatibility is not stored inside the shortcut (the .lnk file), but instead it is stored in the registry.
"HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" or it's HKLM equivalent.
You should see what is stored there and try to replicate it with a Scense registry action.