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

Board/Library Manager "Versions" not intutitive. #1924

Closed
3 tasks done
Tracked by #1927
bdowling opened this issue Feb 28, 2023 · 1 comment · Fixed by #1927
Closed
3 tasks done
Tracked by #1927

Board/Library Manager "Versions" not intutitive. #1924

bdowling opened this issue Feb 28, 2023 · 1 comment · Fixed by #1927
Assignees
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: enhancement Proposed improvement

Comments

@bdowling
Copy link

bdowling commented Feb 28, 2023

Describe the request

The behavior of the version drop down immediately changing (dropping the installing version) and highlighting the prior version after clicking install does not seem very intuitive at first use, it tripped me up initially before recognizing what it was doing.

Describe the current behavior

When you select to install the latest version of a library or board plugin, the version drop-down immediately changes to the prior version. This can make the user think they are installing the older version. You have no visual indication of "Installing version x.x" in the Manager window, the user would have to be monitoring the Output window.

Once it is installed of course, the "Version x.x Installed" appears, but is separated by the description from the version drop-down and install buttons. The drop-down the no longer lists the installed version.

I feel it would be more intuitive if the latest version remained in the drop-down, with "Installing or Installed" on the same line when the drop-down is expanded, but of course then the install button should be grayed out if the installed version is selected.

Just a thought/experience I wanted to share..

Arduino IDE version

2.0.4

Operating system

N/A

Operating system version

n/a

Additional context

No response

Issue checklist

  • I searched for previous requests in the issue tracker
  • I verified the feature was still missing when using the latest nightly build
  • My request contains all necessary details
@bdowling bdowling added the type: enhancement Proposed improvement label Feb 28, 2023
@per1234 per1234 added the topic: code Related to content of the project itself label Feb 28, 2023
@kittaakos kittaakos self-assigned this Mar 1, 2023
@bdowling
Copy link
Author

bdowling commented Mar 2, 2023

One simple fix for this that I thought of while using the widgets again:

Change the "Install" button.

  1. When the user first clicks it, change it to Installing, leaving the version in the drop-down.
  2. Once installed, change it to Installed but grayed-out or highlighted in blue as the Installed box is. Or this could just replace the "Version x.x.x Installed/Uninstall" button where the "Installed" changes to "Uninstall" on hover-over, letting the version/button do double duty and not actually needing the other line to appear.
  3. If the user changes drop-down to a different version after being installed, re-enable the "Install button", but it feels like it should have different wording, "Downgrade", "Upgrade" if you grok the version semantics, otherwise "Change Version" generically.

kittaakos pushed a commit that referenced this issue Mar 3, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 3, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 7, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 9, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 9, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 9, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
kittaakos pushed a commit that referenced this issue Mar 13, 2023
Closes #19
Closes #781
Closes #1591
Closes #1607
Closes #1697
Closes #1707
Closes #1924
Closes #1941

Signed-off-by: Akos Kitta <[email protected]>
@kittaakos kittaakos added the conclusion: resolved Issue was resolved label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants