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

Add default values of numeric fields or dropdown menues to the tooltips #3273

Open
Scuba4436 opened this issue Jan 24, 2023 · 2 comments
Open

Comments

@Scuba4436
Copy link

Is your feature request related to a problem? Please describe

The content of the tooltips is not very consistent in terms of default values. For some values and choices (like dropdown selections), the default value is mentioned in the tooltips, sometime even "hidden" in the explanation text. For some values, no defaults are mentioned in the tooltip. To reset a single specific value, you have to go to the CLI, where the default values are displayed.

Describe the solution you'd like

Add the default value of all numeric fields or dropdown menues in the Configurator to the corresponding tooltip. In a consistent way, like this for motor idle: Default: 5.5
Add the default value at the end of each tooltip (for conistency). Eventually format the default value in bold, to get a visual difference with the existing text in the tooltip. If a tooltip is missing, add a tooltip with the default value only.

Describe alternatives you've considered

Another solution could also be: add a "reset" button next to a value field or dropdown menue. Like 3D printing slicer software does. Often, there is a "reset to defaults" button just to the right of a value field, where you can reset a manually changed value back to defaults.

Other information

No response

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2023

Issue closed automatically as inactive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants