frontend: Input widgets should work for all Actions, not just HTTP ones #1535
Labels
Actions
enhancement
New feature or request
ui
UI related issues
widget-specific
A widget-specific issue
Current behaviour
Button input widgets can trigger a Cockpit Action, but they don't find any of the built in ones, or custom MAVLink or JS Actions, just the HTTP ones.
It reduces the value of having custom actions if you can't use them, and it's unintuitive to have some actions that work in one place and others that only work in others, especially when they don't have specific input requirements.
Expected or desired behaviour
General input widgets should just set data lake variables, and Action triggers (e.g. buttons) should be able to trigger any kind of available Action, not just HTTP ones.
Prerequisites
The text was updated successfully, but these errors were encountered: