-
Notifications
You must be signed in to change notification settings - Fork 17
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
Labels support for 0.4.19, points support for > 0.4.19 #239
Conversation
Tests pass locally. |
src/napari_spatialdata/_viewer.py
Outdated
@@ -539,12 +548,13 @@ def add_sdata_points(self, sdata: SpatialData, key: str, selected_cs: str, multi | |||
np.fliplr(xy) | |||
# radii_size = _calc_default_radii(self.viewer, sdata, selected_cs) | |||
radii_size = 3 | |||
version = get_napari_version() | |||
kwargs = {"edge_width": 0.0} if version <= packaging.version.parse("0.4.19") else {"border_width": 0.0} |
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.
I would say this solution is very temporary. 0.4.19 had some fixes with layer.events.data that will be important for the table widget so we would need to have 0.4.19 as constraint.
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.
Pre-emptive approval. I will check regarding the leaking problem. Might have to close the viewer prior to the test that is failing.
If you could add a todo perhaps to change the constraint to 0.4.19 or higher as soon as the table widget is in. In 0.4.18 there were quite some issues with layer.events.data
. In 0.4.19 there were still some but way less and we require these events for a properly working table widget.
Good to merge now. |
colormap
instead ofcolor
from0.5.0
border_xxx
instead ofedge_xxx
from the latestmain
(unreleased, >0.5.0
).This PR assumes that the next released version of napari is
0.5.0
(the current is0.4.19
). @melonora confirmed that this should be the case. If not, we need to adjust the version strings in this PR.Also, with @melonora we discussed if napari should automatically accept both the old argument and the new argument, as we do with our deprecation decorator approach: scverse/spatialdata#562. If it will, then we can remove the manual versions if-else checks added with this PR.