This PR adresses https://github.com/haesleinhuepf/napari-assistant/issues/18
Basically, instead of setting a default blending in napari-assisant Category class, the default is left as None such that it is handled by napari.
In napari 0.4.15 this will still be translucent but in napari 0.4.16 the new default is translucent_no_depth.
Specific categories that had previously hard-set translucent are also now just using the default, because it wasn't clear that they require depth checking (or not).
Categories that specifically set other blending modes, such as Mesh that set additive, continue to use their custom modes.
I tested this locally with both 0.4.15 and 0.4.16 testing a few of the different workflow operations, including the workflow originally posted in the napari issue https://github.com/napari/napari/issues/4618
Everything behaved correctly.
This PR adresses https://github.com/haesleinhuepf/napari-assistant/issues/18 Basically, instead of setting a default blending in
napari-assisantCategory class, the default is left asNonesuch that it is handled by napari. In napari 0.4.15 this will still betranslucentbut in napari 0.4.16 the new default istranslucent_no_depth. Specific categories that had previously hard-settranslucentare also now just using the default, because it wasn't clear that they require depth checking (or not). Categories that specifically set other blending modes, such as Mesh that setadditive, continue to use their custom modes.I tested this locally with both 0.4.15 and 0.4.16 testing a few of the different workflow operations, including the workflow originally posted in the napari issue https://github.com/napari/napari/issues/4618 Everything behaved correctly.