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
Describe the bug
In 6.3.3 a major command center ui update was introduced. Since the update there is no description of the config values anymore.
It would be nice if this could be readded in any way (as bugfix) because for some config values the description is indispensable.
Screenshots
Before:
Since 6.3.3
The text was updated successfully, but these errors were encountered:
dbeuchler
changed the title
Missing configuration description in CommandCenter since 6.3.3
Missing config-item description in CommandCenter since 6.3.3
Aug 15, 2024
The description should still be available as a tooltip by hovering over configuration options:
If that is not possible, I would agree with you on this being a bug.
When updating the UI, we didn't find a better spot to put these descriptions and tried to balance between having all the information at a glance and appropriate UX. We are happy about any ideas to improve this.
Hovering is not an option on touch UIs where we typically configure the modules. We do not have a mouse on production machine HMIs. Even the "open" and "expand" is not that clear. In a tree (what it looks like) a click on a tree-item typically "expands" it. In the command center it "opens" the item, thats misleading. Only with the arrow it can be expanded.
To be honest, I preferred the tabular view rather than having everything randomly arranged. Compare it in my screenshots, from my POV the view from 6.3.2 is cleaner and tidier with all necessary information
Describe the bug
In 6.3.3 a major command center ui update was introduced. Since the update there is no description of the config values anymore.
It would be nice if this could be readded in any way (as bugfix) because for some config values the description is indispensable.
Screenshots
Before:
Since 6.3.3
The text was updated successfully, but these errors were encountered: