Mailman 3 February 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

Re: [Tkinter-discuss] Tracebacks
by Bob Greschke April 12, 2014

April 12, 2014

On 2014-02-28, at 12:08, Bob Greschke <bob(a)passcal.nmt.edu> wrote: It doesn't, this would just be more elegant, right? It just seems funny that the interpreter doesn't help out this one little bit more. I'd even say why not just have a Python command that you put in your program (not on the #! line) that tells the interpreter what to globally do with traceback error messages, especially since these things can happen and the program just keep on running. "set stdtraceback to file X". For a non-threaded/non-GUI program it might not be that big of a deal -- it hits a bug and stops -- but for a big Tkinter program you could just keep selecting menus and buttons and never know there was a problem somewhere. Yes there is the logging and the traceback modules and all of that, but that's a lot of duplication of labor. The interpreter already knows everything, you just can't tell it what to do with the messages to make it helpful. It seems like a small oversight to me. On 2014-02-28, at 09:35, Cam <camfarnell(a)bitflipper.ca> wrote: > I'm probably not understanding the question. How does what you propose differ from wrapping your whole application in a try/except so that any uncaught exceptions result in information being written to error.txt? > > Cam > > On 14-02-28 11:33 AM, Bob Greschke wrote: >> This isn't quite a Tkinter thing, but why can't some clever person (I couldn't do it) make it possible for you to put something like this >> >> #! /usr/bin/python -t "/home/me/error.txt",stderr >> >> at the beginning of a Python program and have the interpreter direct all of the traceback messages to the file error.txt, and stderr? I've got a 43,000 line Tkinter/via X11 program and stupid users that won't tell me when it crashes -- if they even notice. Right now we create an xterm on their computer then execute and ssh to the server where the program resides. The errors come out in that xterm, but if the users quit they are gone. It seems like the interpreter would be the smartest place to put something like this since it controls everything, and so you don't have to try and guess in which section of code you misspelled a variable name and put it in a try-except. >> >> Isn't this reasonable? There are all kinds of questions about this problem, but never any really good solutions. I like this one. :) I just wouldn't have any idea how to do it, or if it's even possible. >> >> Bob >> >> _______________________________________________ >> Tkinter-discuss mailing list >> Tkinter-discuss(a)python.org >> https://mail.python.org/mailman/listinfo/tkinter-discuss >> > _______________________________________________ > Tkinter-discuss mailing list > Tkinter-discuss(a)python.org > https://mail.python.org/mailman/listinfo/tkinter-discuss >

4 4

tkRAD - XML widget building for Tkinter
by tarball69 March 11, 2014

March 11, 2014

Hello there, Would it be possible for me to aknowledge good people Tkinter has now a complete *XML widget building* library named *tkRAD*? Wiki URL: https://github.com/tarball69/tkRAD/wiki Project GitHub: https://github.com/tarball69/tkRAD Project downloads: https://github.com/tarball69/tkRAD/releases I've worked hard for this wiki wiki documentation, so please, read documentation before asking thousands of questions. Thanks a lot. -- View this message in context: http://python.6.x6.nabble.com/tkRAD-XML-widget-building-for-Tkinter-tp50478… Sent from the Python - tkinter-discuss mailing list archive at Nabble.com.

2 1

Tracebacks
by Bob Greschke March 1, 2014

March 1, 2014

This isn't quite a Tkinter thing, but why can't some clever person (I couldn't do it) make it possible for you to put something like this #! /usr/bin/python -t "/home/me/error.txt",stderr at the beginning of a Python program and have the interpreter direct all of the traceback messages to the file error.txt, and stderr? I've got a 43,000 line Tkinter/via X11 program and stupid users that won't tell me when it crashes -- if they even notice. Right now we create an xterm on their computer then execute and ssh to the server where the program resides. The errors come out in that xterm, but if the users quit they are gone. It seems like the interpreter would be the smartest place to put something like this since it controls everything, and so you don't have to try and guess in which section of code you misspelled a variable name and put it in a try-except. Isn't this reasonable? There are all kinds of questions about this problem, but never any really good solutions. I like this one. :) I just wouldn't have any idea how to do it, or if it's even possible. Bob

3 2

Differences on Mac and Windows
by Bhaskar Chaudhary Feb. 18, 2014

Feb. 18, 2014

Hi The following piece of code displays correctly on Windows PC but it displays all messed up in OS X (10.9.1 and others) as shown in attachment below. from Tkinter import * root = Tk() root.geometry('142x280+150+200') root.configure(background='#4D4D4D') mytext = Text(root, background='#101010', foreground="#D6D6D6", borderwidth=18, relief='sunken',width=16, height=5, font="Times 8 bold" ) mytext.insert(END, "Style is knowing \nwho you are, what \nyou want to say, \nand not giving a \ndamn.") mytext.grid(row=0, column=0, columnspan=6, padx=5, pady=5) root.mainloop() Any reasons why it shows the way it does on Mac. Thanks. Version Info: Python 2.7.3 >>>> Tkinter.__version__ > '$Revision: 81008 $' >>>> Tkinter.TclVersion > 8.5 >>>> Tkinter.TkVersion > 8.5 regards Bhaskar Chaudhary

6 11

Re: [Tkinter-discuss] Differences on Mac and Windows
by Kevin Walzer Feb. 14, 2014

Feb. 14, 2014

On 2/14/14, 10:21 AM, Bhaskar Chaudhary wrote: > Hi Kevin > > On Windows it looks like the following attachment. > > regards > Bhaskar Thank you. As I expected, that is simply the difference in the font rendering engines on both platforms. 8 point Times Bold is as unreadable on Word on the Mac is it is in Tk. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com

3 6

Interrupt a long process
by Vasilis Vlachoudis Feb. 14, 2014

Feb. 14, 2014

Hi all, in my canvas sometimes it happens to have a long process to insert lots of items. This typically takes a lot of time (up to min) so I want to give the possibility to the user to interrupt this process. And since I am adding to the Canvas I cannot push it on a thread. So in the main thread, in the big loop, once I exceed a certain time I display a button to interrupt the long process and I call the update_idletasks() periodically. However it is not possible for the user to click on the button. It seems that the update_idletasks doesn't update the "Button-1" messages How can I do it? Thanks in advance Vasilis

2 2

Re: [Tkinter-discuss] root
by Pierre Dagenais Feb. 4, 2014

Feb. 4, 2014

On 14-02-04 04:07 PM, Bryan Oakley wrote: > You must have a root window. If you do not create one, one will be created > for you. That's just how tkinter works. > > PEP-20 says "Explicit is better than implicit", so explicitly creating the > root window is better than letting tkinter implicitly create it for you. > Makes a lot of sense! Thank you, > > On Tue, Feb 4, 2014 at 2:08 PM, Pierre Dagenais <pierre.dagenais(a)ncf.ca>wrote: > >> This program, example1.py: >> >>> from tkinter import * >>> >>> root = Tk() >>> canvas = Canvas() >>> canvas.pack() >>> >>> root.mainloop() >> >> >> and this one, example2.py: >> >>> from tkinter import * >>> >>> canvas = Canvas() >>> canvas.pack() >>> >>> mainloop() >> >> do exactly the same thing, as far as I can tell. Yet, most examples I >> find on the net use the first form. Why? >> I must be missing something, but I can't figure what is the utility of >> root. Can you help? >> >> PierreD. >> _______________________________________________ >> Tkinter-discuss mailing list >> Tkinter-discuss(a)python.org >> https://mail.python.org/mailman/listinfo/tkinter-discuss >> >

1 0

root
by Pierre Dagenais Feb. 4, 2014

Feb. 4, 2014

This program, example1.py: > from tkinter import * > > root = Tk() > canvas = Canvas() > canvas.pack() > > root.mainloop() and this one, example2.py: > from tkinter import * > > canvas = Canvas() > canvas.pack() > > mainloop() do exactly the same thing, as far as I can tell. Yet, most examples I find on the net use the first form. Why? I must be missing something, but I can't figure what is the utility of root. Can you help? PierreD.

1 0