mikeyww reported this issue:ghisler(Author) wrote: 2025-01-06, 08:13 UTCWhat does this have to do with parameter %S in this thread?The asterisk doesn't work when configuring the editor in TC.
Which happens because CreateProcess is used in this case and not ShellExecuteEx, resulting in an error message that is probably not very clear for the user. The same thing happens with the editor.mikeyww wrote: 2025-01-04, 18:15 UTC For some reason, %P%S does not work when running a program that has its file properties set to run the program as administrator.
Sorry for the confusion. I didn't mean only for the editor, but for cases where CreateProcess is used and it fails because the program has its file properties set to run the program as administrator.ghisler(Author) wrote: 2025-01-06, 08:13 UTC Anyway, I could switch to ShellExecuteEx for the editor, but I fear that it would break a LOT of configurations because programs and parameters are passed to it in a different way than with CreateProcess.
Furthermore, my suggestion was not to switch to ShellExecuteEx but I wondered if it would be possible, and if it is a good idea, to try executing the program using ShellExecuteEx when CreateProcess fails in this situation, instead of showing the error.
I was trying to find a more user friendly solution. Having to add an asterisk is not a solution in all cases, and how is the user supposed to know that he needs to do that? Another solution would be to show an error message that is clearer, if that is possible.