Page 2 of 2

Re: Auto insert EnVar in path after select from dialog

Posted: 2022-05-05, 16:18 UTC
by ghisler(Author)
It ran into troubles because I have TC installations in multiple directories (32-bit and 64-bit in separate compiler directories, various older versions for testing), so when I used %COMMANDER_PATH% for a plugin, it wasn't found by the other installations. So doing this automatically may be a bad idea even for advanced users.

Re: Auto insert EnVar in path after select from dialog

Posted: 2022-05-05, 21:30 UTC
by Fla$her
ghisler(Author) wrote: 2022-05-05, 16:18 UTCSo doing this automatically may be a bad idea even for advanced users.
Please pay attention to my earlier statement:
Fla$her wrote: 2020-02-05, 15:36 UTCIn this case, it was necessary to write initially about the optionality of such an auto-replacement. The main thing is to add the opportunity itself.
Wouldn't an additional option solve this problem?

Re: Auto insert EnVar in path after select from dialog

Posted: 2022-05-19, 03:15 UTC
by thomasmolover
In fact, I don't think it is that complicated. This requirement is just to quickly switch between different dialog boxes under the same setting interface - for example, I also want to add some shortcut keys. As for the variables inside, I think I can directly extract the setting path in the corresponding dialog box.
For unset, the original behavior is maintained, but this does not conflict with the action of the selection dialog.

Re: Auto insert EnVar in path after select from dialog

Posted: 2022-05-20, 14:01 UTC
by Fla$her
2thomasmolover
I didn't understand what you were writing about here at all.
Here we discuss the variables that are necessary for portability and versatility.

Re: Auto insert EnVar in path after select from dialog

Posted: 2023-05-13, 20:29 UTC
by Fla$her
Bump for v.11.00