Lorenzo Gaifas

Closing up in favor of #5060.

Yes! This always annoys me, but I never got around to do anything about it. I'm not sure if there's a way to keep the data on vram on the...

Sorry, I meant "set view slice" :)

> This mostly looks great and I think could be merged pretty soon. Are there any high level parts you're more uncertain about or want particular feedback on? Or do...

> @andy-sweet and @brisvag do we want to try to push for merging this in 0.4.17 or would you rather leave until 0.5.0? I'm happy either way, excited to see...

I think I have addressed all the comments. @sofroniewn, @andy-sweet and @alisterburt, this is ready to be merged if you are happy with it. I can then focus on the...

Good progress! I incorporated the bounding box code from #4849, so now we also have an example of `LayerOverlay`! You can now test everything with this little snippet: ```py import...

> What if we add a convenience method to our utils that takes the viewer as an arg too? I don't know, I find this very unpythonic, which makes it...

In principle I'm fine with adding these lines in the example to get it to work; however as I mentioned in [the relative vispy issue](https://github.com/vispy/vispy/issues/1759), I don't think this is...

> but the disadvantage that mesh generation is now done each time the slice is changed This was the thing that got me stuck last time, as I was trying...