It was recently discussed (in English) in the German forum:
ghisler(Author) wrote: 2022-10-07, 16:06 UTC
[Shortcuts] only work with numeric commands. When TC loads them, it converts cm_commands to their numeric values, and uses internal values for em_commands. The main reason is that menus don't support more complex content than just numeric values.
white wrote: 2022-10-09, 10:21 UTCIt was recently discussed (in English) in the German forum:
1 is a numeric value. It's not about the parameter, it's about the notation. If the notation was made functional (cm_exit(1), for example), then the problem would be solved. Or not?
Last edited by Fla$her on 2022-10-10, 11:07 UTC, edited 1 time in total.
white wrote: 2022-10-09, 10:21 UTCIt was recently discussed (in English) in the German forum:
1 is a numeric value. It's not about the parameter, it's about the record. If the record was made functional (cm_exit(1), for example), then the problem would be solved. Or not?
What do you mean with "record"
There is no such term releated to cm_commands.
The number 1 is a parameter for the cm_exit command and nothing else.
Windows 11 Home, Version 24H2 (OS Build 26100.4061) TC 11.55 RC2 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.4 x64
As said, currently shortcut are stored as command index.
You can at any time create an em_exit_1 which support your parameter request. Then do a shortcut,alias...
If this do not fit your needs, you can add a suggestion.
nsp wrote: 2022-10-10, 11:21 UTCAs said, currently shortcut are stored as command index.
There was no mention of indexes anywhere. But now I understood what was meant by numeric values. The interpretation of the commands themselves in Totalcmd.inc, not the type of view I wrote about.