Talley Lambert

Also want to point out that in addition to the `napari_write_` hookspecs, there is another one called [`napari_get_writer`](https://napari.org/docs/plugins/hook_specifications.html#napari.plugins.hook_specifications.napari_get_writer) that is called when saving multiple layers. This one is much more...

hi @dstabley, looks like you're in a somewhat old environment (based on that dask version error). I don't yet know what's going on here... but do you still do you...

oh actually... are you always _double_ clicking? I can actually see why that might cause this bug (which is fundamentally a problem with the way I'm clearing the viewer when...

ok thanks for checking. one more question: The stack trace indicates this is a bug in napari with removing a layer (and napari-omero attempts to remove all layers before loading...

definitely interesting. I can certainly see how that might create a problem. but i can't quite see how it would result in the `KeyError` in this stack track! 😅 i...

agreed... need to get back to those ROI saving functions. I _think_ we're gonna want (even a simple version of) #16 to be merged for that

all of the layers have a `data` attribute that holds the numpy array. so for example: ```python import napari import numpy as np with napari.gui_qt(): viewer = napari.Viewer() # just...

It’s definitely related to those two lines, but it should still not be an error to call remove_selected with no layers in the viewer. I need to look closer at...

Thanks a lot for the feedback! > exception pointing to SessionsStore.ctx ... Do you always have an active login when running? handling of the client/gateway is definitely the thing I...

oh i see. very cool.