Talley Lambert
Talley Lambert
and for reference... "reclaiming" the keypress events from vispy and simply redirecting them to QtViewer can look like this ```python # napari/napari/_vispy/canvas.py class VispyCanvas(SceneCanvas): ... # overriding keyPressEvent and keyReleaseEvent...
> You could use simple [event.ignore()](https://doc.qt.io/qt-6/qevent.html#ignore) and Qt will automatically call key handling in parent class. There is no need to call basic implementation from QWidget. ok ... I did...
Not a dumb question! 😂 Let's try without?
given how frequently this argument is highlighted in our docs (it's literally the first example in the readme) we can also discuss whether we want a better alternative to the...
@sofroniewn, @jni ... would like your eyes on this one
There's two variants to consider here: I thought it felt better to use `from napari.utils import split_channels` than `from napari.layers.utils import split_channels`, but moving that ended up being somewhat invasive....
after chatting with @jni on zulip, given how frequently this is used, we both thought it warrants a convenience method: so @napari/core-devs, please vote on the name: - 🚀 =...
> I'd much rather we change our examples in that case, do you want it as shown in the first example? ```python from napari.utils import split_channels for (ch, kw, _)...
> The simplest rationale is that add_* methods should be reserved for each of our primitive layer types and having add_multichannel_image goes against that. perhaps it shouldn't start with `add_*`...