Mailman 3 October 2012 - Tkinter-discuss

Control position of Tkinter common dialogs?
by python＠bdurham.com Dec. 9, 2016

Dec. 9, 2016

Python 2.7 under Windows: How can we control the position of Tkinter's common dialogs? Here's what we've discovered: * Certain common dialogs always open up relative to their parent window * Certain common dialogs always open up centered on the user's desktop * All common dialogs appear to ignore the optional parent= parameter Questions: * How can we force a dialog to open up relative to its parent window? * How can we force a dialog to open up centered on the user's desktop? Background: import tkColorChooser as colorchooser import tkFileDialog as filedialog import tkMessageBox as messagebox # always open up relative to parent windows fileOpen = filedialog.askopenfilename() fileOpens = filedialog.askopenfilenames() fileSaveAs = filedialog.asksaveasfilename() color = colorchooser.askcolor() # always open up centered on desktop folderOpen = filedialog.askdirectory() messagebox.askquestion() Malcolm

6 9

Segfault in Image.PhotoImage on OS X
by Marc Culler Nov. 14, 2012

Nov. 14, 2012

This was reported here in February, but no debugging information was provided by the reporter: http://stackoverflow.com/questions/9142786/python-imagetk-photoimage-segfau… <view-source:http://stackoverflow.com/questions/9142786/python-imagetk-photo…> I can explain the nature of the problem, but I don't know how to fix it correctly. I am using the standard x86_64 Python 2.7.2 package from python.org and I have installed Active State Tcl/Tk 8.11. When I tried using easy_install to install PIL it would not load, claiming that _imaging.so did not exist. In fact, it existed but was only a thin i386 executable. So I compiled Imaging-1.1.7 with export CFLAGS='-arch i386 -arch x86_64' and export TCL_ROOT=/Library/Frameworks/Tcl.framework/Versions/8.5/Tcl I was then able to load the module. However, the following code produced a segfault: import Image import ImageTk import Tkinter W = Tkinter.Tk() Im = Image.open('test_image.jpg') x = ImageTk.PhotoImage(Im) The crash occurs in Tk_GetImageMasterData. More importantly, though, the crash was preceded by the following messages: objc[36554]: Class TKApplication is implemented in both /Library/Frameworks/Tk.framework/Versions/8.5/Tk and /System/Library/Frameworks/Tk.framework/Versions/8.5/Tk. One of the two will be used. Which one is undefined. objc[36554]: Class TKMenu is implemented in both /Library/Frameworks/Tk.framework/Versions/8.5/Tk and /System/Library/Frameworks/Tk.framework/Versions/8.5/Tk. One of the two will be used. Which one is undefined. objc[36554]: Class TKContentView is implemented in both /Library/Frameworks/Tk.framework/Versions/8.5/Tk and /System/Library/Frameworks/Tk.framework/Versions/8.5/Tk. One of the two will be used. Which one is undefined. objc[36554]: Class TKWindow is implemented in both /Library/Frameworks/Tk.framework/Versions/8.5/Tk and /System/Library/Frameworks/Tk.framework/Versions/8.5/Tk. One of the two will be used. Which one is undefined. Guessing that PIL was finding the System/Library/Frameworks/Tk.Framework instead of /Library/Frameworks/Tk.Framework, I tried hiding the system Tcl and Tk frameworks by renaming them. I was then able to create the PhotoImage and display it. I don't know where those messages come from, and I have never encountered them before. But I am guessing they are from OS X, since they are generated by an objective C program. Evidently _tkinter.so is able to specify which Tk.Framework to use. I don't know its mechanism for doing that. But, somehow, PIL is not doing it, and it ends up using the wrong one. A stack trace of the crash is below. - Marc 0x000000011517bccd in Tk_GetImageMasterData () (gdb) bt #0 0x000000011517bccd in Tk_GetImageMasterData () #1 0x0000000115183d9f in Tk_FindPhoto () #2 0x00000001014fbadc in PyImagingPhotoPut () #3 0x000000011502a05b in TclInvokeStringCommand () #4 0x000000010102142a in TclEvalObjvInternal () #5 0x000000010102261c in Tcl_EvalObjv () #6 0x000000010100646d in Tkapp_Call () #7 0x00000001000c102d in PyEval_EvalFrameEx () #8 0x00000001000c2d29 in PyEval_EvalCodeEx () #9 0x00000001000c0b6a in PyEval_EvalFrameEx () #10 0x00000001000c2d29 in PyEval_EvalCodeEx () #11 0x000000010003da80 in function_call () #12 0x000000010000c5e2 in PyObject_Call () #13 0x000000010001ebcb in instancemethod_call () #14 0x000000010000c5e2 in PyObject_Call () #15 0x00000001000ba5f7 in PyEval_CallObjectWithKeywords () #16 0x0000000100021e5e in PyInstance_New () #17 0x000000010000c5e2 in PyObject_Call () #18 0x00000001000be5f3 in PyEval_EvalFrameEx () #19 0x00000001000c2d29 in PyEval_EvalCodeEx () #20 0x00000001000c2e46 in PyEval_EvalCode () #21 0x00000001000e769c in PyRun_InteractiveOneFlags () #22 0x00000001000e78fe in PyRun_InteractiveLoopFlags () #23 0x00000001000e80e1 in PyRun_AnyFileExFlags () #24 0x00000001000fe77c in Py_Main () #25 0x0000000100000f14 in dyld_stub_strlen ()

4 5

Checkbutton indicatoron ignored on Mac
by Russell E. Owen Oct. 31, 2012

Oct. 31, 2012

I just realized that the Checkbutton option "indicatoron" is being ignored on Mac OS X: the checkbox is always shown, even if indicatoron is false. I'm using ActiveState's Tcl/Tk 8.5.11, specifically: ActiveTcl8.5.11.1.295590-macosx10.5-i386-x86_64-threaded Has anyone else noticed this, and is there a workaround? It ruins the appearance of a lot of my application. I see that ActiveState now has version 8.5.12 available and I'll give that a try. Anyone know how reliable that is on Mac OS X? I've seen warnings of bugs, but I don't know if they were fixed in time for that release. -- Russell

4 8

loop delay
by Paul Simon Oct. 24, 2012

Oct. 24, 2012

I' m a novice python programmer and now starting to learn tkinter for a front and db back end to replace an application written MS Access/VBA. The following program doesn't work as I expected as data is not written to the text box until the def is exited. If I include a print statement with the increment it is printed. Any suggestions are welcome. from Tkinter import * from time import sleep def count (event): #while n < 2: for n in range(2): print str(n) text_button.insert(2.0, str(n)) sleep (2) root = Tk() root.geometry("300x300+10+10") frame = Frame(root,bg="red", width=100,height=100) text_button = Text(frame,fg ="green",bg="blue",height=1,width=7) text_button.bind("<Button-1>",count) text_button.pack(side=LEFT) quit_button = Button(frame, text="QUIT",fg="red", command=root.destroy) quit_button.pack(side=LEFT) frame.pack() root.mainloop() ------------------------------- Paul Simon

3 5

Re: [Tkinter-discuss] FocusOut not working as expected - tix broken?
by mkieverpy＠tlink.de Oct. 16, 2012

Oct. 16, 2012

Hello, thanks for the new hints/information Michael and Bryan. I don't know if your hints would work in my setup, though. Except bind_all, which should work, I guess. My program structure: I have a Frame, which is nearly the complete toplevel window (only a title label and quit button outside; this is the Frame I originally tried to let capture all the keys). The left half is taken by a tix Tree and the right half contains one of a few editor classes (subclassed from Frame) which get exchanged based on the selected Tree node. One type of nodes opens a Canvas in the right half where I want the key shortcuts to work. The problem I see with both your hints (bind keys to all widgets, tag widgets and bind keys to tag) is I doubt they will work with tix Tree. I don't think tix Tree hands down any bind or tag to its subwidgets (or does it?). Thanks again, Matthias Kievernagel

2 1

Re: [Tkinter-discuss] FocusOut not working as expected - tix broken?
by mkieverpy＠tlink.de Oct. 11, 2012

Oct. 11, 2012

Hello Michael, I found a workaround: ------------------------------------------------ import tkinter root = tkinter.Tk() f = tkinter.Frame(root) f.pack(fill='both', expand=1) tkinter.Button(f, text='foo').pack() f2 = tkinter.Frame(root) f2.pack(fill='both') tkinter.Button(f2, text='bar').pack() f3 = tkinter.Frame(root) f3.pack(fill='both') def on_key(event): print('key') def on_focus_out(event): print('focus out') f3.focus_set() f3.focus_set() f3.bind('<Key>', on_key) f3.bind('<FocusOut>', on_focus_out) root.mainloop() ------------------------------------------------ The other program does not look wrong though. I think I'll ask at tcl/tk if they think it's a bug. Regards, Matthias Kievernagel

3 6

Error in import of Tkinter in python 2.7
by Pedro Marcal Oct. 9, 2012

Oct. 9, 2012

I have python 2.6 and 2.7 installed on my Windows 7-prof. my IDLE runs OK with Tkinter. When I tried to use IDLE in 2.7 I got the above error. I suspect I need to set an environmental Variable. Thanks for any suggestions. Pedro

2 4

Re: [Tkinter-discuss] FocusOut not working as expected - tix broken?
by mkieverpy＠tlink.de Oct. 7, 2012

Oct. 7, 2012

Hello Michael, I'm back and tested a bit more. I updated to standard packages (debian wheezy) python 3.2 tcl/tk 8.5 tix 8.4.3 to avoid any problems with who is using who. I then expanded your test program to emulate my configuration and what I want to implement. There I noticed that it's not a tix problem at all, but standard tcl/tk focus behaves the same. Here's the program: ----------------------------------------------- import tkinter root = tkinter.Tk() f = tkinter.Frame(root) f.pack(fill='both', expand=1) tkinter.Button(f, text='foo').pack() f2 = tkinter.Frame(root) f2.pack(fill='both') tkinter.Button(f2, text='bar').pack() def on_key(event): print('key') def on_focus_out(event): print('focus out') f.focus_set() f.focus_set() f.bind('<Key>', on_key) f.bind('<FocusOut>', on_focus_out) root.mainloop() ----------------------------------------------- The problem is when I use the 'Tab' key to move the focus. The first 'Tab' moves the focus to the 'foo' button. 'f' no longer gets key events but does not get the focus out event either. The next 'Tab' moves the focus to the 'bar' button, 'f' gets the focus out event and key events arrive again after I do 'focus_set'. So it looks like tk standard behaviour. Can I get what I want? In my program it's a mouse click that can move the focus away. So tweaking or disabling 'Tab' is not a solution. Regards, Matthias Kievernagel

1 0

Re: [Tkinter-discuss] whats Style()
by Matthew Ngaha Oct. 7, 2012

Oct. 7, 2012

sorry i sent the email directly by mistake. Just like to say thanks once again for all the help

1 0

whats Style()
by Matthew Ngaha Oct. 7, 2012

Oct. 7, 2012

hi guys. in my tutorial ive come across an undefined class called Style. using python 3 most import statements produce an error so i mainly stick to: from tkinter import * . here are some of the lines of code that produces errors in different examples making it hard to move on: Style().configure("TFrame", background="#333") and self.style = Style() self.style.theme_use("default") maybe the error is in my importing but the imports the examples use produce errors. here are one: from ttk import Frame, Button, Style my interpreter doesnt know what ttk is.

2 2