Page 1 of 4

✅ Support for parameters when binding commands to hotkeys

Posted: 2023-05-05, 18:28 UTC
by Fla$her
Already wrote:
Fla$her wrote: 2023-05-04, 15:18 UTC Or somehow add on the Misc. page the ability to specify an internal command along with a parameter. It would be even better, given the number of such commands.
We have already accumulated 70 internal commands that support parameters. Some of them are in demand exclusively when creating hotkeys. At the moment, this is only possible after creating custom em_ commands. It would be great to save time and space in usercmd.ini if there was support for parameters with an additional field on the Misc. page.

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-05, 18:45 UTC
by petermad
Support ++ if feasible - and also for the ability to use commands with parameters in the .mnu file

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-05, 19:11 UTC
by jinsight
Support++

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-10, 17:20 UTC
by Fla$her
05.05.23 Added: Hotkeys defined via Configuration - Options - Misc now support commands with parameters (32/64)
At last! 😃 Thank you, Christian! 👍

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-10, 18:34 UTC
by AntonyD
2petermad
Dont' you know the LANG new ID for this text resource? String "&Parameters:"?

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-10, 18:56 UTC
by petermad
2AntonyD
5375="&Parameter:"

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-10, 19:25 UTC
by AntonyD
huge thanks!

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-12, 10:31 UTC
by sa16
A little remark. In the list of currently defined hotkeys, the command with the parameter is shown twice in the line. For example, - > cm_EditNewFile cm_EditNewFile 1.
It is also desirable to make the Parameters field unavailable for commands that do not support parameters.

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-12, 11:55 UTC
by AntonyD
It is also desirable to make the Parameters field unavailable for commands that do not support parameters.
I would treat it even as a bug((( - i mean current situation - when there is no such check.

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-12, 13:45 UTC
by petermad
the command with the parameter is shown twice in the line. For example, - > cm_EditNewFile cm_EditNewFile 1.
Not only twice in the line but also in two lines: https://tcmd.madsenworld.dk/keywithpatameter.png
It is also desirable to make the Parameters field unavailable for commands that do not support parameters.
Support+++ if feasible.

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-12, 13:56 UTC
by ghisler(Author)
the command with the parameter is shown twice in the line. For example, - > cm_EditNewFile cm_EditNewFile 1.
Confirmed, thanks!
Not only twice in the line but also in two lines: https://tcmd.madsenworld.dk/keywithpatameter.png
Seems to depend on the hotkey. I get it for F12 alone, but not for Ctrl+1.

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-12, 16:53 UTC
by petermad
Seems to depend on the hotkey. I get it for F12 alone
Then it was a lucky strike that it was F12 I tested it with :-)

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-17, 19:03 UTC
by sa16
14.05.23 Fixed: Configuration - Options - Misc: Hotkeys with parameters were shown incorrectly with command name doubled, e.g. cm_exit cm_exit 1 (32/64)
Thanks!

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-17, 21:52 UTC
by petermad
sa16 wrote: 2023-05-17, 19:03 UTC
14.05.23 Fixed: Configuration - Options - Misc: Hotkeys with parameters were shown incorrectly with command name doubled, e.g. cm_exit cm_exit 1 (32/64)
Thanks!
Yes, confirmed fixed in TC 11.00b3 :-)

Re: Support for parameters when binding commands to hotkeys

Posted: 2023-05-18, 02:30 UTC
by Fla$her
2ghisler(Author)
And what about the support of commands like LOADLIST[0], SAVETABS[2|L/R], etc.?
If you specify a path like "%COMMANDER_PATH%\Lists\test.txt", then writes an error or does nothing. Moreover, the quotes in the dialog are not displayed when the keys are selected again.