Mailman 3 November 2019 - Tkinter-discuss

tkinter.PhotoImage to PIL.Image
by Vasilis Vlachoudis Dec. 6, 2019

Dec. 6, 2019

Hi all, I have several images loaded as tkinter.PhotoImage, I want some to resize them The PhotoImage zoom accepts only integer values and the result is not that great. While if load them with PIL resize them and then convert to PIL.ImageTk it is much better. I found several references on how to convert from PIL to tkinter but I cannot find how to do the opposite so I can use the PIL resizing with the existing tkinter images. Many thanks Vasilis

2 4

busy mouse cursor for application
by Vasilis Vlachoudis Nov. 28, 2019

Nov. 28, 2019

Hi all, how can I display the cursor as the watch for the whole application. When I set it on the toplevel window as self.toplevel.config(cursor="watch") it displays the cursor almost everywhere (I believe where the cursor is "") except for the widgets like Entry, Text that have the cursor="xterm" or anything that has a custom cursor. Is there a way to set the "watch" for everything and restore it later on Vasilis

2 2

ttk styles - is it possible to have one per widget?
by Mike Barnett Nov. 23, 2019

Nov. 23, 2019

I have come back to this problem several times and have asked friends for help, but I never seem to crack this nut. What I am trying to do is "style" ttk widgets in a way that each one can have their own unique settings. I've not found code or pseudo-code that does what I'm looking for. Is it possible for ttk widgets to work like tk widgets in that each can have their own unique settings like background color, text color, etc? Any code or pointers to pages with some code that I can lift would be awesome as I can't seem to write my own that works. Happy to share the kinds of things I've tried if it would help. Thank you for your time -mike

2 2

Tkinter to Qt-whatever
by Robert Greschke Nov. 14, 2019

Nov. 14, 2019

So pigs have started sprouting wings and I guess "we" (work) are going to start shifting to Qt/PySide2/whatever. I've been playing around for a few weeks and what a mess compared to Tkinter. Does anyone know/think something like Qt-based classes could be written that are called just like and act just like Tkinter Button()s/Frame()s/Entry()s/etc. but spit out Qt widgets? I've got tens of thousands of lines of just Tkinter code (in hundreds of thousands of lines of Python code), that I probably won't HAVE to rewrite, but something like that would be pretty spiffy for running the old stuff and for writing new stuff. Maybe someone will come to their senses and well go back to Tkinter. :) There is nothing Qt widgets do that I need beyond the Tkinter basics...if I can figure out how to even do that stuff. I know some functions may not work out, but it could be worth a try, and either way I guess I'd get to know Qt better. Thanks! Bob

4 5

Re: [Tkinter-discuss] Tkinter to Qt-whatever
by Robert Greschke Nov. 13, 2019

Nov. 13, 2019

> On 2019-11-13, at 10:16, Mike Barnett <mike_barnett(a)hotmail.com> wrote: > > Ohhhh….. on a Mac… yea, not a good combination with tkinter from my experience. It works great if you compile your own Python and link to an included standard Tcl/Tk. We've been doing that since we started using Macs. 12, 15 years? It looks and works just like the normal/standard Linux or Windows installations. But "they" don't want to do that anymore. Someone may have figured out a workaround in Anaconda, but that's a whole other bag of worms. > > Most Mac users of PySimpleGUI are using PySimpleGUIQt because of this. > > PySimpleGUI may very well not have the “Depth” you need. Because the APIs are meant to be portable across multiple GUI frameworks, things like Toolbars are something users need to create on their own, at least for now. Yeah, we'll see. I don't even use things as "fancy" as Toolbars, but I may change the look of things a bit too much, or maybe not. > > Simple… that’s the main focus of PySimpleGUI… to keep things simple, especially for the developer. No need to write 40 lines of code when 4 will work just as well. > > PySimpleGUI is extendable. There is a section in the documentation about accessing the underlying “Widgets”. Each PySimpleGUI Element tends to map 1 to 1 with a GUI Framework’s Widget. This gives advanced developers access to changing more detailed settings for a Widget. It’s not, however, meant to be how the normal programming of PySimpleGUI is done. Cool. Hope I can get to it today. Thanks! > > > > From: Robert Greschke <robert(a)greschke.com <mailto:robert@greschke.com>> > Sent: Wednesday, November 13, 2019 12:11 PM > To: Mike Barnett <mike_barnett(a)hotmail.com <mailto:mike_barnett@hotmail.com>> > Cc: Python-Tkinter <tkinter-discuss(a)python.org <mailto:tkinter-discuss@python.org>> > Subject: Re: [Tkinter-discuss] Tkinter to Qt-whatever > > Hi! > > I saw that, but didn't take a look at it. Did I even get a choice? Hmm. I'll look and see if it can handle me. The trigger for all of this was the way things Tkinter look/feel in macOS. I guess I should give tix/ttk stuff a look, again, too. Our stuff doesn't need to look native, but consistent (Linux/Mac/Win) would be nice. The default Linux look is even the same as it was when stuff was still running on SunOS. Everything is generally "big and clunky" which is really nice for field work. No finesse required when the Sun is in your eyes and the wind chill factor is 0F. > > I've looked at a bunch of documentation online for Qt stuff, got three books, and all of it is just PyDoc quality and 'Hello World' stuff. "...setIconSize(): This sets the icon size of the toolbar icons for this main window." No!! Never would have guessed that. I sleep with Grayson's book to keep anything from happening to it. :) > > Other than just the standard .config() things I haven't needed to really mess with widgets. Color, padding, maybe the width of the scrollbars (they got really narrow on some macOS versions), etc. A bit of Canvas drawing. Rewriting would be OK if there is even less writing! > > These are things Tkinter has been fine for: > > www.passcal.nmt.edu/~bob/passcal/software/index.html <https://eur02.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.passcal.…> > > It would just be more of the same from here on. > > Thanks! > > Bob > > > On 2019-11-13, at 09:14, Mike Barnett <mike_barnett(a)hotmail.com <mailto:mike_barnett@hotmail.com>> wrote: > > Hi there > > Take a look at PySimpleGUI (http://www.PySimpleGUI.org <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.PySimp…>) > > With it you can write your code once and then easily move between tkinter, Qt, WxPython and Remi (runs in browser). > > Sometimes the only change needed is to the import statement. Other times only slight changes are needed. > > If you're using only the basic kinds of Widgets and aren't getting overly fancy with styles (aren't changing things like scrollbars down deep inside tkinter), then moving across the GUI frameworks is pretty easy. > > A number of the "Demo Programs" found on the GitHub run on multiple GUI frameworks by only changing the import. The OpenCV ones are great examples of this. > > But you will be required to "rewrite" your tkinter code. PySimpleGUI code is up to 10x shorter than tkinter code so it could happen a lot quicker than you think. > > TONS of documentation is available. The Cookbook is being updated daily at the moment and you can run a bunch of sample code on Trinket (https://pysimplegui.trinket.io/demo-programs <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpysimpleg…>). > > It is certainly worth a look. > > -mike

1 0

Re: [Tkinter-discuss] Tkinter to Qt-whatever
by Robert Greschke Nov. 13, 2019

Nov. 13, 2019

Hi! I saw that, but didn't take a look at it. Did I even get a choice? Hmm. I'll look and see if it can handle me. The trigger for all of this was the way things Tkinter look/feel in macOS. I guess I should give tix/ttk stuff a look, again, too. Our stuff doesn't need to look native, but consistent (Linux/Mac/Win) would be nice. The default Linux look is even the same as it was when stuff was still running on SunOS. Everything is generally "big and clunky" which is really nice for field work. No finesse required when the Sun is in your eyes and the wind chill factor is 0F. I've looked at a bunch of documentation online for Qt stuff, got three books, and all of it is just PyDoc quality and 'Hello World' stuff. "...setIconSize(): This sets the icon size of the toolbar icons for this main window." No!! Never would have guessed that. I sleep with Grayson's book to keep anything from happening to it. :) Other than just the standard .config() things I haven't needed to really mess with widgets. Color, padding, maybe the width of the scrollbars (they got really narrow on some macOS versions), etc. A bit of Canvas drawing. Rewriting would be OK if there is even less writing! These are things Tkinter has been fine for: www.passcal.nmt.edu/~bob/passcal/software/index.html <http://www.passcal.nmt.edu/~bob/passcal/software/index.html> It would just be more of the same from here on. Thanks! Bob > On 2019-11-13, at 09:14, Mike Barnett <mike_barnett(a)hotmail.com> wrote: > > Hi there > > Take a look at PySimpleGUI (http://www.PySimpleGUI.org) > > With it you can write your code once and then easily move between tkinter, Qt, WxPython and Remi (runs in browser). > > Sometimes the only change needed is to the import statement. Other times only slight changes are needed. > > If you're using only the basic kinds of Widgets and aren't getting overly fancy with styles (aren't changing things like scrollbars down deep inside tkinter), then moving across the GUI frameworks is pretty easy. > > A number of the "Demo Programs" found on the GitHub run on multiple GUI frameworks by only changing the import. The OpenCV ones are great examples of this. > > But you will be required to "rewrite" your tkinter code. PySimpleGUI code is up to 10x shorter than tkinter code so it could happen a lot quicker than you think. > > TONS of documentation is available. The Cookbook is being updated daily at the moment and you can run a bunch of sample code on Trinket (https://pysimplegui.trinket.io/demo-programs). > > It is certainly worth a look. > > -mike

1 0