Joey Mukherjee wrote:
>
> Hello!
>
> I am not a member of the list so I would appreciate any replies coming
> to me as well as the list.
>
> I think I might have found and fixed a bug in Mesa v3.0. I use Mesa
> with VTK, the Visualization Toolkit, and in one routine I plot the VTK
> window onto a window of my X/Motif program. I tell VTK the window to
> draw into and it will call the appropriate Mesa routine to route it to
> the right window.
Could you provide more details of this? Is the X window created with
a visual which was returned by glXChooseVisual?
> However, if the window is a different depth than the default, Mesa can
> not get the correct visual depth to match up.
>
> To fix it, I changed the following line in src/X/fakeglx.c (336) in the
> routine find_glx_visual:
>
> if (VisualTable[i]->display==dpy && VisualTable[i]->vishandle==vinfo) {
>
> to
>
> if (VisualTable[i]->display==dpy && VisualTable[i]->visinfo==vinfo) {
> ^^^^^^^
>
> I think this is correct since visinfo is used more often than vishandle,
> the variables (visinfo and vinfo) look alike, and my program works! :-)
>
> I don't know if this will have any bad ramifications, but I don't think
> it will since it is still going through a list of potential visuals.
I have to be VERY careful about changing this code or other programs
are likely to break. I specifically added the vishandle business in
order to solve a problem related to how visuals are chosen by clients.
Remember, Mesa's GLX is just an emulation of the real thing. It's
impossible for Mesa's GLX to act exactly like a real GLX implementation.
Typically programs which try to do something tricky expose the
differences.
I'll need to know more about your code before I make any changes.
Thanks.
-Brian
----------------------------------------------------------------------
Brian Paul Avid Technology / Softimage [EMAIL PROTECTED]
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
