Mailman 3 October 2011 - 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

ttk.Notebook - how to bind to tab events (tab caption has focus or mouseover)
by python＠bdurham.com May 9, 2012

May 9, 2012

I'm using the ttk.Notebook widget. What object do I bind to capture events related to specific tabs? I would like to trap when a tab caption gets keyboard focus ('<FocusIn>') and when the mouse pointer is over a specific tab caption ('<Enter>'). I can trap mouse clicks on tabs (<Button-1>, <Button-3>), but I can't find a way to determine what tab a user clicked on in the case of a right click. Thank you, Malcolm

3 5

tag insertion while writing
by Alessandro Magni Oct. 21, 2011

Oct. 21, 2011

1 0

Re: [Tkinter-discuss] [Tutor] tkinter binding issues
by Wayne Werner Oct. 20, 2011

Oct. 20, 2011

Forwarding to the list... On Thu, Oct 20, 2011 at 9:06 AM, Elwin Estle <chrysalis_reborn(a)yahoo.com>wrote: > Thank you very much. That was a great help. I briefly considered the > lambda idea, but since I really don't understand the whole lambda thing (I > used an explanation from effbot for my buttons...but didn't really know > what I was doing) ... didn't even attempt it. The one that was really > driving me crazy was the clear form thing. I tried your idea of changing > the focus before calling the tkmessagebox. Worked like a champ! Lambdas are quite nice - they let you create a single, one line function with minimal effort. def add(x, y): return x + y add2 = lambda x, y: x + y add(2, 3) # Returns 5 add2(2, 3) # Also returns 5 I highly recommend firing up your interpreter and playing around with lambda functions. There are only a few places that they're appropriate, but they make those few things a _lot_ easier. HTH, Wayne

1 0

Re: [Tkinter-discuss] Calculating a ripening tomato
by Brian Meanley Oct. 19, 2011

Oct. 19, 2011

>Not sure that colour temperature would be all that relevant, >since it's concerned with black body radiation. You would >have to heat your tomatoes to a rather uncomfortable degree >for that to affect their colour... True. I never meant to imply that it was a bolt-on solution to the problem. I was merely trying to give a jumping off point for some further research (as the OP also mentioned other situations that he was interested in such as sunsets, etc...). I think that with a bit of work, the underlying concepts of plotting points in xy, rather than manipulating individual RGB channels, could possibly be adopted to suit the OP's needs. Anyways, didn't mean to take the talk off topic. -Brian

1 0

Re: [Tkinter-discuss] Calculating a ripening tomato
by Brian Meanley Oct. 19, 2011

Oct. 19, 2011

Not that I have a solution for you, but figured that I would share some of my experiences with something similar... The suggestion of using HSL rather than RGB is a good one, as calculating this in RGB would be rather hit or miss most likely... However, I think perhaps you might want to try calculating the raw chromaticity as CIE xy coordinates, rather than HSL, and then doing your color conversions from there. From the papers that were linked to earlier regarding the topic, it seemed that the preferred color-space for calculations was LAB, which would coincide rather nicely to the xyY coordinates. Many things are calculated along these lines, perhaps the most common being light/color temperature using the Planckian Locus: http://en.wikipedia.org/wiki/Planckian_locus. Unfortunately as you can see, the algorithms used are rarely 'simple' (at least to calculate initially), and approximations are often used. Basically, if you can find a 'curve' on on the color-chart that matches the color-ranges that you are after, than it just becomes a matter of figuring out the function(s) that best approximates it. I have a python/tkinter app that I created that you could take a look at for an implementation of the above color-temperature scale if it would help you out. I won't post all the code here, but you can download it at the links below. You'll have to excuse the code however, I make my living as a vfx artist, and I'm rather a hack when it really comes to coding... Anyways, you can find it here: http://wiki.brianmeanley.com/wiki/LightTools.py . For the main code involving the color calculations, look in the 'bhm_color.py' module. A non-gui version can be found here: http://www.brianmeanley.com/blog/?page_id=349 Color-science is a pretty hefty subject in its' own right, but it can be an extremely interesting and 'fun' one too if you take an interest in it. I would think that doing a bit of digging into the color temperature examples/links above might give you some insight into what it is that you are hoping to accomplish, as well as the other examples that you mentioned. I would also highly suggest checking out http://brucelindbloom.com/ for some good info regarding the math behind most color conversions and more. Good luck! -Brian (PS, sorry if I messed this mailing list thing up, I have never actually posted to this list before...)

3 2

Re: [Tkinter-discuss] Tkinter-discuss Digest, Vol 92, Issue 7
by Steve Solomon Oct. 19, 2011

Oct. 19, 2011

Thank you all, Peter Otten's patch worked right off the bat. Now that Peter explained the core of the problem I'll be able to tinker with the code to dig deeper. Steve On Mon, Oct 17, 2011 at 3:00 AM, <tkinter-discuss-request(a)python.org> wrote: > Send Tkinter-discuss mailing list submissions to > tkinter-discuss(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/tkinter-discuss > or, via email, send a message with subject or body 'help' to > tkinter-discuss-request(a)python.org > > You can reach the person managing the list at > tkinter-discuss-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Tkinter-discuss digest..." > > > Today's Topics: > > 1. Re: Limit to the number of canvases in a top_level object? > (Peter Otten) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 16 Oct 2011 15:43:26 +0200 > From: Peter Otten <__peter__(a)web.de> > To: tkinter-discuss(a)python.org > Subject: Re: [Tkinter-discuss] Limit to the number of canvases in a > top_level object? > Message-ID: <j7emvl$m7$1(a)dough.gmane.org> > Content-Type: text/plain; charset="ISO-8859-1" > > Steve Solomon wrote: > > >>> Is there a limit to the number of canvases in a top_level object -- > one > >>> maybe ? I have been trying to solve this problem with an application > for > >>> several weeks. In the application I have two canvases, each with a grid > >>> of rectangle objects. They display perfectly but when I try to interact > >>> with the rectangles they behave anomalously. Using > >>> canvas.find_closest(event.x, event.y) the rectangles in the first drawn > >>> canvas behave normally, allowing configuring each, but within the > second > >>> canvas the rectangles report back the id of only one of the rectangles > >>> and an attempt to change the fill-color of any one is applied only to > >>> the last item in the grid. > >>> > >>> Your thoughts would be appreciated, thank you > > > I'm a bit in the tall weeds, please excuse the mess (in the attached > > code). > > The best time to clean up your code is always right now; the second best > time is when you run into an error ;) > > > from Tkinter import * > > import random > > import palettebuilder as pb > > from colorservices import getHSV > > > > def randomColors(count=1, sorted=False): > > "returns list of color strings in #nnnnnn hexidecimal format" > > rtn = [] > > for x in range(count): > > intgr = random.randrange(0, 16777215, 1) > > hex = "#{:0>6X}".format(intgr) > > rtn.append(hex) > > if sorted: > > "the folowing should be sorted by ..." > > # rtn.sort(key=lambda rtn: getHSV(rtn)[2]) #...value > > rtn.sort(key=lambda rtn: getHSV(rtn)) #...full HSV > > return rtn > > > > class test(Toplevel): > > def __init__(self): > > Toplevel.__init__(self) > > self.config(height = 500, width = 500) > > self.activeCanvas = None > > self.bind("<KeyPress-c>", self.reportXY) > > size = 180 > > frameOne = Frame(self, height = 200, width =200, bg = "pink") > > self.canvasOne = Canvas(frameOne, height=size, width=size, > background="#bababa") > > self.canvasOne.grid(row = 0, column = 0, sticky = W ) > > frameTwo = Frame(self, height = 200, width =200, bg="light blue") > > self.canvasTwo = Canvas(frameTwo, height=size, width=size, > bg='#bababa') > > self.canvasTwo.grid(row = 1, column = 1) > > self.canvasOne.bind("<Enter>", self.makeOneActive) > > self.canvasTwo.bind("<Enter>", self.makeTwoActive) > > frameOne.grid(row = 0, column = 0, sticky = W ) > > frameTwo.grid(row = 1, column = 1, sticky = E ) > > colors = randomColors(64, sorted = True) > > pb.DrawPalette(self.canvasOne, colors, columns = 8) > > colors = randomColors(64, sorted = True) > > pb.DrawPalette(self.canvasTwo, colors, columns = 8) > > > > def makeOneActive(self, event): > > self.activeCanvas = self.canvasOne > > print "one = active self.activeCanvas>>>", > type(self.activeCanvas) > > > > def makeTwoActive(self, event): > > self.activeCanvas = self.canvasTwo > > print "two = active self.activeCanvas>>>", > type(self.activeCanvas) > > > > def reportXY(self, event): > > print event.x, event.y > > item=self.activeCanvas.find_closest(event.x, event.y) > > print self.activeCanvas.itemcget(item, "tags"), "item>>", item > > self.activeCanvas.itemconfigure(item, fill = "red") > > > > root = Tk() > > root.withdraw() > > test() > > #for x in range(10): > > # print randomColors(10) > > # print "\n" > > root.mainloop() > > > > You bind the reportXY() method to an event triggered by your Toplevel > subclass, so the event instance contains coordinates relative to the test > widget. On the other hand the Canvas.find_closest() method expects > coordinates in terms of the canvas widget. The difference doesn't matter > for > canvasOne which is located at the origin of the toplevel, but gives wrong > results for canvasTwo with its non-zero offset. > > While the diagnosis was easy it took me a while to find a way to convert > between the two coordinate systems. The following seems to work: > > def reportXY(self, event): > canvas = self.activeCanvas > > dx = self.winfo_rootx() - canvas.winfo_rootx() > dy = self.winfo_rooty() - canvas.winfo_rooty() > > x = event.x + dx > y = event.y + dy > > print "before", event.x, event.y > print "after", x, y > > item = canvas.find_closest(x, y) > print canvas.itemcget(item, "tags"), "item>>", item > canvas.itemconfigure(item, fill="red") > > Let me know if you find a better way or run into a problem with my > approach. > > > > ------------------------------ > > _______________________________________________ > Tkinter-discuss mailing list > Tkinter-discuss(a)python.org > http://mail.python.org/mailman/listinfo/tkinter-discuss > > > End of Tkinter-discuss Digest, Vol 92, Issue 7 > ********************************************** >

1 0

Re: [Tkinter-discuss] Calculating a ripening tomato
by Francesco Bochicchio Oct. 18, 2011

Oct. 18, 2011

A quick googling tourned out with this: http://www.scielo.br/scielo.php?script=sci_arttext&pid=S0102-05362004000300… Which seems to be related to what you are looking for... only a lot more complex than a simple formula. I suspect a look-up table does mot seem so bad, now :-) Ciao ------- FB

5 5

Calculating a ripening tomato
by Bob Greschke Oct. 17, 2011

Oct. 17, 2011

Do you think there is a formula (probably three of them) for calculating the RGB colors for the background color of a widget of a tomato ripening from green to red with, let's say, an input of 0-100%? It's not just Red 0-255 and green 255-0, because the brown shows up in the middle and doesn't look good at all. There must be some blue in there somewhere, but I'd like to calculate the values, instead of just looking them up in a list of 100 RGB values. I'd think there would be something like this for various things somewhere. Autumn leaves turning colors, sunsets... I've done widget coloring for things like different elevations and water depths, but for those I just binned the values into 16 or thereabouts bins and looked up the color I wanted to use. Calculating the values would be more elegant, right? :) I searched around a little, but just kept getting schooled on how to grow tomatoes. Bob

1 0

Limit to the number of canvases in a top_level object?
by Steve Solomon Oct. 16, 2011

Oct. 16, 2011

Hello, Is there a limit to the number of canvases in a top_level object -- one maybe ? I have been trying to solve this problem with an application for several weeks. In the application I have two canvases, each with a grid of rectangle objects. They display perfectly but when I try to interact with the rectangles they behave anomalously. Using canvas.find_closest(event.x, event.y) the rectangles in the first drawn canvas behave normally, allowing configuring each, but within the second canvas the rectangles report back the id of only one of the rectangles and an attempt to change the fill-color of any one is applied only to the last item in the grid. Your thoughts would be appreciated, thank you Steve

3 3