Now I am not convinced that it has to do with glydget. If I set it up to open the file dialog box after pressing a key I still get the error. I also occasionally get errors about the autorelease pool:
2009-11-29 20:37:33.280 Python[25903:d0f] *** __NSAutoreleaseNoPool(): Object 0xa069ec68 of class NSCFString autoreleased with no pool in place - just leaking On Nov 29, 8:26 pm, Daniel <[email protected]> wrote: > This may be a problem with glydget, I moved some code around and it > works elsewhere, but not if I'm calling it from a glydget button > action. > > I'll look into it some more.... > > On Nov 29, 8:22 pm, Daniel <[email protected]> wrote: > > > > > Yes, I do root.destroy() after the dialog is complete. I just get: > > > Program terminated by uncaught signal #10 after 5.37 seconds. > > > if I do not try to access the variable, but if I do try to access the > > variable it is signal 11. I'm on a mac running snow leopard if that > > may be part of the issue. > > > Dan > > > On Nov 29, 8:17 pm, Richard Jones <[email protected]> wrote: > > > > On 30/11/2009, at 3:08 PM, Daniel wrote: > > > > > Any tips on getting a file dialog to work with pyglet? I naively > > > > tried: > > > > > root = Tkinter.Tk() > > > > root.withdraw() > > > > filename = tkFileDialog.askopenfilename() > > > > I use this in a pyglet app with no problems. What's the exception you get? > > > > Do you "root.destroy()" when the file dialog is finished with? > > > > Richard -- 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.
