Profiling PyOpenGL

[Kerim Borchaev ( WarKiD )]

Thanks you (and Georg) for clarifying this glutMainLoop thing.

But I didn't quite understand this phrase:
> forcing a request for a PyGame context in one of the OpenGLContext
> tests

(sorry for sounding dumb but I'm just starting to learn (Py)OpenGl )

Best regards,
 Kerim                            mailto:warkid at storm.ru

Friday, October 12, 2001, 5:23:38 AM, you wrote:

MF> Profiling the GLUT mainloop is rather difficult, as it's a C loop that only
MF> returns by executing a sys.exit (as mentioned by Georg).  You can, however,
MF> profile a PyGame-hosted PyOpenGL project fairly readily (PyGame doesn't have
MF> a native-code mainloop and it's Python one(s) can easily return as a normal
MF> function would).  I tested by forcing a request for a PyGame context in one
MF> of the OpenGLContext tests and then using profile.run to call MainLoop.

MF> Of course, swapping contexts is sometimes not an option, but if you're early
MF> in the project and PyGame is available on your platforms, using it might
MF> work for you.

MF> HTH,
MF> Mike

MF> BTW, posting to the SourceForge PyOpenGL list is probably the fastest way to
MF> get a response on PyOpenGL-specific questions like this.

MF> -----Original Message-----
MF> From: python-list-admin at python.org
MF> [mailto:python-list-admin at python.org]On Behalf Of Kerim Borchaev (
MF> WarKiD )
MF> Sent: October 11, 2001 04:03
MF> To: python-list at python.org
MF> Subject: Profiling PyOpenGL


MF> Hello python-list,

MF> why can't I profile PyOpenGL application using profile module?
MF> ...
MF> but it prints nothing unless I remove glutMainLoop call.

MF> Best regards,
MF>  Kerim                          mailto:warkid at storm.ru



MF> --
MF> http://mail.python.org/mailman/listinfo/python-list