From rhixz06_sorphen at yahoo.com Mon Sep 3 07:28:39 2012 From: rhixz06_sorphen at yahoo.com (rhixz06) Date: Sun, 2 Sep 2012 22:28:39 -0700 (PDT) Subject: [Tkinter-discuss] DRAG and DROP image Message-ID: <1346650119739-4987204.post@n6.nabble.com> hey guys!hmm... I'm kinda new in tkinter...my friends and I were developing an educational game,..I just want to ask if you know an easiest way to drag and drop an image in tkinter.... please I need a reply thanks,.. -- View this message in context: http://python.6.n6.nabble.com/DRAG-and-DROP-image-tp4987204.html Sent from the Python - tkinter-discuss mailing list archive at Nabble.com. From msa01 at bitflipper.ca Mon Sep 3 14:37:37 2012 From: msa01 at bitflipper.ca (Cam Farnell) Date: Mon, 03 Sep 2012 09:37:37 -0300 Subject: [Tkinter-discuss] DRAG and DROP image In-Reply-To: <1346650119739-4987204.post@n6.nabble.com> References: <1346650119739-4987204.post@n6.nabble.com> Message-ID: <5044A491.3070105@bitflipper.ca> You might check out this page: http://www.bitflipper.ca/Documentation/Tkdnd.html which gives a description of how to implement drag and drop in tkinter. On 12-09-03 02:28 AM, rhixz06 wrote: > hey guys!hmm... I'm kinda new in tkinter...my friends and I were developing > an educational game,..I just want to ask if you know an easiest way to drag > and drop an image in tkinter.... please I need a reply thanks,.. From kw at codebykevin.com Mon Sep 3 16:45:05 2012 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 03 Sep 2012 10:45:05 -0400 Subject: [Tkinter-discuss] DRAG and DROP image In-Reply-To: <5044A491.3070105@bitflipper.ca> References: <1346650119739-4987204.post@n6.nabble.com> <5044A491.3070105@bitflipper.ca> Message-ID: <5044C271.8020009@codebykevin.com> On 9/3/12 8:37 AM, Cam Farnell wrote: > You might check out this page: > > http://www.bitflipper.ca/Documentation/Tkdnd.html > > which gives a description of how to implement drag and drop in tkinter. Another option for cross-application drag and drop: http://klappnase.bubble.org/TkinterDnD/index.html -- Kevin Walzer Code by Kevin http://www.codebykevin.com From python at bdurham.com Mon Sep 3 18:18:41 2012 From: python at bdurham.com (python at bdurham.com) Date: Mon, 03 Sep 2012 12:18:41 -0400 Subject: [Tkinter-discuss] DRAG and DROP image In-Reply-To: <5044C271.8020009@codebykevin.com> References: <1346650119739-4987204.post@n6.nabble.com> <5044A491.3070105@bitflipper.ca> <5044C271.8020009@codebykevin.com> Message-ID: <1346689121.13519.140661123074805.52E3FD2A@webmail.messagingengine.com> Kevin, > Another option for cross-application drag and drop: > http://klappnase.bubble.org/TkinterDnD/index.html Any experience with the experimental version 2 of the above library? TkinterDnD2 is a python wrapper for George Petasis' tkDnD Tk extension version 2. http://klappnase.bubble.org/TkinterDnD2/index.html Malcolm From kw at codebykevin.com Mon Sep 3 18:22:23 2012 From: kw at codebykevin.com (Kevin Walzer) Date: Mon, 03 Sep 2012 12:22:23 -0400 Subject: [Tkinter-discuss] DRAG and DROP image In-Reply-To: <1346689121.13519.140661123074805.52E3FD2A@webmail.messagingengine.com> References: <1346650119739-4987204.post@n6.nabble.com> <5044A491.3070105@bitflipper.ca> <5044C271.8020009@codebykevin.com> <1346689121.13519.140661123074805.52E3FD2A@webmail.messagingengine.com> Message-ID: <5044D93F.2080301@codebykevin.com> On 9/3/12 12:18 PM, python at bdurham.com wrote: > Kevin, > >> Another option for cross-application drag and drop: >> http://klappnase.bubble.org/TkinterDnD/index.html > > Any experience with the experimental version 2 of the above library? > > TkinterDnD2 is a python wrapper for George Petasis' tkDnD Tk extension > version 2. > http://klappnase.bubble.org/TkinterDnD2/index.html > > Malcolm > That's actually the version I tested--seems to works fine on OS X. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com From lionkimbro at gmail.com Wed Sep 19 08:09:47 2012 From: lionkimbro at gmail.com (Lion Kimbro) Date: Tue, 18 Sep 2012 23:09:47 -0700 Subject: [Tkinter-discuss] pack geometry manager question Message-ID: Dear tkinter-discuss, I'm trying to make a user interface like the following: :::::::::::::::::::::::::::::::::::::::::::: : XXXXXXXXXXXXXX : <- a Label :[ <-- expands ][ expands --> ]: <- 2 Entries :[ <-- expands ][ expands --> ]: <- 2 more Entries : : : (empty space expands : : downward) : :..........................................: Pseudo-code (full code at end of document): toplevel "XXXXXXXXXXXXXX" label anchor=n pack frame expand=1 fill=x anchor=n pack entry expand=1 fill=x anchor=n lpack entry expand=1 fill=x anchor=n lpack frame expand=1 fill=x anchor=n pack entry expand=1 fill=x anchor=n lpack entry expand=1 fill=x anchor=n lpack frame expand=1 fill=both anchor=n pack What I'm finding is this: 1. the label (XXXXXXXXXXXXXX) hugs the top of the window (GOOD) 2. the top two entries hug the label (GOOD) 3. the lower two entries space a ways away from the top two entries (DO NOT WANT) What I want instead, is that the lower two entries hug the top two entries. (More deeply: I want to UNDERSTAND why this is happening like this. I could use a grid and that would solve this problem, but I want to have facility with the packer, too.) I've tried changing around the values a bunch, but I just don't have any luck getting this to work. My assumption (that seems to be flawed) is that when I set expand=1, that if it says "fill=x", then that means that it will ONLY expand horizontally. But it seems to be expanding in both directions. Thoughts? Insights? == Full Example (Python 3.2) == from tkinter import * t = Toplevel() lbl = Label(t, text="XXXXXXXXXXX") lbl.pack(side=TOP, anchor=N) f1 = Frame(t) f1.pack(side=TOP, expand=1, fill=X, anchor=N) e11 = Entry(f1) e11.pack(side=LEFT, expand=1, fill=X, anchor=N) e12 = Entry(f1) e12.pack(side=LEFT, expand=1, fill=X, anchor=N) f2 = Frame(t) f2.pack(side=TOP, expand=1, fill=X, anchor=N) e21 = Entry(f2) e21.pack(side=LEFT, expand=1, fill=X, anchor=N) e22 = Entry(f2) e22.pack(side=LEFT, expand=1, fill=X, anchor=N) # This last one seems to do nothing. # My hope was that it would somehow "pressure" f2 higher, but nope. f3 = Frame(t) f3.pack(side=TOP, expand=1, fill=X, anchor=N) -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.odonnell at uam.es Wed Sep 19 13:35:42 2012 From: michael.odonnell at uam.es (Michael O'Donnell) Date: Wed, 19 Sep 2012 13:35:42 +0200 Subject: [Tkinter-discuss] pack geometry manager question In-Reply-To: References: Message-ID: Hi Lion, At least under my Windows version running Python 3.3.0rc2, and TK 8.5, I get the initial window is tight to the Entries (no extra space). However, when I drag the window larger than this minimum, yes, the second row of entries is spaced down from the top one. Three changes to your code: 1) I dropped the last frame, which being empty and without specified dimensions, does nothing. 2) I set the background color of your frames so I can see which frame is actually consuming what space. 3) I changed the expand=1 for the frames to expand=False, and now all frames stick to the top, which is what I think you want. See code below: from tkinter import * t = Toplevel(bg="blue") lbl = Label(t, text="XXXXXXXXXXX") lbl.pack(side=TOP, anchor=N) f1 = Frame(t, bg="green") f1.pack(side=TOP, expand=False, fill=X, anchor=N) e11 = Entry(f1) e11.pack(side=LEFT, expand=True, fill=X, anchor=N) e12 = Entry(f1) e12.pack(side=LEFT, expand=True, fill=X, anchor=N) f2 = Frame(t, bg="red") f2.pack(side=TOP, expand=False, fill=X, anchor=N) e21 = Entry(f2) e21.pack(side=LEFT, expand=True, fill=X, anchor=N) e22 = Entry(f2) e22.pack(side=LEFT, expand=True, fill=X, anchor=N) Now, as to why expand=False, fill=X gives the behaviour you want, I cannot help you. I just much around with these until I find the soultion. Sorry. Mick From emilianogavilan at gmail.com Wed Sep 19 13:46:29 2012 From: emilianogavilan at gmail.com (Emiliano Gavilan) Date: Wed, 19 Sep 2012 08:46:29 -0300 Subject: [Tkinter-discuss] pack geometry manager question In-Reply-To: References: Message-ID: 2012/9/19 Michael O'Donnell : > > Now, as to why expand=False, fill=X gives the behaviour > you want, I cannot help you. I just much around with these > until I find the soultion. Sorry. Is explained in the documentation: http://www.tcl.tk/man/tcl8.5/TkCmd/pack.htm See THE PACKER ALGORITHM and EXPANSION sections. Regards Emiliano From bob at greschke.com Wed Sep 19 13:55:41 2012 From: bob at greschke.com (Bob Greschke) Date: Wed, 19 Sep 2012 05:55:41 -0600 Subject: [Tkinter-discuss] pack geometry manager question In-Reply-To: References: Message-ID: Let me try to type this on an iPad. From Tkinter import * Root = Tk() Sub = Frame(Root) Label(Sub, text = "Now is the time\nto fix this.").pack(side = TOP) SSub = Frame(Sub) Entry(SSub).pack(side = LEFT, expand = YES, fill = X) Entry(SSub).pack(side = LEFT, expand = YES, fill = X) SSub.pack(side = TOP, fill = X) SSub = Frame(Sub) Entry(SSub).pack(side = LEFT, expand = YES, fill = X) Entry(SSub).pack(side = LEFT, expand = YES, fill = X) SSub.pack(side = TOP, fill = X) Sub.pack(side = TOP, fill = X, anchor = N) Sub = Frame(Root) Label(Sub, text = "Other stuff here.").pack() Sub.pack() mainloop() You just didn't have the Sub frame around everything to keep them glued together and at the top. Bob Sent from my iPad. Sucks for writing code. On Sep 19, 2012, at 0:09, Lion Kimbro wrote: > > Dear tkinter-discuss, > > I'm trying to make a user interface like the following: > > :::::::::::::::::::::::::::::::::::::::::::: > : XXXXXXXXXXXXXX : <- a Label > :[ <-- expands ][ expands --> ]: <- 2 Entries > :[ <-- expands ][ expands --> ]: <- 2 more Entries > : : > : (empty space expands : > : downward) : > :..........................................: > > Pseudo-code (full code at end of document): > > toplevel > "XXXXXXXXXXXXXX" label anchor=n pack > frame expand=1 fill=x anchor=n pack > entry expand=1 fill=x anchor=n lpack > entry expand=1 fill=x anchor=n lpack > > frame expand=1 fill=x anchor=n pack > entry expand=1 fill=x anchor=n lpack > entry expand=1 fill=x anchor=n lpack > > frame expand=1 fill=both anchor=n pack > > > What I'm finding is this: > > 1. the label (XXXXXXXXXXXXXX) hugs the top of the window > (GOOD) > > 2. the top two entries hug the label > (GOOD) > > 3. the lower two entries space a ways away from the top two entries > (DO NOT WANT) > > What I want instead, is that the lower two entries hug the top two > entries. > > (More deeply: I want to UNDERSTAND why this is happening like this. > I could use a grid and that would solve this problem, but I want to > have facility with the packer, too.) > > I've tried changing around the values a bunch, but I just don't have > any luck getting this to work. > > My assumption (that seems to be flawed) is that when I set expand=1, > that if it says "fill=x", then that means that it will ONLY expand > horizontally. But it seems to be expanding in both directions. > > Thoughts? Insights? > > > == Full Example (Python 3.2) == > > from tkinter import * > > t = Toplevel() > > lbl = Label(t, text="XXXXXXXXXXX") > lbl.pack(side=TOP, anchor=N) > > f1 = Frame(t) > f1.pack(side=TOP, expand=1, fill=X, anchor=N) > > e11 = Entry(f1) > e11.pack(side=LEFT, expand=1, fill=X, anchor=N) > e12 = Entry(f1) > e12.pack(side=LEFT, expand=1, fill=X, anchor=N) > > f2 = Frame(t) > f2.pack(side=TOP, expand=1, fill=X, anchor=N) > > e21 = Entry(f2) > e21.pack(side=LEFT, expand=1, fill=X, anchor=N) > e22 = Entry(f2) > e22.pack(side=LEFT, expand=1, fill=X, anchor=N) > > # This last one seems to do nothing. > # My hope was that it would somehow "pressure" f2 higher, but nope. > > f3 = Frame(t) > f3.pack(side=TOP, expand=1, fill=X, anchor=N) > > _______________________________________________ > Tkinter-discuss mailing list > Tkinter-discuss at python.org > http://mail.python.org/mailman/listinfo/tkinter-discuss From lionkimbro at gmail.com Wed Sep 19 16:49:46 2012 From: lionkimbro at gmail.com (Lion Kimbro) Date: Wed, 19 Sep 2012 07:49:46 -0700 Subject: [Tkinter-discuss] pack geometry manager question In-Reply-To: References: Message-ID: Thank you all..! I understand now, and have verified that your solutions work and have adjusted my own code as well. Success! This explanation within the tcl/tk documentation is particularly helpful because it eliminates all guesswork. Thank you all very much! - Lion On Sep 19, 2012, at 4:46 AM, Emiliano Gavilan wrote: > 2012/9/19 Michael O'Donnell : >> >> Now, as to why expand=False, fill=X gives the behaviour >> you want, I cannot help you. I just much around with these >> until I find the soultion. Sorry. > > Is explained in the documentation: > > http://www.tcl.tk/man/tcl8.5/TkCmd/pack.htm > > See THE PACKER ALGORITHM and EXPANSION sections. > > Regards > Emiliano > _______________________________________________ > Tkinter-discuss mailing list > Tkinter-discuss at python.org > http://mail.python.org/mailman/listinfo/tkinter-discuss From mkieverpy at tlink.de Tue Sep 25 17:18:50 2012 From: mkieverpy at tlink.de (mkieverpy at tlink.de) Date: Tue, 25 Sep 2012 15:18:50 -0000 Subject: [Tkinter-discuss] =?utf-8?q?FocusOut_not_working_as_expected_-_ti?= =?utf-8?q?x_broken=3F?= Message-ID: <3XR5fB5C5zzQq0@mail.python.org> Dear list, I built a GUI using tkinter and tix (python 3.1/linux) and have a frame which wants to receive key events in a certain "mode". I do this when initializing the frame: class WBuildMenu(Frame, View): ... self._keyID = self.bind('', self._onKey, add=True) and later when entering the "mode": ... self.focus_set() self._FocusID = self.bind('' , self._focusLost, add=True) I then receive key events correctly. I expected to get event when my frame loses focus and no longer receives key events. Am I correct in expecting this behaviour? (I wanted to repeat "self.focus_set()" in this case) What I really get is this: I only get FocusOut when the mouse leaves the application window. I do not get FocusOut event when I click some other part of the application window which nonetheless results in the frame losing focus and no longer receiving key events. Currently, my guess is that this is broken in tix (which unluckily seems not to be under development any more). Any other opinions? Any other method to track focus which I missed? Thanks for any hints, Matthias Kievernagel From klappnase at web.de Tue Sep 25 19:29:22 2012 From: klappnase at web.de (Michael Lange) Date: Tue, 25 Sep 2012 19:29:22 +0200 Subject: [Tkinter-discuss] FocusOut not working as expected - tix broken? In-Reply-To: <3XR5fB5C5zzQq0@mail.python.org> References: <3XR5fB5C5zzQq0@mail.python.org> Message-ID: <20120925192922.dc0a76f7.klappnase@web.de> Hi, On Tue, 25 Sep 2012 15:18:50 -0000 mkieverpy at tlink.de wrote: (...) > > What I really get is this: I only get FocusOut when the mouse > leaves the application window. I do not get FocusOut event > when I click some other part of the application window > which nonetheless results in the frame losing focus and no longer > receiving key events. > Currently, my guess is that this is broken in tix > (which unluckily seems not to be under development any more). > Can you post a simple example that shows this problem? I am not sure if I understood you correctly; I tried the following: ###################################### import tkinter.tix as Tix root = Tix.Tk() f = Tix.Frame(root) f.pack(fill='both', expand=1) Tix.Button(f, text='foo').pack() f2 = Tix.Frame(root) f2.pack(fill='both') Tix.Button(f2, text='bar').pack() def on_focus_out(event): print('focus out') f.bind('', on_focus_out) root.mainloop() ###################################### and here it worked as expected (python 3.1,, debian squeeze with IceWM). It might very well be a WM specific issue though, did you try different WMs? Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. "That unit is a woman." "A mass of conflicting impulses." -- Spock and Nomad, "The Changeling", stardate 3541.9 From mkieverpy at tlink.de Wed Sep 26 14:16:42 2012 From: mkieverpy at tlink.de (mkieverpy at tlink.de) Date: Wed, 26 Sep 2012 14:16:42 +0200 Subject: [Tkinter-discuss] =?utf-8?q?FocusOut_not_working_as_expected_-_ti?= =?utf-8?q?x_broken=3F?= Message-ID: <393b0e3b3864df4d514e849f2db33ce7@tlink.de> Hello Michael, Me: > What I really get is this: I only get FocusOut when the mouse > leaves the application window. I do not get FocusOut event > when I click some other part of the application window > which nonetheless results in the frame losing focus and no longer > receiving key events. > Currently, my guess is that this is broken in tix > (which unluckily seems not to be under development any more). Michael: (...) >and here it worked as expected (python 3.1,, debian squeeze with > IceWM). >It might very well be a WM specific issue though, did you try > different >WMs? Sorry, lost focus completely, so to speak. Hardware failure. Hopefully back next week. Before breakdown I tried IceWM and got same result for my and your program. I'm on debian wheezy, ctwm, self compiled python 3.1.1 (tcl/tk 8.4 not sure) I am not getting any 'focus out' messages from your program. No idea why. I'll try to post a minimal example some time next week. Regards, Matthias. (sent from my mac cookie box) From klappnase at web.de Wed Sep 26 20:31:30 2012 From: klappnase at web.de (Michael Lange) Date: Wed, 26 Sep 2012 20:31:30 +0200 Subject: [Tkinter-discuss] FocusOut not working as expected - tix broken? In-Reply-To: <393b0e3b3864df4d514e849f2db33ce7@tlink.de> References: <393b0e3b3864df4d514e849f2db33ce7@tlink.de> Message-ID: <20120926203130.a3712973.klappnase@web.de> Hi Matthias, On Wed, 26 Sep 2012 14:16:42 +0200 mkieverpy at tlink.de wrote: > Before breakdown I tried IceWM and got same result for my and your > program. > I'm on debian wheezy, ctwm, self compiled python 3.1.1 (tcl/tk 8.4 not > sure) Then I guess it might be a version conflict between Tk and tix, like for example: you built Python against Tk-8.4 and use debian's default tix which itself is compiled against Tk-8.5. Is it possible that something like this happened? Regards Michael .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-. There's coffee in that nebula! -- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud" From raycores at gmail.com Sun Sep 30 20:07:18 2012 From: raycores at gmail.com (Lynn Oliver) Date: Sun, 30 Sep 2012 11:07:18 -0700 Subject: [Tkinter-discuss] crash on tkFileDialog:asksaveasfilename() Message-ID: <302C0C86-AFE6-418A-8DB9-1001CFAAE4ED@gmail.com> I'm puzzled by reports from a single person using my program, who states that he consistently crashes in the common file dialog invoked by asksaveasfilename() if, and only if, he attempts to change folders. He says this is happening on two different machines, an iMac (see below) and a 2011 MacBookPro, both running 10.8.2 (current version of Mountain Lion). The program is using Python 2.7.2, Tcl/Tk 8.5. I have never seen this error or been able to reproduce it on my machine, a 2011 iMac also running 10.8.2. My understanding is that Tkinter is handing control over to a system dialog, so the crash occurs before control returns to Tkinter. Is there anything I could be doing in my program that would affect this? I couldn't find any problem reports similar to this for Tkinter. The crash report he sent is below. Thanks... Lynn Stack Trace: Process: aomDSP [6110] Path: /Applications/aomDSP.app/Contents/MacOS/aomDSP Identifier: aomDSP Version: 1.0.7 (???) Code Type: X86-64 (Native) Parent Process: aomDSP [6108] User ID: 501 Date/Time: 2012-09-29 13:19:05.322 -0400 OS Version: Mac OS X 10.8.2 (12C54) Report Version: 10 Interval Since Last Report: 604288 sec Crashes Since Last Report: 2 Per-App Crashes Since Last Report: 1 Anonymous UUID: 3CA6AC2E-0D37-27A5-22F1-1E1194B4B4EF Crashed Thread: Unknown Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000003 Backtrace not available Unknown thread crashed with X86 Thread State (64-bit): rax: 0x00007fff75965860 rbx: 0x0000000000000000 rcx: 0x00007fff76bcde01 rdx: 0x0000000000000007 rdi: 0x00007fff5fbfa790 rsi: 0x00007fff86062c7e rbp: 0x00007fff5fbfa790 rsp: 0x00007fff5fbfa768 r8: 0x00007fff7664c580 r9: 0x0000000000000000 r10: 0x00007fff75965870 r11: 0x00007fff5fbfa634 r12: 0x000000010b6ccd00 r13: 0x000000010b7a72a0 r14: 0x00007fff5fbfa8d8 r15: 0x00007fff5fbfa918 rip: 0x0000000000000003 rfl: 0x0000000000010246 cr2: 0x0000000000000003 Logical CPU: 0 Binary images description not available External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 17 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 3527 thread_create: 0 thread_set_state: 0 Model: iMac7,1, BootROM IM71.007A.B03, 2 processors, Intel Core 2 Duo, 2.8 GHz, 6 GB, SMC 1.21f4 Graphics: ATI Radeon HD 2600 Pro, ATI,RadeonHD2600, PCIe, 256 MB Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F7F7FF70000, 0x00004B363435365536314535363637460000 Memory Module: BANK 1/DIMM1, 4 GB, DDR2 SDRAM, 667 MHz, 0x7F7FFE0000000000, 0x4542453431554638414244412D36452D4520 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.16) Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports Network Service: Ethernet, Ethernet, en0 Serial ATA Device: ST31000528AS, 1 TB Parallel ATA Device: MATSHITADVD-R UJ-85J USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd400000 / 3 USB Device: Drobo, 0x19b9, 0x4d10, 0xfd100000 / 2 USB Device: USB 2.0 Hub [MTT], 0x050d (Belkin Corporation), 0x0017, 0xfa400000 / 2 USB Device: Back-UPS BX1300G FW:864.L5 .D USB FW:L5, 0x051d (American Power Conversion), 0x0002, 0xfa440000 / 7 USB Device: My Book 1130, 0x1058 (Western Digital Technologies, Inc.), 0x1130, 0xfa430000 / 6 USB Device: Impulse, 0x1235, 0x001a, 0xfa410000 / 5 USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc50c, 0xfa460000 / 4 USB Device: My Book 1110, 0x1058 (Western Digital Technologies, Inc.), 0x1110, 0xfa420000 / 3 USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2 USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x1a100000 / 2 FireWire Device: Duet, Apogee Electronics, 400mbit_speed -------------- next part -------------- An HTML attachment was scrubbed... URL: From raycores at gmail.com Sun Sep 30 20:18:05 2012 From: raycores at gmail.com (Lynn Oliver) Date: Sun, 30 Sep 2012 11:18:05 -0700 Subject: [Tkinter-discuss] crash on tkFileDialog:asksaveasfilename() Message-ID: <1DC31F15-A4A7-4142-85C7-297C09C711FA@gmail.com> He just sent the console output during a crash, so I thought I'd pass that along as well: 2012-09-30 12:41:34.481 PM ReportCrash[935]: Failed to create CSSymbolicatorRef for aomDSP[933] 2012-09-30 12:41:34.589 PM ReportCrash[935]: Failed to create dSYM-less CSSymbolicatorRef for aomDSP[933] 2012-09-30 12:41:34.876 PM ReportCrash[935]: Failed to create CSSymbolicatorRef for aomDSP[930] 2012-09-30 12:41:34.985 PM ReportCrash[935]: Failed to create dSYM-less CSSymbolicatorRef for aomDSP[930] 2012-09-30 12:41:35.099 PM com.apple.launchd.peruser.501[584]: ([0x0-0x4e04e].aomDSP[930]) Job appears to have crashed: Bus error: 10 This looks more like a failure to link to a dynamic library but I'm not sure how to interpret this. Is it a result of the crash, or is it related to an incompatibility that caused the crash? I'm afraid I'm reduced to searching stackoverflow for this type of thing. Lynn -------------- next part -------------- An HTML attachment was scrubbed... URL: From raycores at gmail.com Sun Sep 30 21:46:51 2012 From: raycores at gmail.com (Lynn Oliver) Date: Sun, 30 Sep 2012 12:46:51 -0700 Subject: [Tkinter-discuss] crash on tkFileDialog:asksaveasfilename() In-Reply-To: References: <302C0C86-AFE6-418A-8DB9-1001CFAAE4ED@gmail.com> Message-ID: <7A68FE1A-2584-4643-83B7-63370E0B38B1@gmail.com> It's packaged using pyinstaller, so it unpacks into a temp folder and runs from there. Sent from my iPad On Sep 30, 2012, at 12:22 PM, wrw at mac.com wrote: > On Sep 30, 2012, at 2:07 PM, Lynn Oliver wrote: > >> I'm puzzled by reports from a single person using my program, who states that he consistently crashes in the common file dialog invoked by asksaveasfilename() if, and only if, he attempts to change folders. He says this is happening on two different machines, an iMac (see below) and a 2011 MacBookPro, both running 10.8.2 (current version of Mountain Lion). >> >> The program is using Python 2.7.2, Tcl/Tk 8.5. I have never seen this error or been able to reproduce it on my machine, a 2011 iMac also running 10.8.2. >> >> My understanding is that Tkinter is handing control over to a system dialog, so the crash occurs before control returns to Tkinter. Is there anything I could be doing in my program that would affect this? I couldn't find any problem reports similar to this for Tkinter. >> >> The crash report he sent is below. >> >> Thanks... >> Lynn >> > > Lynn, I'm no help reading the dump, but I have a question, which is possibly relevant. > > How was your program distributed? That is, is it an OS-X 'bundle' produced by py2app, or is your user executing python source directly? > > -Bill > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wrw at mac.com Sun Sep 30 21:22:17 2012 From: wrw at mac.com (wrw at mac.com) Date: Sun, 30 Sep 2012 15:22:17 -0400 Subject: [Tkinter-discuss] crash on tkFileDialog:asksaveasfilename() In-Reply-To: <302C0C86-AFE6-418A-8DB9-1001CFAAE4ED@gmail.com> References: <302C0C86-AFE6-418A-8DB9-1001CFAAE4ED@gmail.com> Message-ID: On Sep 30, 2012, at 2:07 PM, Lynn Oliver wrote: > I'm puzzled by reports from a single person using my program, who states that he consistently crashes in the common file dialog invoked by asksaveasfilename() if, and only if, he attempts to change folders. He says this is happening on two different machines, an iMac (see below) and a 2011 MacBookPro, both running 10.8.2 (current version of Mountain Lion). > > The program is using Python 2.7.2, Tcl/Tk 8.5. I have never seen this error or been able to reproduce it on my machine, a 2011 iMac also running 10.8.2. > > My understanding is that Tkinter is handing control over to a system dialog, so the crash occurs before control returns to Tkinter. Is there anything I could be doing in my program that would affect this? I couldn't find any problem reports similar to this for Tkinter. > > The crash report he sent is below. > > Thanks... > Lynn > Lynn, I'm no help reading the dump, but I have a question, which is possibly relevant. How was your program distributed? That is, is it an OS-X 'bundle' produced by py2app, or is your user executing python source directly? -Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: From kw at codebykevin.com Sun Sep 30 22:31:23 2012 From: kw at codebykevin.com (Kevin Walzer) Date: Sun, 30 Sep 2012 16:31:23 -0400 Subject: [Tkinter-discuss] crash on tkFileDialog:asksaveasfilename() In-Reply-To: <1DC31F15-A4A7-4142-85C7-297C09C711FA@gmail.com> References: <1DC31F15-A4A7-4142-85C7-297C09C711FA@gmail.com> Message-ID: <5EA95369-4B7D-4B57-A631-E5D996382169@codebykevin.com> According to SO a failure to link to a dylib is likely the cause. Hard to say which dylib though. Sent from my iPhone On Sep 30, 2012, at 2:18 PM, Lynn Oliver wrote: > He just sent the console output during a crash, so I thought I'd pass that along as well: > > 2012-09-30 12:41:34.481 PM ReportCrash[935]: Failed to create CSSymbolicatorRef for aomDSP[933] > 2012-09-30 12:41:34.589 PM ReportCrash[935]: Failed to create dSYM-less CSSymbolicatorRef for aomDSP[933] > 2012-09-30 12:41:34.876 PM ReportCrash[935]: Failed to create CSSymbolicatorRef for aomDSP[930] > 2012-09-30 12:41:34.985 PM ReportCrash[935]: Failed to create dSYM-less CSSymbolicatorRef for aomDSP[930] > 2012-09-30 12:41:35.099 PM com.apple.launchd.peruser.501[584]: ([0x0-0x4e04e].aomDSP[930]) Job appears to have crashed: Bus error: 10 > > This looks more like a failure to link to a dynamic library but I'm not sure how to interpret this. Is it a result of the crash, or is it related to an incompatibility that caused the crash? I'm afraid I'm reduced to searching stackoverflow for this type of thing. > > Lynn > _______________________________________________ > Tkinter-discuss mailing list > Tkinter-discuss at python.org > http://mail.python.org/mailman/listinfo/tkinter-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From wrw at mac.com Sun Sep 30 23:32:07 2012 From: wrw at mac.com (wrw at mac.com) Date: Sun, 30 Sep 2012 17:32:07 -0400 Subject: [Tkinter-discuss] crash on tkFileDialog:asksaveasfilename() In-Reply-To: <7A68FE1A-2584-4643-83B7-63370E0B38B1@gmail.com> References: <302C0C86-AFE6-418A-8DB9-1001CFAAE4ED@gmail.com> <7A68FE1A-2584-4643-83B7-63370E0B38B1@gmail.com> Message-ID: <7D3D3FC3-7401-4519-9128-D98305DD4395@mac.com> On Sep 30, 2012, at 3:46 PM, Lynn Oliver wrote: > It's packaged using pyinstaller, so it unpacks into a temp folder and runs from there. > > Sent from my iPad > > On Sep 30, 2012, at 12:22 PM, wrw at mac.com wrote: > >> On Sep 30, 2012, at 2:07 PM, Lynn Oliver wrote: >> >>> I'm puzzled by reports from a single person using my program, who states that he consistently crashes in the common file dialog invoked by asksaveasfilename() if, and only if, he attempts to change folders. He says this is happening on two different machines, an iMac (see below) and a 2011 MacBookPro, both running 10.8.2 (current version of Mountain Lion). >>> >>> The program is using Python 2.7.2, Tcl/Tk 8.5. I have never seen this error or been able to reproduce it on my machine, a 2011 iMac also running 10.8.2. >>> >>> My understanding is that Tkinter is handing control over to a system dialog, so the crash occurs before control returns to Tkinter. Is there anything I could be doing in my program that would affect this? I couldn't find any problem reports similar to this for Tkinter. >>> >>> The crash report he sent is below. >>> >>> Thanks... >>> Lynn >>> >> >> Lynn, I'm no help reading the dump, but I have a question, which is possibly relevant. >> >> How was your program distributed? That is, is it an OS-X 'bundle' produced by py2app, or is your user executing python source directly? >> >> -Bill >> So, have you included _all_ the necessary libraries in the compressed package, and are the imports precise enough that it isn't maybe picking up one of the Apple system python libraries? -Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: