Johannes Soltwedel

Hi, I just stumbled over this issue because it's what I am trying to do with various workarounds. I think this would greatly ease (in the context of napari) to...

> I do not understand what you expect to have in the interface. The core problem with annotation np.ndarray is that it does not contain any context information. Hi @Czaki...

> The main thing thing I would not want to support here is simply "ignoring" np.ndarray if it happens to come in a union with something that magicgui recognizes. Thanks...

Hi @giovp and @ivirshup , thanks for the feedback! > I'd argue a fig and ax would be needed when multiple plots are plotted. Tbh I was coming more from...

Where new functions are concerned I think I would restrict myself to making existing functions available in the Napari plugin, so I cannot yet tell whether there is an urgent...

Hi @kevinyamauchi , cool to see you on board here :) > or make a separate library that libraries like napari-clusters-plotter and napari-spatial-statistics can depend on. We were discussing with...

Hi @kevinyamauchi @giovp , if you are interested - I created a zulib thread [here](https://napari.zulipchat.com/#narrow/stream/309872-plugins/topic/general-purpose.20plotting.20in.20Napari) :)

Hey @JacksonMaxfield , thanks for the fast reply. The spatial relation of single mosaic tiles to the whole image is quite important on this one, but the proplem is not...

Hi @JacksonMaxfield , Thanks for the reply! I agree that it's a very reasonable approach to choose daskability (is that a word?) over exact pixel dimensions. The difference in dimensions...

>Thinking aloud, I think there is room for quick-n-dirty put tile together preview of mosaics—as long as it is correct & responsive—and proper stitching. Love the idea of a warning...