On 22/07/2007, at 12:16 PM, Brian Jorgensen wrote:
> I'm slowly figuring out how Pyglet works under the hood, and am > always pleasantly surprised. The window closure problem stemmed > from a misunderstanding of the semantics of has_exit and close; for > example, I thought close was supposed to set has_exit to True. Now > I've gotten rid of close_later altogether and just use has_exit, as > I think you intended. Sounds good. Quite a lot of documentation on this has been written, but hasn't been published yet. This should be done in the next few weeks, and will hopefully clear these sorts of things up before they become problems. > Anyway, it took me a while to find the right paradigm for > ManagedWindow, but it's working really well now. It might be nice > to see something like it in the examples directory. Sounds good. Actually (with your permission) I'd like to add it directly into pyglet.window; it looks very useful for dealing with multiple windows in a sane way, as well as for exploratory programming. Alex. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
