Peter Sobolewski

Maybe we can actually close this? - We don't use RGB by default but instead CMY - we con't have jet or rainbow -- HSV isn't great, but we do...

> Or you would like to implement only if that data is not downsampled in a given dimension? I assume this would be the use case. So something like (2,...

I just tested with a Split RGB and it does work:

However, trying to merge to stack or merge to RGB afterwards fails: ``` --------------------------------------------------------------------------- IndexError Traceback (most recent call last) File ~/Dev/miniforge3/envs/napari-060/lib/python3.12/site-packages/app_model/backends/qt/_qaction.py:59, in QCommandAction._on_triggered(self=QMenuItemAction(MenuItem(when=None, group='5_spl...tle=None, toggled=None), alt=None), app='napari'), checked=False) 55...

Regular split also works. I did move axis the RGB image into (3, Y, X) and then Split Stack. But again merge does not.

I renamed the issue, but I think we should close this and make an issue to fix merging? or update the OP. Unless @jni really did intend to split along...

Split and Merge (https://github.com/napari/napari/pull/8025) now both work for the most typical mulitscale use case via the contextual.

~~Dupe? https://github.com/napari/napari/issues/5933 😜~~ Edit: derp, I see it's subtly different.

> with the napari screen maximized but not full screen Is this a windows thing? If so, might be worth putting that in a label or the title to make...

I understand that part. I have a 2 and/or 3 monitor setup for work and tested with that.