Following up:
I haven't installed the latest Linux NVidia driver yet. Several people on
Ubuntu Forums who have tried the 319.xx series drivers are reporting
problems more serious than new OpenGL threads causing their parent
applications to crash. I went down that path once before and spent over a
week undoing the mess. Until I have a good handle on how to try a video
driver in a way that allows me a quick and graceful recovery from trouble,
I will wait.
In the mean time, I have encountered the hanging problem in a Pyglet
example program which generates NO graphics beyond the original blank
window. It uses no clocks, nor does it use sound. I'm referring to the
very simple examples/events.py. Here's the entire code, minus comments:
===========================================
import pyglet
window = pyglet.window.Window(resizable=True)
@window.event
def on_draw():
window.clear()
window.push_handlers(pyglet.window.event.WindowEventLogger())
pyglet.app.run()
===========================================
This will happily print mouse events and keyboard events to the console for
a while -- and then, it freezes. As before, the window close icon and the
ESC key are rendered non-functional by the freeze, and I have to use the
System Monitor to identify and end the Python interpreter which is running
events.py.
Now, I can't be sure that the window.clear() call doesn't make OpenGL do
something. But why should it, when the window contains no graphics? I'm
beginning to wonder whether this problem has anything to do with graphics
at all. The event loop itself seems to become unhooked after a while.
Once again, I turn to you for advice. Thanks.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/groups/opt_out.
