You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a feature relevant to companion itself, and not a module?
I believe this to be a feature for companion, not a module
Is there an existing issue for this?
I have searched the existing issues
Describe the feature
Custom variables and module variables can be of all valid JS types but the UI only features a textbox to initialize variables.
It should be possible to create user variables and initialize them also as an boolean, number, array or object.
Maybe the same UI elements like for the button text entry can be reused. If it is switched to text, the variable will be the entry as a string. If it is switched to expression, the variable value will be the JSON-parsed result of the entry.
I don't want to have full expression handling in the initialization, just the same or similar UX.
For places where variables are displayed in the UI they are usually converted to string, so the information of the type gets lost, even if you can perfectly use e.g. arrays in expressions. There should be a type indicator in the variables lists, so users can see and take advantage of variable types.
This request is not about type safety or type handling or type casting, only some UI tweaks.
Usecases
No response
The text was updated successfully, but these errors were encountered:
Is this a feature relevant to companion itself, and not a module?
Is there an existing issue for this?
Describe the feature
Custom variables and module variables can be of all valid JS types but the UI only features a textbox to initialize variables.
It should be possible to create user variables and initialize them also as an boolean, number, array or object.
Maybe the same UI elements like for the button text entry can be reused. If it is switched to text, the variable will be the entry as a string. If it is switched to expression, the variable value will be the JSON-parsed result of the entry.
I don't want to have full expression handling in the initialization, just the same or similar UX.
For places where variables are displayed in the UI they are usually converted to string, so the information of the type gets lost, even if you can perfectly use e.g. arrays in expressions. There should be a type indicator in the variables lists, so users can see and take advantage of variable types.
This request is not about type safety or type handling or type casting, only some UI tweaks.
Usecases
No response
The text was updated successfully, but these errors were encountered: