-
-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Problem
parseInputMacroArg (used by input.keyboard and input.gamepad commands) processes characters one at a time and has no SymExpressionStart handling. This means expressions like [[active_media.launcher_id]] are split into individual characters instead of being evaluated.
In contrast, parseArgs (used by all other commands) correctly handles SymExpressionStart at line 341 of arguments.go and delegates to parseExpression.
Expected behavior
**input.keyboard:[[active_media.launcher_id]] should evaluate the expression first, then pass the result through the input macro parser. For example, if active_media.launcher_id evaluates to "my-kodi", the macro parser should see my-kodi and process each character as a key press.
Suggested fix
Either:
- Add
SymExpressionStarthandling toparseInputMacroArg(likeparseArgsdoes), or - Pre-process expressions before the input macro parser runs
Option 1 is probably cleaner since it keeps expression handling consistent across all arg parsers.
Affected commands
input.keyboardinput.gamepad- Any future commands using
isInputMacroCmd/parseInputMacroArg