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

fix nested toolbar losing suboptions #2605

Merged
merged 1 commit into from
Dec 11, 2023

Conversation

kecnry
Copy link
Member

@kecnry kecnry commented Dec 11, 2023

Description

This pull request fixes the case where clicking a tool in the toolbar dropdown menu could lose the ability to select other suboptions. This was happening because the "has_suboptions" on the tool was originally set to False and not updated later when it then became the "primary" tool in the sub-menu. This fix is perhaps overly conservative, but ensures that the "has_suboptions" will always be kept up-to-date in advance of choosing a new tool.

This could be reproduced in specviz2d by selecting the non-synced zoom tool in either viewer.

image

Change log entry

  • Is a change log needed? If yes, is it added to CHANGES.rst? If you want to avoid merge conflicts,
    list the proposed change log here for review and add to CHANGES.rst before merge. If no, maintainer
    should add a no-changelog-entry-needed label.

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

  • Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
  • Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
  • Do the proposed changes follow the STScI Style Guides?
  • Are tests added/updated as required? If so, do they follow the STScI Style Guides?
  • Are docs added/updated as required? If so, do they follow the STScI Style Guides?
  • Did the CI pass? If not, are the failures related?
  • Is a milestone set? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone.
  • After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

@kecnry kecnry added bug Something isn't working 💤backport-v3.8.x on-merge: backport to v3.8.x labels Dec 11, 2023
@kecnry kecnry added this to the 3.8.1 milestone Dec 11, 2023
@kecnry kecnry force-pushed the nested-toolbar-fix branch from 1c209b5 to a7d7b04 Compare December 11, 2023 20:51
@kecnry kecnry marked this pull request as ready for review December 11, 2023 21:05
Copy link
Collaborator

@rosteen rosteen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@kecnry kecnry added the trivial Only needs one approval instead of two label Dec 11, 2023
@kecnry kecnry merged commit 0673de8 into spacetelescope:main Dec 11, 2023
16 of 17 checks passed
meeseeksmachine pushed a commit to meeseeksmachine/jdaviz that referenced this pull request Dec 11, 2023
@kecnry kecnry deleted the nested-toolbar-fix branch December 11, 2023 21:56
kecnry added a commit that referenced this pull request Dec 11, 2023
Co-authored-by: Kyle Conroy <kyleconroy@gmail.com>
@kecnry kecnry mentioned this pull request Jan 17, 2024
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working trivial Only needs one approval instead of two 💤backport-v3.8.x on-merge: backport to v3.8.x
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants