-
-
Notifications
You must be signed in to change notification settings - Fork 419
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 problem of missing plugin widgets after minimize napari #5577
Conversation
for more information, see https://pre-commit.ci
The PR seems to solve the issue for me when I test it locally. |
Codecov Report
@@ Coverage Diff @@
## main #5577 +/- ##
==========================================
+ Coverage 88.02% 89.52% +1.49%
==========================================
Files 610 610
Lines 51176 51194 +18
==========================================
+ Hits 45050 45829 +779
+ Misses 6126 5365 -761
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, I'm just wondering why the call was there in the first place.
Sorry y'all, I may have just added that and never second guessed that it wasn't necessary. I see that there is a toggle function on each plugin entry, so I am not sure if I missed that before and thought I needed to hide the widget when you toggle the menu item? I can't remember. Thanks for the fix @Czaki ! |
# Description <!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> * `INP` flake8-no-pep420 - The pep 420 is something that part of us may remember as the reason why napari stop working at some moment because of some problematic files in `site-packages`. * `PYI` flake8-pyi - better type annotation * `Q`, flake8-quotes - enforce quoting, but the rule Q000 is disabled (see #5589). * `RSE` # flake8-raise - simplify raise code by remove `()` when obsolete. * `RET` # flake8-return - simplify code readability by forcing proper return schema. * `TID` # flake8-tidy-imports - replacement for absolutify imports * `TRY` # tryceratops - enforce rules on exception raises like keeping in try only this that could raise exception (see why it could create problems in #5577). * `ICN` # flake8-import-conventions - enforce import convention for alias (like `import numpy as np`) * `RUF`# ruff specific rules - ## Type of change <!-- Please delete options that are not relevant. --> - [x] Maintenance # References <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> # How has this been tested? <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. ## Final checklist: - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html).
<!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> * `INP` flake8-no-pep420 - The pep 420 is something that part of us may remember as the reason why napari stop working at some moment because of some problematic files in `site-packages`. * `PYI` flake8-pyi - better type annotation * `Q`, flake8-quotes - enforce quoting, but the rule Q000 is disabled (see napari#5589). * `RSE` # flake8-raise - simplify raise code by remove `()` when obsolete. * `RET` # flake8-return - simplify code readability by forcing proper return schema. * `TID` # flake8-tidy-imports - replacement for absolutify imports * `TRY` # tryceratops - enforce rules on exception raises like keeping in try only this that could raise exception (see why it could create problems in napari#5577). * `ICN` # flake8-import-conventions - enforce import convention for alias (like `import numpy as np`) * `RUF`# ruff specific rules - <!-- Please delete options that are not relevant. --> - [x] Maintenance <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html).
# Description <!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> It removes the `setVisible` call triggered during minimalization of napari window ## Type of change <!-- Please delete options that are not relevant. --> - [x] Bug-fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # References <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> closes #5576 # How has this been tested? <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. ## Final checklist: - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html). @ppwadhwa You add this in #3331. Maybe I missed some use case and this need to be called in some scenarios. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
# Description <!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> It removes the `setVisible` call triggered during minimalization of napari window ## Type of change <!-- Please delete options that are not relevant. --> - [x] Bug-fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # References <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> closes #5576 # How has this been tested? <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. ## Final checklist: - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html). @ppwadhwa You add this in #3331. Maybe I missed some use case and this need to be called in some scenarios. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
<!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> * `INP` flake8-no-pep420 - The pep 420 is something that part of us may remember as the reason why napari stop working at some moment because of some problematic files in `site-packages`. * `PYI` flake8-pyi - better type annotation * `Q`, flake8-quotes - enforce quoting, but the rule Q000 is disabled (see #5589). * `RSE` # flake8-raise - simplify raise code by remove `()` when obsolete. * `RET` # flake8-return - simplify code readability by forcing proper return schema. * `TID` # flake8-tidy-imports - replacement for absolutify imports * `TRY` # tryceratops - enforce rules on exception raises like keeping in try only this that could raise exception (see why it could create problems in #5577). * `ICN` # flake8-import-conventions - enforce import convention for alias (like `import numpy as np`) * `RUF`# ruff specific rules - <!-- Please delete options that are not relevant. --> - [x] Maintenance <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html).
# Description <!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> It removes the `setVisible` call triggered during minimalization of napari window ## Type of change <!-- Please delete options that are not relevant. --> - [x] Bug-fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # References <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> closes #5576 # How has this been tested? <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. ## Final checklist: - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html). @ppwadhwa You add this in #3331. Maybe I missed some use case and this need to be called in some scenarios. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
<!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> * `INP` flake8-no-pep420 - The pep 420 is something that part of us may remember as the reason why napari stop working at some moment because of some problematic files in `site-packages`. * `PYI` flake8-pyi - better type annotation * `Q`, flake8-quotes - enforce quoting, but the rule Q000 is disabled (see #5589). * `RSE` # flake8-raise - simplify raise code by remove `()` when obsolete. * `RET` # flake8-return - simplify code readability by forcing proper return schema. * `TID` # flake8-tidy-imports - replacement for absolutify imports * `TRY` # tryceratops - enforce rules on exception raises like keeping in try only this that could raise exception (see why it could create problems in #5577). * `ICN` # flake8-import-conventions - enforce import convention for alias (like `import numpy as np`) * `RUF`# ruff specific rules - <!-- Please delete options that are not relevant. --> - [x] Maintenance <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html).
# Description <!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> It removes the `setVisible` call triggered during minimalization of napari window ## Type of change <!-- Please delete options that are not relevant. --> - [x] Bug-fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # References <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> closes #5576 # How has this been tested? <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. ## Final checklist: - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html). @ppwadhwa You add this in #3331. Maybe I missed some use case and this need to be called in some scenarios. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
<!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> * `INP` flake8-no-pep420 - The pep 420 is something that part of us may remember as the reason why napari stop working at some moment because of some problematic files in `site-packages`. * `PYI` flake8-pyi - better type annotation * `Q`, flake8-quotes - enforce quoting, but the rule Q000 is disabled (see #5589). * `RSE` # flake8-raise - simplify raise code by remove `()` when obsolete. * `RET` # flake8-return - simplify code readability by forcing proper return schema. * `TID` # flake8-tidy-imports - replacement for absolutify imports * `TRY` # tryceratops - enforce rules on exception raises like keeping in try only this that could raise exception (see why it could create problems in #5577). * `ICN` # flake8-import-conventions - enforce import convention for alias (like `import numpy as np`) * `RUF`# ruff specific rules - <!-- Please delete options that are not relevant. --> - [x] Maintenance <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html).
# Description <!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> It removes the `setVisible` call triggered during minimalization of napari window ## Type of change <!-- Please delete options that are not relevant. --> - [x] Bug-fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # References <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> closes #5576 # How has this been tested? <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. ## Final checklist: - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html). @ppwadhwa You add this in #3331. Maybe I missed some use case and this need to be called in some scenarios. --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
<!-- What does this pull request (PR) do? Why is it necessary? --> <!-- Tell us about your new feature, improvement, or fix! --> <!-- If your change includes user interface changes, please add an image, or an animation "An image is worth a thousand words!" --> <!-- You can use https://www.cockos.com/licecap/ or similar to create animations --> * `INP` flake8-no-pep420 - The pep 420 is something that part of us may remember as the reason why napari stop working at some moment because of some problematic files in `site-packages`. * `PYI` flake8-pyi - better type annotation * `Q`, flake8-quotes - enforce quoting, but the rule Q000 is disabled (see #5589). * `RSE` # flake8-raise - simplify raise code by remove `()` when obsolete. * `RET` # flake8-return - simplify code readability by forcing proper return schema. * `TID` # flake8-tidy-imports - replacement for absolutify imports * `TRY` # tryceratops - enforce rules on exception raises like keeping in try only this that could raise exception (see why it could create problems in #5577). * `ICN` # flake8-import-conventions - enforce import convention for alias (like `import numpy as np`) * `RUF`# ruff specific rules - <!-- Please delete options that are not relevant. --> - [x] Maintenance <!-- What resources, documentation, and guides were used in the creation of this PR? --> <!-- If this is a bug-fix or otherwise resolves an issue, reference it here with "closes #(issue)" --> <!-- Please describe the tests that you ran to verify your changes. --> - [ ] example: the test suite for my feature covers cases x, y, and z - [ ] example: all tests pass with my change - [ ] example: I check if my changes works with both PySide and PyQt backends as there are small differences between the two Qt bindings. - [ ] My PR is the minimum possible work for the desired functionality - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] If I included new strings, I have used `trans.` to make them localizable. For more information see our [translations guide](https://napari.org/developers/translations.html).
Description
It removes the
setVisible
call triggered during minimalization of napari windowType of change
References
closes #5576
How has this been tested?
as there are small differences between the two Qt bindings.
Final checklist:
trans.
to make them localizable.For more information see our translations guide.
@ppwadhwa You add this in #3331. Maybe I missed some use case and this need to be called in some scenarios.