Repository navigation
Add release notes for v0.10.0rc0 - #1165
Merged
Merged
Conversation
github-actions
Bot
added
the
documentation
TimMonko
approved these changes
Oct 20, 2026
TimMonko
left a comment
TimMonko
left a comment
Member
There was a problem hiding this comment.
Looking great so far! I always enjoy how you include the narration and the little code snippets -- they are digestible but so powerful!
|
|
||
| ### Cursor crosshair | ||
|
|
||
| Ever use the [grid mode](https://napari.org/stable/gallery/grid_mode.html#grid-mode) for your miltichannel data but then struggle to know where you're clicking? Struggle no more! You can now enable the new crosshair overlay ([#8017](https://github.com/napari/napari/pull/8017)) to always locate your exact position in every viewbox. |
Member
There was a problem hiding this comment.
Suggested change
| Ever use the [grid mode](https://napari.org/stable/gallery/grid_mode.html#grid-mode) for your miltichannel data but then struggle to know where you're clicking? Struggle no more! You can now enable the new crosshair overlay ([#8017](https://github.com/napari/napari/pull/8017)) to always locate your exact position in every viewbox. | |
| Ever use the [grid mode](https://napari.org/stable/gallery/grid_mode.html#grid-mode) for your miltichannel data but then struggle to know where you're clicking? Struggle no more! You can now enable the new crosshair overlay ([#8017](https://github.com/napari/napari/pull/8017)) to always locate your exact position in every viewbox. | |
| Do you also struggle to figure out where your cursor is located when in 3D view? | |
| The crosshair overlay helps with that too! | |
| Unfortunately, it doesn't help make positioning the cursor any less confusing. | |
| For that, we ask for your help in making napari better! |
Contributor
Author
There was a problem hiding this comment.
I think we should shy away from that for now, as we figure out whether the cursor as a stateful model is even a thing we want to keep around. Also, it really is just "bad" in 3d for now, so let's not bring attention to it XD
Member
There was a problem hiding this comment.
Ok but I'm just here to say miltichannel -> mutichannel 😂
Contributor
Author
There was a problem hiding this comment.
miltichannel -> mutichannel
lol both wrong
TimMonko
reviewed
Oct 20, 2026
Comment on lines
+77
to
+84
| - Remove `PyQt5` support, part 1 ([#9650](https://github.com/napari/napari/pull/9650)) | ||
|
|
||
| ## New Features | ||
|
|
||
| - Add grid overlay ([#7827](https://github.com/napari/napari/pull/7827)) | ||
| - 2D/3D Crosshair overlay for cursor position ([#8017](https://github.com/napari/napari/pull/8017)) | ||
| - Allow plugins widgets to specify dock area ([#9526](https://github.com/napari/napari/pull/9526)) | ||
| - Add tabify default for plugin widgets ([#9707](https://github.com/napari/napari/pull/9707)) |
Member
There was a problem hiding this comment.
we want to keep an eye on wahtever is happening in this section -- since it seems all these features are highlighted it just kidna floats
jni
reviewed
Oct 21, 2026
jni
reviewed
Oct 21, 2026
jni
reviewed
Oct 21, 2026
Comment on lines
+30
to
+32
| for layer in layers: | ||
| layer.units = 'nm' | ||
| layer.axis_labels = ['z', 'y', 'x'] |
Member
There was a problem hiding this comment.
Side note: we should probably update our sample data to have units and axis annotations now! 😅
jni
reviewed
Oct 21, 2026
jni
approved these changes
Oct 21, 2026
jni
left a comment
jni
left a comment
Member
There was a problem hiding this comment.
left minor fixes, but these look great! 😊
brisvag
added
the
Full docs preview/ready to merge
github-actions
Bot
removed
the
Full docs preview/ready to merge
brisvag
added a commit
to napari/napari-release-tools
that referenced
this pull request
Oct 23, 2026
I didn't realize at first what @TimMonko meant in [this comment](napari/docs#1165 (comment)), but now I get the issue. We should bump `Breaking changes` up above new features, since we usually have some text for `highlights`, we might have some for `breaking changes` but we'll likely not have any for the new features section (covered in highlights). In general, breakign changes should usually be high up.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
WIP, starting to add highlights.