Mailman 3 January 2014 - 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

Strange word wrapping behaviour in Text widget
by Michael O'Donnell Jan. 28, 2014

Jan. 28, 2014

Hi All, Running Python 3.3.3 / Tk 8.5.15 under MacOSX 10.9.1 I am using a Text widget to display some text from a file, with 'wrap=WORD' set. When the file uses both \n and \r in line breaks (which happens in some Windows files) The last word of each line is wrapped to the next line. E.g. text: "Mike Krath\n\ris nice." is displayed as Mike Krath is nice. When editing the text, the widget gets confused as to where characters are on the screen. Clicking just past the end of line of "Krath", the insert curser appears BEFORE the "h". Try the example below to see if it happens on your installation: from tkinter import * tk = Tk() fr=Text(tk, wrap=WORD) fr.pack() fr.insert(END, "Mike Krath\r\nHigh and Lifted Up\r\nIt was a windy day.") tk.mainloop() I could replace all "\n\r" in my text with "\n", but it would be better for Tk to behave as expected. Mick

2 2

Canvas performance, OpenGL, VTK
by Beinan Li Jan. 27, 2014

Jan. 27, 2014

Hi tkinter, I'm investigating into tkinter for data visualization with Python. Seems that the Canvas widget is the one for drawing data curves, and I will need several Canvas at the same time for different views and the same data. Now the question is how is the general graphics performance if I need to update the Canvas frequently, e.g., 30-60fps? If the performance does not meet my expectation, should I consider using OpenGL instead? If yes, I have no idea how to hook GL up with tkinter. There is a tk OpenGL widget, but seems it is not easy to set up: http://stackoverflow.com/questions/11844882/tkinter-opengl-context-in-python So I wonder if there are any documents about how to make Canvas work with OpenGL or VTK. Thanks Beinan

1 0

Binding a List to a ScrollBar
by Rob Ward Jan. 16, 2014

Jan. 16, 2014

Hi Folks, Sorry to be back so soon but I have another challenge. I wanted to choose some colours for my program and came across a program that claimed to list the colours in a nifty little Python program. Cute I thought, I must try that. Quite a few hours later I am stumped. Here is the code with only the first 26 colours as data - from tkinter import * COLORS =['snow', 'ghost white', 'white smoke', 'gainsboro', 'floral white', 'old lace', 'linen', 'antique white', 'papaya whip', 'blanched almond', 'bisque', 'peach puff', 'navajo white', 'lemon chiffon', 'mint cream', 'azure', 'alice blue', 'lavender', 'lavender blush', 'misty rose', 'dark slate gray', 'dim gray', 'slate gray', 'light slate gray', 'gray', 'light grey'] root = Tk() scrollbar = Scrollbar(root) scrollbar.pack( side = RIGHT, fill=Y ) mylist = Listbox(root, yscrollcommand = scrollbar.set ) for c in COLORS: e = Label(mylist, text = c, background = c) mylist.insert(END,e ) e.pack(fill=X)#Problem line???? mylist.pack( side = LEFT, fill = BOTH ) scrollbar.config( command = mylist.yview ) mainloop() As you can see I have an interesting line shown as a "Problem line????". If this line is out I get a list of pairs of number showing the default 10 lines and the list of numbers is "scrollable". However if the line is in as shown above, I get a list 26 lines long, with the lovely colours nicely shown. If I drag the list to a shorter size, the scroll bar appears but its movement does not link with the list. It goes up an down nicely but the list stays still. This is rather inconvenient when trying to view the complete list of colours, which is 479 high! Thanks in anticipation of anyone being able to help me, it will be very much appreciated. Cheers, Rob

5 4

Re: [Tkinter-discuss] [Python-Dev] Binding problem
by Guido van Rossum Jan. 15, 2014

Jan. 15, 2014

Hey Rob, The place to get help with Tkinter is tkinter-discuss(a)python.org. I've CC'ed that list for you. --Guido On Tue, Jan 14, 2014 at 4:53 PM, Rob Ward <rl.ward(a)bigpond.com> wrote: > I apologise if I have come to the wrong place here, but 12hrs searching, > plus experimenting, on the WWW for advice on it has not yielded any > successful advice to resolve the issue. > > I am am having trouble binding an Entry widget to <Return> > > Here is the snippet (butCol is a Frame widget to put buttons,labels and text > entry down LHS) > > KS1=StringVar() > KS1.set("Key is ??") > butCol.ks1 > =Label(butCol,textvariable=KS1).grid(column=0,row=18,sticky=(N,W)) > > myKey = [0,2,4,5,7,9,11] #Begin in the key of C > KS2 =StringVar() > KS2.set("C") > butCol.ks2 > =Entry(butCol,width=20,textvariable=KS2).grid(column=0,row=19,sticky=(N,W)) > > The above lines all render correctly, but will not trigger off "entry" of > data at all on <Return> > > Adding the following line just crashes. > > butCol.ks2.bind("<Return>",chooseKey) > > I downloaded the Python 3 package from the recommended site last week to > begin this project (it was previously working OK in Skulptor, but I was not > prepared to develop it any further in that environment, though it was an > excellent starting environment). So I believe the Python language installed > is up todate. I have not previously installed Python so it should be > "clean". > > If you could give any direct advice I would be very grateful or if you can > direct me to your best "forum" site maybe I could use that. > > One overall observation that has frustrated me is how toi search for > information that relates to Python3 and the latest tkinter modules. I kept > finding old python or old Tkinter or combinations of both. Wrorking my way > through this was very time consuming and rarely productive. Is there any > advice on how to get the "latest" information off the WWW? > > > > Cheers, Rob Ward > > PS In my state of eternal optimism I have attached the whole file :-) > > PPS I have done some OOP in the past but not keen to jump in at the moment. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev(a)python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido)

3 2

Bind to a an Entry widget problems (tkinter/python3)
by Rob Ward Jan. 15, 2014

Jan. 15, 2014

I apologise if I have come to the wrong place here, but 12hrs searching, plus experimenting, on the WWW for advice on it has not yielded any successful advice to resolve the issue. I am am having trouble binding an Entry widget to <Return> Here is the snippet (butCol is a Frame widget to put buttons,labels and text entry down LHS) KS1=StringVar() KS1.set("Key is ??") butCol.ks1 =Label(butCol,textvariable=KS1).grid(column=0,row=18,sticky=(N,W)) myKey = [0,2,4,5,7,9,11] #Begin in the key of C KS2 =StringVar() KS2.set("C") butCol.ks2 =Entry(butCol,width=20,textvariable=KS2).grid(column=0,row=19,sticky=(N,W)) The above lines all render correctly, but will not trigger off "entry" of data at all on <Return> Adding the following line just crashes. butCol.ks2.bind("<Return>",chooseKey) I downloaded the Python 3 package from the recommended site last week to begin this project (it was previously working OK in Skulptor, but I was not prepared to develop it any further in that environment, though it was an excellent starting environment). So I believe the Python language installed is up todate. I have not previously installed Python so it should be "clean". If you could give any direct advice I would be very grateful. One overall observation that has frustrated me is how toi search for information that relates to Python3 and the latest tkinter modules. I kept finding old python or old Tkinter or combinations of both. Wrorking my way through this was very time consuming and rarely productive. Is there any advice on how to get the "latest" information off the WWW? Cheers, Rob Ward PS In my state of eternal optimism I have attached the whole file :-) PPS I have done some OOP in the past but not keen to jump in at the moment.

1 0

Issues converting TKinter application to Ttk
by Fleming, Land D. (JSC-ER111)[Jacobs Technology, Inc.] Jan. 6, 2014

Jan. 6, 2014

I have a Tkinter application that runs as intended, but I'm in the process of converting it to Ttk in order to get some of the new widget classes Ttk provides. I'm using Python 2.7.5 on a Windows 7 machine. I've run into two serious problems doing the conversion that I've been able to find work-arounds for, but I'm not sure if the problems are associated with undocumented peculiarities with Ttk or if I'm doing something wrong. I describe the application and the two problems below. I've worked with Tkinter for several months but only recently tried to using Ttk. If anyone knows of a repository where issues like these are documented, please let me know. Thanks The application frame is a subclass of PanedWindow defined as follows: import sys, os from Tkinter import * import ttk from ttk import * class App(ttk.PanedWindow): ... def __init__(self, master, **panedWindowOpts): PanedWindow.__init__(self, master, **panedWindowOpts) First problem: I found that the styles I defined for widgets in the application were ignored when I made the application's master an instance of Tk() as follows: root = Tk() app = App(root, style='My.TPanedwindow', orient=VERTICAL) After considerable trial and error (mostly error) I found that the styles worked as advertised, if I changed the application master to an instance of Toplevel rather than of Tk: top = Toplevel() app = App(top, style='My.TPanedwindow', orient=VERTICAL) top.mainloop() Second Problem: When the mainloop executed as above, what appeared to be an extraneous blank window was stacked on top of the application window. This window didn't appear when I was using basic Tkinter. I noticed that if I killed the extraneous window by clicking on the "X" in the window's upper right corner, it also killed the application, which suggested the "extraneous" window was really the root window. After searching the documentation and much trial and error, I found that I could get the root window to go away without killing my app by explicitly calling withdraw() on the root before running the mainloop: Tkinter._default_root.withdraw() app.mainloop() This would have been a show stopper if I hadn't been able to work around it, because I couldn't give an application to end users that pops up a meaningless empty window that they have to close themselves. I wasn't able to locate much documentation on the root window, and I only found out about _default_root by looking at Tkinter.py. Further, I found nothing to indicate that the root had a withdraw method, and just tried it after running out of all other options I could think of. Luckily, it worked.

2 2