From: "Mehamli, Tristan" on

Finally, a SetCurrent() was missing before the rendering which is not required under msw.
Hope this helps.

-----Original Message-----
From: Mehamli, Tristan [mailto:tmehamli(a)mc.com]
Sent: lundi 27 août 2007 09:17
To: wx-users(a)lists.wxwidgets.org
Subject: RE: GLXBadDrawable

No none has an explanation on this? No one can help me on this?

-----Original Message-----
From: Mehamli, Tristan [mailto:tmehamli(a)mc.com]
Sent: jeudi 23 août 2007 16:18
To: wx-users(a)lists.wxwidgets.org
Subject: GLXBadDrawable

Hi everyone,

I'm currently testing my application under linux (RHEL5 64bits) using gcc 4.1, GTK+ 2.10 and wxGTK 2.8.4.

As soon as my app is starting nothing is showed, it aborts with this
message:
The program 'SoWxApp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadDrawable'.
(Details: serial 502 error_code 130 request_code 128 minor_code 11)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)

Of course if I comment the calls to my opengl render area, there's no problem. So it definitly has something to do with it. A previous mail on a similar error was posted by Jonathan Haws the 07/16. I verified several times that I'm calling SwapBuffers just when it's needed and not more than once.
Can someone help me on this?

Regards,
TM.



---------------------------------------------------------------------
To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org
For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-users-unsubscribe(a)lists.wxwidgets.org
For additional commands, e-mail: wx-users-help(a)lists.wxwidgets.org