I would like to move forward with the macro parametrization issue, for which I need to have an Agent that can serialize macro parameters. The same config mechanism can be easily used to implement action key/action labels.
Serialization:
- Arguments and labels would be added as a new action (
SerializedKeyActionType_Label = 39, SerializedKeyActionType_Argument = 40,) after the action they relate to.
- The format would be
<new macro action id> <kind-dependent data, typically a pascal-like string>
- example:
39 6 72 101 108 108 111 33
new action Id, compact read string length, "Hello!"
At the moment I am not convinced about any of the more complex proposals, so I would like to start with the minimal implementation / prototype of macro arguments. In this version, arguments would be referenced by $macroArg.1, $macroArg.2, ... .
Eventually, UI should allow the user to:
- add a label to any key
- to a macro action, add an arbitrary number of string macro arguments
For the testing/prototyping however, either of them is sufficient.
Firmware with a parser is implemented in
Related sources:
I would like to move forward with the macro parametrization issue, for which I need to have an Agent that can serialize macro parameters. The same config mechanism can be easily used to implement action key/action labels.
Serialization:
SerializedKeyActionType_Label = 39, SerializedKeyActionType_Argument = 40,) after the action they relate to.<new macro action id> <kind-dependent data, typically a pascal-like string>At the moment I am not convinced about any of the more complex proposals, so I would like to start with the minimal implementation / prototype of macro arguments. In this version, arguments would be referenced by
$macroArg.1,$macroArg.2, ... .Eventually, UI should allow the user to:
For the testing/prototyping however, either of them is sufficient.
Firmware with a parser is implemented in
Related sources: