Thanks for your answer! I tried to debug it, but I've found the implementation kind of chaotic (not to offend anybody...it happens), so I reimplemented it (without some features) and it worked. And in my implementation I'm setting immediate mode always. When I have a bit of time I'll if the behaviour of vtkResliceImageViewer changes if I set the hair mode to immediate.<div>
<br></div><div>Thanks again,</div><div><br></div><div>Federico<br><br><div class="gmail_quote">On Fri, Jul 27, 2012 at 12:26 PM, Jean-Hugues Royer <span dir="ltr"><<a href="mailto:jhroyer@joher.com" target="_blank">jhroyer@joher.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
This is a late reply but I think you might run in the recently problem of deprecated OpenGL list.<br>
<br>
Basically when you are using a vtkPolyDataMapper, which is probably what your crosshair widget is using, you need to set ImmediateModeRenderingOn() to avoid hidden/black rendering.<br>
<br>
The problem is explained in this vtk developpers post:<br>
<br>
<a href="http://www.vtk.org/pipermail/vtk-developers/2012-June/011832.html" target="_blank">http://www.vtk.org/pipermail/<u></u>vtk-developers/2012-June/<u></u>011832.html</a><br>
<br>
I'm not using vtkResliceImageViewer, but the one I coded had the same issue until I enabled immediate mode rendering.<br>
<br>
It would be a good idea to try to set it manually if you access the crosshair mapper or by patching the source of the widget...<br>
<br>
Regards.<br>
<br>
</blockquote></div><br></div>