Talley Lambert

> where would the method be since the proposal is for a top level `napari.imshow` method, you can put it pretty much anywhere you want, as long as you export...

> This is [a goal of the async slicing project, but it is not a must-have](https://hackmd.io/YN6Qhu18QriV-rtVI6Pzog?view#2-Clean-up-slice-state-and-logic-in-layers). I could imagine an implementation where we at least encapsulate the slice state to...

> @sofroniewn, I was following @tlambert03 suggestion. The layer-variable nested menu will require additional changes. see discussion in https://github.com/napari/napari/pull/3981#discussion_r790944932 This was discussed in a meeting at one point. @jni also...

> @tlambert03 I think we could use the approach we discussed yesterday of auto-generating a dialog when there is a command used in a menu with free parameters (in this...

this really is a challenging problem, and exposes some very deep brokenness with pydantic's handling of generics. I also find it very interesting :joy:, and some of the stuff I've...

sidenote: `Array`, really is a generic (by nature of having a `__class_getitem__`)... so it should also probably have `Generic` added to the bases (unless that breaks due to some metaclass...

one more thought: the goal of making pydantic work with parametrized generics is well-contained enough, and big enough, that you might consider extracting this (perhaps just temporarily) to it's own...

aaand one more thought :) we could take this in steps, and just try to solve `test_validate_evented_collections` first, and then `test_validate_parametrized_evented_collections` in a followup. the following appears sufficient to solve...

I'm starting to work on this... just adding some notes here on how this currently works for personal future reference: ### current keypress handling #### if a key is pressed...

> You mean stop using vispy conversion yeah, no vispy in the loop at all. > overwrite of QtViewerDockWidget.keyPressEvent to not accept event? in what I've described so far, I...