Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: frontend: vehicle-setup: failsafes: disable unused parameters #2786

Open
1 task done
ES-Alexander opened this issue Jul 5, 2024 · 0 comments
Open
1 task done
Labels
core Issue related to BlueOS-core enhancement New feature or request triage Needs triage from developers ui User Interface feature

Comments

@ES-Alexander
Copy link
Collaborator

ES-Alexander commented Jul 5, 2024

Current behaviour

From #2748, the interface is consistent whether a failsafe is configured to do something or as disabled. This isn't specifically problematic, but it could be more intuitive if there was visual feedback about which failsafes are 'active'.

Expected or desired behaviour

Setup parameters for a failsafe (and possibly the whole failsafe card) should be greyed out and/or disabled when the corresponding failsafe Action is set to Disabled, with only the Action remaining interactive and with normal colours/shades. This would draw attention to that box, and make it more obvious that the other available parameters aren't actually having an effect when the relevant Action is not configured to do anything.


Originally raised in this comment.

Prerequisites

  • I have checked to make sure that a similar request has not already been filed or fixed.
@ES-Alexander ES-Alexander added enhancement New feature or request core Issue related to BlueOS-core ui User Interface feature triage Needs triage from developers labels Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Issue related to BlueOS-core enhancement New feature or request triage Needs triage from developers ui User Interface feature
Projects
None yet
Development

No branches or pull requests

1 participant