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.
This is an experiment in napari multi-canvas with an attempt to minimize breaking API changes. Tests are almost green!
There are some hacks and inefficiencies here, but in general it's working. The idea is you get a list of canvases (
_MultiCanvas
objects) as part of theViewerModel
. These canvases take ownership of thedims
andcamera
, allowing you to have multiple views of the same data.ViewerModel
maintainsdims
andcamera
properties that simply delegate to a primary/active (right now just the first) canvas.Since slice/view data currently lives on the layer model, the data must be resliced whenever the canvas changes. I'm going to start looking at this next.
Here's a brief demo:
Screen.Recording.2023-06-09.at.2.37.41.PM.mov