For those that are curious, this appears to be a problem with Snow Leopord (running with the prefer 32bit workaround). The exact program works fine on another mac using Leopord. The error occurs when you exit out of a tkinter file dialog either by pressing the OK or Cancel buttons, and only occurs if the pyglet event loop is running (you can put the open dialog code before pyglet.app.run() and it runs fine).
Dan On Nov 29, 9:18 pm, Steve <[email protected]> wrote: > I wrote some code a year or so ago that will open a native dialog on > most OSes. No dependencies. > > http://github.com/irskep/pygletlibs/blob/master/dialogs.py > > On Nov 29, 11:08 pm, Daniel <[email protected]> wrote: > > > > > Any tips on getting a file dialog to work with pyglet? I naively > > tried: > > > root = Tkinter.Tk() > > root.withdraw() > > filename = tkFileDialog.askopenfilename() > > > but this causes an uncaught exception once the dialog is closed either > > by canceling or selecting a file (the exception happens some time > > after it passes back the path string, I can successfully print the > > variable 'filename', but then it immediately crashes with a signal 11 > > or signal 10 if I do not attempt to read the variable 'filename') > > > I know kytten offers some rudimentary functionality for this, but > > would prefer to avoid that as I am already using glydget. > > > Any help, tips, or points in the right direction will be appreciated. > > > Thanks, > > Dan -- 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.
