Peter Sobolewski

BTW: Is there some thought to napari providing/storing plugin preferences, so such behavior could be configured and stored between sessions?

I think the lint error requires updating flake8 to >5... Edit: Bumping flake8 to >5 seems to solve it, see: #64 https://github.com/AllenCellModeling/napari-aicsimageio/actions/runs/3352991816/jobs/5555501398

I've updated the widget based on @Czaki tips above, but sticking with magic_factory. The default values are now read from `core.py` rather than hard-coded. The widget values will now persist...

> > The default values are now read from `core.py` rather than hard-coded. > > The widget values will now persist between instances of the widget and napari sessions. >...

Right, I agree it could be confusing. The only way to change that behavior is to look for cached magicgui file and read & apply on-load.

But mutating the global state is the goal of this PR? It's not perfect, but it's not terrible? If the user wants to change the memory behavior of the reader,...

I've added a header to inform that the button needs to be pressed per session and changed the button text to use the verb `Apply` which I think is clearer.

> > it depends on what you want to have. I could provide some solution (simple use of appdirs for the correct location and json for serialize/deserialize). > > The...

This is just a fix for the bug/issue with the two-widget solution to multiscene files. Multiscene files open 2 widgets, with the scene selector needing values from the Scene Management...

I suspect this might be upstream? but can you do: `mamba repoquery depends libxml2` and `mamba repoquery whoneeds libxml2`