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

divergent behaviour
by Alan Gauld June 25, 2014

June 25, 2014

I've observed a strange difference in the behaviour of one of my event handlers, I'm wondering if anyone knows the explanation. I have a form with a list box and a set of buttons. When you highlight a list item you can press the Edit button and it calls evEdit() which opens an edit dialog in the centre of the parent window. However I also bound the double click event to evEdit and if you double click the same item it opebns the dialog in the centre of the screen. Does anyone know why double-click and button versions of the same method result in different locations? I'm assuming that somehow the dialog (TopLevel widget) sees the screen as its parent in one version but the original window as parent in the other - maybe...? PS. If necessary I'll try to produce a short example to illustrate, but the existing code is over 500 lines so a tad too long to post. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.flickr.com/photos/alangauldphotos

3 13

About making Text.tag_*range methods more consistent
by Saimadhav Heblikar June 17, 2014

June 17, 2014

Some code, >>> from tkinter import Text >>> text = Text() >>> text.pack() >>> text.insert('insert', 'ab cd ef') >>> text.tag_add('red', '1.0','1.2') >>> text.tag_add('red', '1.6', '1.8') >>> text.tag_prevrange('red', 'end') ('1.6', '1.8') >>> text.tag_ranges('red') (<textindex object: '1.0'>, <textindex object: '1.2'>, <textindex object: '1.6'>, <textindex object: '1.8'>) >>> text.tag_nextrange('red', '1.0') ('1.0', '1.2') I propose that Text.tag_ranges(tag) return a list of tuples (start index, end index), instead of a list like [start index1, endindex1, startindex2, endindex2....etc] To be more even more consistent, tag_ranges tuples should contain indexes similar to the ones returned by tag_prevrange/tag_nextrange i.e. strings instead of textindex objects. So, the above output would have been >>> text.tag_ranges('red') (('1.0', '1.2'), ('1.6', '1.8')) If there is a reason for current behavior, can you link me to it? -- Regards Saimadhav Heblikar

3 4

Text widget "lags" when doing fast updates with increased window heights
by Thiago Padilha June 10, 2014

June 10, 2014

I'm currently implementing a sample UI for neovim(http://neovim.org/), and decided to use Tkinter/python due to the popularity/simplicity of the platforms. The problem I'm having is that tkinter seems to "stack" UI updates when the window height crosses a certain threshold. Here is a video that shows the problem: http://youtu.be/sgE2C9lLqQQ The right window is a terminal emulator running neovim, and the left window is the Tkinter UI program connected to neovim. The idea is that the tkinter UI should mirror neovim terminal screen, including dimensions. Notice that in this video I don't take focus away from the terminal window, so the only events Tk has to process come from the connection to neovim(virtual <<nvim>> events which describe screen updates) The first part of the video shows that everything works nicely when the window height is small, but starts to lag updates when I increase the height. I think what I'm trying to implement is close to a terminal emulator(must handle large bursts of text updates efficiently) but I'm very inexperienced in GUI programming. Is Tkinter a wise choice for this task? If yes, then what am I doing wrong?( The code for the Tkinter program is here: http://pastebin.com/0c8cjsmR and my OS is ubuntu 12.04(running as a VM under windows 7) Thanks in advance Thiago.

1 0

About making Text.tag_*range methods more consistent
by Saimadhav Heblikar June 8, 2014

June 8, 2014

Some code, >>> from tkinter import Text >>> text = Text() >>> text.pack() >>> text.insert('insert', 'ab cd ef') >>> text.tag_add('red', '1.0','1.2') >>> text.tag_add('red', '1.6', '1.8') >>> text.tag_prevrange('red', 'end') ('1.6', '1.8') >>> text.tag_ranges('red') (<textindex object: '1.0'>, <textindex object: '1.2'>, <textindex object: '1.6'>, <textindex object: '1.8'>) >>> text.tag_nextrange('red', '1.0') ('1.0', '1.2') I propose that Text.tag_ranges(tag) return a list of tuples (start index, end index), instead of a list like [start index1, endindex1, startindex2, endindex2....etc] To be more even more consistent, tag_ranges tuples should contain indexes similar to the ones returned by tag_prevrange/tag_nextrange i.e. strings instead of textindex objects. So, the above output would have been >>> text.tag_ranges('red') (('1.0', '1.2'), ('1.6', '1.8')) If there is a reason for current behavior, can you link me to it? -- Regards Saimadhav Heblikar

1 0