mchwasisdj
To whom it may concern. Most of the time in my automation chain tasks, I encounter roadblocks due to some action script failling to accept arguments.
For instance I wanted to display the name of a custom_button based on the set variable name $btnNumber
get_text '`get_var $btnNumber & param_cast & custom_button_name`'
This fails because custom_button_name doesn't accept casted values. This functionality is important especially for display related tasks since you only need to update the value of the assigned variable rather than manually changing the action argument itself (custom_button_name 1)
This is just one example of many actions that neither accept arguments nor execute custom actions in backtick syntax
In my opinion, whenever possible, all actions that have parameters should be made to accept casted values or execute actions as their arguments
For instance I wanted to display the name of a custom_button based on the set variable name $btnNumber
get_text '`get_var $btnNumber & param_cast & custom_button_name`'
This fails because custom_button_name doesn't accept casted values. This functionality is important especially for display related tasks since you only need to update the value of the assigned variable rather than manually changing the action argument itself (custom_button_name 1)
This is just one example of many actions that neither accept arguments nor execute custom actions in backtick syntax
In my opinion, whenever possible, all actions that have parameters should be made to accept casted values or execute actions as their arguments
Posted Thu 17 Oct 24 @ 10:51 am