Peter Sobolewski

I've tagged a few more with the `migrate` tag that seem worth transferring. Maybe you can glance at them @melissawm and @lucyleeow ?

I can transfer them, just wanted to let people see them first, so that we don't need to transfer any back 😊

I'll add another aspect to this issue: Changing the theme of one viewer changes the theme of all viewers. Try: ``` import napari viewer1 = napari.Viewer() viewer2 = napari.Viewer() viewer2.theme...

> > Both viewers will change to dark. > > @psobolewskiPhD Yes. This is intentional and allows us to simply style additional windows (opened ex from the viewer) and keep...

> But this may be unintuitive for a new user. In most of the applications that I meet, when allowing toggle theme from the view menu, it happens globally. I...

Works perfectly—I did have to `napari --reset` though, maybe due to a clash with my keybinds? I may have set/unset that keybind before.

Good catch! When keybinds were overhauled in https://github.com/napari/napari/pull/3072 the docs weren't updated. Maybe should just add back all the old mnemonic keybinds as secondary keybinds, to match the docs?

> Related: it would also be better for the discoverability of shortcuts if the docs were substantially improved. There is some information here, but it's not very readable: https://napari.org/stable/guides/preferences.html?highlight=shortcuts#shortcuts Yup,...

Here's what it looks like to me anyways: Live: RC4 (same with `main`): Git bisect indicates this commit: https://github.com/napari/napari/commit/d4b28364a2d1cc832b1eba06cc33ab5849514f62 CC: @perlman `layer.color_mode = "auto"` also makes the cube visible again....

> The error was introduced in #4935 Yup, I also did a git bisect—what an awesome tool! my favorite git thing I think—posted above 😉 >Git bisect indicates this commit:...