Kai Mühlbauer

@briancurtin Thank you for the comment. Especially the idea with the 'arg_checker' is charming. This will keep the flexibility at the user side and the simple code in the package....

@ajcr Thanks for looking into this. I'll definitely try your suggestion using `rolling.Apply(array, window_size, operation=np.nanmedian))`.

> Also, do you know how to turn off a Marker object so that the previously marked objects would disappear? You can disable drawing of visuals by setting: `visual.visible =...

> Do I need to instantiate a new view.scene for every image that I browse through? If you just change the image you can use the `.set_data()` method.

If you use `.set_data()` the image will automatically updated to the new data you provided. So disable/enable visibility would depend on your use-case, but it's not needed from my experience.

> Sorry, I meant the markers .visible. I got it to work by keeping track of the previous state. Each image has its own markers. No problem, glad you got...

OK. As David already mentioned, you could add a `STTransform` with a decent z-offset. Would it be possible for you, to strip your code down to a minimal example (no...

@mariakesa You could try to combine the [markers example](https://github.com/vispy/vispy/blob/master/examples/basics/visuals/markers.py) and [image example](https://github.com/vispy/vispy/blob/master/examples/basics/visuals/image_visual.py). I'm currently having issues with my installation so can't come up with a minimal example myself.

@mariakesa Just checking in. Did you solve your issue? It would be interesting to know how you got it working.

@almarklein Is this issue and #799 still relevant? If so, it would be good to get a bit more detail on both issues.