-
-
Notifications
You must be signed in to change notification settings - Fork 446
Layer controls widgets refactor #7355
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
base: main
Are you sure you want to change the base?
Conversation
Note: Some code clean up and docstrings changes are still needed but marking this as ready for review in case someone wants to give feedback |
Co-authored-by: Grzegorz Bokota <bokota+github@gmail.com>
a09639c
to
2a7735c
Compare
bd482ea
to
e50515e
Compare
@dalthviz should we pull this out of draft? Thank you for the continuous updates, I know it's not easy!!! 🙏 |
Hi @jni! I think there are still a couple of comments to address before this is ready for another review so probably is still better to leave this as a draft. I would say that the three main things to do are:
Also, I think I will probably have some time over the weekend to work on those things but if someone has time and wants to tackle those right now go ahead :) |
Hi there @willingc ! I don't think I will have time to do further changes here before Friday so leaving this for 0.7.0 makes sense to me 👍 |
…napari into layer_controls_widgets
References and relevant issues
Related with PR #6219
Description
This takes out some of the refactoring effort proposed over PR #6219 (creation of classes that encapsulate specific widget controls for logic reusage and provide base methods to add those widgets to layer controls classes).
Dependencies/imports diagram related with layer controls
Source code directory layout related to layer controls
Notes
For the moment,thisonlycovers the shape layer, labels layer, image layer, surface layer and tracks layer controlscolormap
attribute (widgets insideqt_colormap_control
), the layerrendering
attribute (widgets insideqt_render_control
) or the layeredge_color
/current_edge_color
(widgets insideqt_edge_color
)IndexError: index -3 is out of bounds for axis 0 with size 2
) #7393shading
attribute is modified programatically #7394raise
is being call when handling aTypeError
exception (when a edge color mode doesn't correspond with the current valid values). This causes the error to be shown to the user eventhough a fallback to put set a proper value is done.Could it make sense to make an issue about that? 🤔