Announcements

[MikeTheWatchGuy]

Announcements - New Features, Design Patterns, and Methods

I'm unsure how GitHub sends out updates. I don't think people are informed about Wiki changes for example. I've been announcing new features and more importantly, new ways of doing things, on the Wiki. I'm going to put announcements here so they are more visible. If there are objections about the traffic, well, what can I say, it's a busy/active project.

[MikeTheWatchGuy]

New use pattern - Element lookup using Keys

keys can be used to lookup Elements. As a result, all Elements are capable of having a key, including non-output elements such as a Text Element.

To get an element object from a form, you call
form.FindElement(key)

This is the new, preferred method for doing Updates on elements.

Previously if you wanted to output something to a Text Element, you needed to create the text element outside of the form layout and keep that text element variable around so you can call text_element. Update('new text')

The new design pattern is thus:
In your form layout, include a key on your Element:

layout = [[sg.Text('My text', key='text')]]

Later in your code you can update this Text Element by making this call, assuming the variable form is your FlexForm object:

form.FindElement('text').Update('new text')

The Demo programs have all been updated to use this new technique. This capability and its impact on the length of programs led to pushing version 2.30 out the door quickly.

[MikeTheWatchGuy]

Borderless Windows are Here

Try them on your next form.
Add this to your FlexForm call:
no_titlebar = True

You can expect to see some of these in the Demo programs.

You can click anywhere on the window and drag to move it. Don't forget to put an exit key on these windows.

Be sure and make an "exit" button or you'll be running task manager to close your windows. The reason is the when you turn on this option, you will not see an icon on your taskbar for the window. This happens on both Windows and Linux. Thus, if you do not supply an exit button, the user will have no means to close the window.

[MikeTheWatchGuy]

Grab Anywhere

Tonight's change is perhaps going to be a really cool thing or one that is going to piss people off.

But, hey, I like it this way. If you don't, setgrab_anywhere = Falsein your call to FlexForm.

As the name implies, you can grab and drag your window using any point on the window, not just the title bar. I was only enabling this when the title bar was turned off. I think it's a much superior way to interact with a window.

FlexForm is becoming quite the call!
def __init__(self, title, default_element_size=DEFAULT_ELEMENT_SIZE, default_button_element_size = (None, None), auto_size_text=None, auto_size_buttons=None, scale=(None, None), location=(None, None), button_color=None, font=None, progress_bar_color=(None, None), background_color=None, is_tabbed_form=False, border_depth=None, auto_close=False, auto_close_duration=DEFAULT_AUTOCLOSE_TIME, icon=DEFAULT_WINDOW_ICON, return_keyboard_events=False, use_default_focus=True, text_justification=None, no_titlebar=False, grab_anywhere=True):

So, enjoy a lazy way of interacting with windows on me.

You will want to turn if off for forms with a SLIDER. you need the slider to move, not the window. I'll update the Demos that use sliders to turn off the grab_anywhere.

[MikeTheWatchGuy]

Tables

This one has been requested a number of times. Rather than make a Table Element, decided to see if the current PySimpleGUI is capable of making nice tables using standard Elements. The answer seems to be yes, it's possible with existing Elements. The key was to enable text justification in the InputText element. By right justifying the text in those Elements, it's possible to create a nice looking table.

Here's an example using a ComboBox and Input Elements.

You'll find the code that generated the table in the file Demo_Table_Simulation.py. It requires the latest PySimpleGUI from GitHub in order to use the justification setting.

This is a "live keyboard" demo. It updates the table values as you are typing.

There are 3 fields at the top of the table. If you enter a value into the 3rd field, the cell that the other 2 cells represents will be changed to that value. Enter 1, 2, 1234 and cell (1,2) will be changed to 1234.

There is a new trick demonstrated in this demo that shows off the power of Python. Rather than pass in a string as the key to the Input Elements, I passed a tuple. Nothing about the key requires it to be a string. The only requirement is that you use the same type to look up the element when you call FindElement or use the key to read the return values.

This is the code that makes the Input Elements:

    for i in range(20):
        inputs = [sg.In('{}{}'.format(i,j), size=(8, 1), pad=(1, 1), justification='right', key=(i,j), do_not_clear=True) for j in range(10)]

See how the key is set to (i,j). This allow me to easily find the Element that is represented by (i,j) later. What to access the cell at (0,0)? This you would make this call:
form.FindElement((0,0))

Hopefully this is enough capability for the folks that need tables in their forms/window.

[MikeTheWatchGuy]

Three Point Oh!

So maybe I kinda screwed up the numbering when the last one became 2.30. I didn't think about it looking like 2.3 also. Doh!

There have been a lot of changes lately so perhaps it's time for a major bump.

It's a clean slate

[MikeTheWatchGuy]

keep_on_top = True

What might this setting do in a call to FlexForm? If you guessed create a window that's ways on top you're right.

This one little flag enables cool floating toolbars that stay on top of all of your other windows. I'll admit a large portion of this project is for selfish purposes, that I have a platform to develop tools on top of.

Now I've got this nifty toolbar on the top part of my screen, always ready to launch or do something.

[MikeTheWatchGuy]

3.0.2 release today to turn off the grab_anywhere feature for non-blocking forms. tkinter is printing out a warning/error message when the form is closed using a button. Doesn't appear to have any effect on the overall functioning, but it's distressing to see. Better to disable this feature for now.

Plan is to add back an override mechanism should a user want it.

[MikeTheWatchGuy]

RELEASED 3.0.2

[MikeTheWatchGuy]

Floating Toolbar - New demo program

This is an always-on-top, compact floating toolbar. They are super-handy to leave running. Something satisfying about writing code that then gets used often, especially if they make you much more efficient.

[MikeTheWatchGuy]

Async Forms

Updated the Readme / primary doc to discuss the use of non-block forms.

As explained in the documentation there are a number of techniques to move away from async forms including using the change_submits = True parameter for elements and return_keyboard_events = True

[MikeTheWatchGuy]

Floating Desktop Widgets

I've discovered that in about 30 lines of code you can create a floating desktop widget.

If you click the pause button, it switches to Run.

This "Widget" is always on top of the other windows.

Looking for a way of launching these in a way that have no taskbar icons. If launched from PyCharm it behaves this way. If launched from a Toolbar, the toolbar's window is attached to the timer. Close it and the timer closes.

This demo is the first time I've ever combined a ReadNonBlocking with a Read in the same form. The reason for using it in this program is that while the timer is paused, there' s nothing happening so why have the program running the loop when it can wait for the user to do something like click a button. When the button is clicked we return from the Read call.

Thank you to jfong for sending an interesting version of this program. His ideas have rolled into a into the project code many times.

[MikeTheWatchGuy]

Menus are done

The last of the big features, Menus, was just released to GitHub. With it comes the ability to get the look and feel of a windows program. I don't know if the architecture will lend itself to being used this way or not, but it did seem like a useful feature to add..

[MikeTheWatchGuy]

3.7 Support

Thanks to @mrstephenneal we can now say that PySimpleGUI works on Python 3.7. There was a button issue causing trouble. Looks like it's fixed now so I think 3.7 is now safe to with PSG.

[MikeTheWatchGuy]

Release 3.01.00

Menus! (and a Listbox.Update bug) are the big features.

Since the Menu code is somewhat isolated, and I want to get some users on it, decided to go ahead and push it all out there in 3.01.00

I didn't mention this in the readme section on menus, but by default (you can't currently turn it off) menus are detachable. If you double-click the dashed line then you get a floating version of that menu. Should make for some pretty interesting user interfaces?

[MikeTheWatchGuy]

3.1.1

There have been enough bug fixes to trigger another PyPI release. People have been doing more and more with the Update method. These fixes were mostly in those methods.

[MikeTheWatchGuy]

Update methods updated

Added the ability to enable / disable all input elements.
Set parameter disable=True to disable, disable=False to enable, disable=None to leave it alone

A number of Demo programs also refreshed.

Expect a PyPI release soon.

Note that some Update method changes also changed parameter names from new_value to value, new_values to values. Some were different than others. Removed new_ so they all match now. Sorry to those living on the bleeding edge!

Here's a before/after. Elements towards the bottom of the window were disabled.

Yes, even buttons can be disabled now. No more needing to gray out your own buttons!

[MikeTheWatchGuy]

3.1.2

Big change this time around is the ability to disable widgets. All input widgets have an Update method that has the parameter disabled that you set to True if you want to disable it.

A few critical bugs in there too which pushed up the release to today.

[MikeTheWatchGuy]

Resizable Windows, Font settings for input text elements, beginnings of Treeview Element

You can stretch windows bigger now and some of the elements will resize with the window. **

The Input Text Elements did not have a functioning Font setting. Doh! Don't know how that got missed.

The very beginnings of the Treeview element are in there.

Hopefully nothing was broke. Any time I make changes to the core widget packing I get nervous!

** Had to turn off some of the Resizable windows features....Buttons and other elements were moving / expanding in forms that I didn't want the to expand. The change fucked up too many elements to leave on for now.

[MikeTheWatchGuy]

Two new Demo programs - CPU Desktop Widget, Spinner Compound Element

Added another Desktop Widget to the demos. This one shows the CPU utilization.

The spinner allows you to change how often it's refreshed

The Spinner Compound Element was done in response from a user wanting to see a different kind of spinner. This one has larger buttons and is laid out horizontally.

The point of this demo is that it's possible to put together multiple Elements into a higher level element. There aren't many of these I can think of at the moment, but given how many user questions are asked, something else is bound to be asked for.

[MikeTheWatchGuy]

Table Element, Complete rework of Popups, Death of MsgBox

You can blame the Popup changes on this issue:
#204

All of the Popups were rewritten to use a long list of customization parameters. The base Popup function remained more or less the same.

Decided while I was going all the Popup work that it's time to completely remove MsgBox. Sorry all you early adopters. You'll need to do a bulk rename and then you'll be fine.

Table Elements

Finally have something to show in the form of tables. The element name is Table. While the tkinter Treeview widget was used, many of the parameters were not exposed. If they were, the caller could really mess things up. Better to present a nice "Table-friendly'" interface than something specific to tkinter. After all, the plan is to expand PySimpleGUI to use other GUI frameworks.

A Demo program is in the works.

It's possible to add scrollbars to the Table element by simply placing it into a Column element.

There's still work to do and a good number of bugs, but I encourage you to give it a try.

If you do not put the Table Element inside of a Column, then you can still view and scroll the table, it just will not have scrollbars.

There is a problem currently with keyboard input when placed into a Column. The keyboard keys work fine when NOT inside of the Column but stop working when placed inside a Column Element.

This program will read a CSV file and display it in a window.

import csv
import PySimpleGUI as sg

filename = sg.PopupGetFile('filename to open', no_window=True, file_types=(("CSV Files","*.csv"),))
# --- populate table with file contents --- #
data = []
if filename is not None:
    with open(filename, "r") as infile:
        reader = csv.reader(infile)
        try:
            data = list(reader)  # read everything else into a list of rows
        except:
            sg.PopupError('Error reading file')
            exit(69)

sg.SetOptions(element_padding=(0, 0))

col_layout = [[sg.Table(values=data, headings=[x for x in range(len(data[0]))], max_col_width=8,
                        auto_size_columns=False, justification='right', size=(8, len(data)))]]

layout = [[sg.Column(col_layout, size=(1200,600), scrollable=True)],]

form = sg.FlexForm('Table', grab_anywhere=False)
b, v = form.LayoutAndRead(layout)

It's another bit of PySimpleGUI "challenge code"..... The challenge is to do the same operation in another GUI framework in less lines of code. I would enjoy seeing the tkinter code required to create the window that this 20 line PySimpleGUI program creates. Most of the code deals with reading the CSV file 👍

[MikeTheWatchGuy]

Linux Virtual Environment

I finally installed VirtualBox and am running Ubuntu Linux. I tried to install the Mint distro, but the display was scrambled when it booted.

I was surprised how close the Linux screen shots look to the Windows.

Even Pong worked the first time.

I don't believe that Python has been labelled the "go to language" for doing cross-platform GUI work. I guess I never stopped to think about it. I don't recall seeing this kind of thinking in posts or books I've read on Python. Perhaps it's time for that to change?

[MikeTheWatchGuy]

3.2.0

Released a new release to PyPI. Sorry about all these releases, but features continue to pour into the code. I'm finding even the folks that are actively using PySimpleGUI only run the pip installed version rather than the GitHub version. That means if I want runtime on the code, I'm only going to get any is to do a full release.

There were a number of changes that could f-up, so be on the lookout. The biggest addition to 3.2.0 was the Table Element (beta quality at the moment).

If you are running older programs then you may crash due to missing functions, MsgBox and several others. This is because I've moved 100% to Popup calls. It's not like I haven't been warning people so I don't expect complaints.

Some people are calling ReadNonBlocking prior to your Event Loop so that the form gets fully made. This call is needed if you want to perform actions on elements prior to calling Read. For example, if you want your form to be shown with some Elements set in the disabled state (using calls to Update), you will need to make an additional call after your Layout call.

Instead of calling ReadNonBlocking in these situations, you can call Finalize/PreRead/PrepareForUpdate. I have not been able to standardize on a name, so I'm providing multiple. I'm sure a winner will emerge. I've been using Finalize.

The call sequence becomes this:

form.Layout(layout)
form.Finalize()
element.Update(.....)
while True:
     b, v = form.Read()

You'll also find the Finalize call used in the scripts that use the Canvas Element.

See the Readme for more info on what's in the release. Note that the readme has not yet been updated with the Table Element and several other changes. There's only so much I can do.

[MikeTheWatchGuy]

One Line Progress Meters

PySimpleGUI has always had a one-line progress meter called EasyProgressMeter. However, that function has a limitation of only 1 meter being active at a time.

The new way to do Progress Meters is the function OneLineProgesssMeter.

All of the documentation and examples will reflect this new function.

Have to say it's nice to be able to run as many meters as desired without having to worry about more than 1 being on the screen at a time.

I intend to remove EasyProgressMeter within the next 5 or 6 releases to PyPI. I tried to insert a warning in the code, but too much code was shared to fit the message in.

I'm sorry about the change, but really would like to both add this function and rename the capability to something very descriptive. If there is enough revolt over removing EasyProgressMeter, I'll leave it in and simply drop it from all the documentation.

[MikeTheWatchGuy]

3.3.0

Yea, yea, it seems like only yesterday that version 3.2.0 was released. That's because it WAS only yesterday. I've been busy.

There are 2 changes I wanted out quickly....

1. The ability to turn off displaying row numbers
2. The new OneLineProgressMeter function

The Progress Meter feature alone is a great use of PySimpleGUI. A number of users are using it only for this purpose in their programs.

[MikeTheWatchGuy]

Graphing

New demo program - graph ping using canvas.
I'm thinking about creating a Graph Element, something that makes it super easy to users tog create graphs, both line and x,y plot. The demo should how to take a canvas element and graph ping times.

There is another ping-graph demo using Matplotlib. This graph only uses tkinter.

Finally, because the pings take a long time, I moved the ping calls outside of the GUI event loop. Calling ping inside event loop was causing the GUI to respond sluggishly. This is because the ping was taking 1 second which means the gui wasn't being refreshed / wasn't responsive during the second. Now the GUI sleeps for 200 ms while the ping is done by a thread.

This is yet another toe in the water with threading. The problems I saw in the past are no longer there, it would appear.

I also checked in the ping.py file that you need for this demo. It's a pure python implementation of ping and works pretty well, even if slow.

[MikeTheWatchGuy]

Progress Meters

Thanks to @JorjMcKie I've learned more about the performance of the EasyProgressMeter and thus probably the OneLineProgressMeter. The more arguments to display the longer it takes.

Was going to document in the Cookbook / Readme that if you have performance concerns, you can call the progress meter less frequently. You don't have to update it 1 count at a time. It could be like this:

for i in range(10000):
    if i % 5 == 0: sg.OneLineProgressMeter('My 1-line progress meter', i+1, 10000, 'single')

This meter is only called every 5 times through the loop. It finished quite a bit quicker than the test updating the meter every single time.

[MikeTheWatchGuy]

PySimpleGUI programs as an EXE file!

The biggest thing to hit PySimpleGUI since Colors.... the ability to run programs written for PySimpleGUI as an exe file. ALL credit goes to @JorjMcKie for this.

There is no need to distribute Python with your programs. It's all included in the exe and folder of supporting files.

From what I understand of nuitka, this code is compiled C++ code, not python code. The performance is thus potentially better! It's the best of both worlds.

Working to get the process documented. It's tricky and required a special script. Stay tuned....

[MikeTheWatchGuy]

Graph Element

This one is pretty exciting as it does something new on the screen. The Graph Element allows you to easily create a canvas and draw on it using your own coordinate system. You don't need to do conversions from your graph coordinates to the tkinter canvas graph coordinates.

The Demo program for it is a good example. It displays a pint graph. The graph we're creating is a line graph what we would like to to from 0,0 in the bottom left to 100, 500 in the upper right. This will give us 100 data points along the x axis and up to 500 ms on the y axis.

After creating the Graph Element, we can do 3 operations on it:

1. Draw Line
2. Draw Point
   3 Erase

The draw line draws a line from 1 point to another. The points are specified using your graph coordinates, not the tkinter canvas coordinates.

I know I have a LOT of documentation to do.

In the meantime, try using Control+P if you're using PyCharm. Press Control+P while you are typing in the parameters and you'll see a popup showing you what the legal parameters are. This feature is almost necessary when using PySimpleGUI because functions have SO many optional parameters.

I hope to see some cool creations using the capability. I'm starting to see more and more projects pop up on GitHub that use PySimpleGUI! Keep those examples coming! And keep the requests for new features coming too. They have made this such a better package because of your help.

Sample code:

This is your layout:

    layout = [  [sg.T('Ping times to Google.com', font='Any 18')],
               [sg.Graph((300,300), (0,0), (100,500),background_color='white', key='graph')],
               [sg.Quit()]]

    form = sg.FlexForm('Canvas test', grab_anywhere=True)
    form.Layout(layout)

To draw a line, call DrawLine:

form.FindElement('graph').DrawLine(from_point, to_point)

[MikeTheWatchGuy]

Movable Graph Element

Made the Graph Element "movable". This means the graph can be shifted when it reaches the "End".

Here's a 1,000 data-point ping graph or 16 minutes woth of pining

[PySimpleGUI]

Website Updates

The Dashboard problem was fixed yesterday.

Today we're having login issues. The site has been running very smoothly for the past month. We're working on the problem. I'm sorry for the inconvenience.

[PySimpleGUI]

License Changes Coming...

I'm not supposed to be announcing anything... but... I'm not so great at following instructions sometimes....

We're working hard on getting the changes made to the license. I'm quite sure everyone will like the change. There are a lot of places that need changing, there are lawyers that have to review documents, there are many more moving parts than before. So, turning on a dime, like I've been able to do in the past, is not as easy.

The Summary....

The word "Subscription" is going away... it's being replaced by the word "Perpetual"

That's all I can say right now, but hopefully that's enough to give a good idea of what we're doing....

[PySimpleGUI]

The New License is Here!

The "Big News" graphic above you may notice has changed slightly, on both the GitHub and in the Documentation.

I think the most concise explanation of the change can be found in the first FAQ item:
https://docs.pysimplegui.com/en/latest/FAQ/#is-pysimplegui-a-subscription-product

Here's what you'll find in the FAQ now:

---

Is PySimpleGUI a subscription product?

No. It's true that PySimpleGUI was a subscription product when it soft launched in 2024. Based on helpful feedback from our users, PySimpleSoft has moved PySimpleGUI away from the recurring annual subscription model. Instead, PySimpleGUI is now a traditionally licensed software product. Commercial Developers pay $99 for a perpetual license to the current version of PySimpleGUI. The perpetual license includes one year of free upgrades and priority support.

Hobbyist Developers continue to use PySimpleGUI at no cost but must refresh their Hobbyist Developer License annually.

---

More Info Coming

I'll go into more detail in the documentation , but this the above paragraph sums up the situation.

So that everyone is informed for this change, we'll be sending out an email to all current key holders.

Working to Keep the Hobbyist Version at No-Cost

A brief word about Hobbyist licenses. My goal is for PySimpleGUI to continue to grow, evolve, be supported, improved, and have a sustainable future. Some Commercial Users are abusing the Hobbyist License and claiming to be eligible for a no-cost license, when they most certainly do not.

If this continues, at some point we will be forced to stop offering a no-cost version. It's a decision driven 100% by the commercial users of PySimpleGUI. I want to continue to offer a no-cost path. It's my hope that our commercial users will make that possible.

[PySimpleGUI]

New Window Feature in 5.0.4.4

One of the features of PySimpleGUI that isn't well-known is the Timer API calls. They help create timer events that are more accurate than using a timeout on the window.read call. The parameter added isrepeating_timer_ms and indicates that a timer will run and create timer events at the interval indicated in milliseconds.

Here's an example of a flashing "LED" using a Text Element:

import PySimpleGUI as sg

layout = [  [sg.Text('Status')],
            [sg.Text(sg.SYMBOL_CIRCLE_OUTLINE, key='-OUT-', justification='c', text_color='red', font='_ 30', metadata=False)],
            [sg.Button('Exit')]  ]

window = sg.Window('Timer Parameter', layout, element_justification='c', font='_ 15', repeating_timer_ms=500)

t_elem = window['-OUT-']        # type: sg.Test

while True:
    event, values = window.read()
    if event == sg.WIN_CLOSED or event == 'Exit':
        break

    t_elem.update(sg.SYMBOL_CIRCLE if t_elem.metadata else sg.SYMBOL_CIRCLE_OUTLINE)

    t_elem.metadata = not t_elem.metadata

window.close()

The window it creates looks like this:

To get this release before it gets posted to PyPI, use the PySimpleGUI Home Window to upgrade to the latest Maint Release.

[PySimpleGUI]

5.0.4.20 - New pip commands added to the Exec APIs

As PySimpleGUI continues to be built-out as an application development SDK/API/Ecosystem, some capabilities were needed that turned out to be trickier than expected. Getting the version of a package that's installed on any version of Python you have installed on your system is not trivial and can take "long time" potentially, so I created an option to run the operation as a thread. It adds complexity, but it's complexity you can skip if you don't mind the small performance hit.

A new demo program was added to show how to use this new call to get the installed version.

https://github.com/PySimpleGUI/PySimpleGUI/blob/master/DemoPrograms/Demo_Pip_Installs.py

These calls are being used heavily by the build, release, and test tools for PySimpleGUI 5, so it made sense to release these capabilities to PySimpleGUI users to aid in installing and managing their environment.

Here's the output of the demo program:

I have a much more sophisticated utility that bulk installs every PySimpleGUI release on every version of PySimpleGUI t o ensure it runs properly.

[PySimpleGUI]

psghelp and Built-in SDK Reference Updated

Maybe folks have forgotten or newcomers never knew it existed....

On Windows, Winkey+S or Winkey + R and then type psghelp

Will open this window:

You can also get to it via the Home Window:

In a Maint Release today (5.0.4.22), I fixed all of the links that are shown at the bottom of the window. These links will open the SDK reference in the main documentation for that element/item.

[PySimpleGUI]

A New PySimpleGUI Book....

I received an early copy of this book and had it translated to English so I could read it. I liked it!

This morning, I saw Twitter is lit up with posts about it.

https://x.com/search?q=PySimpleGUI&src=recent_search_click&f=live

https://techbookfest.org/product/7uwuksXyd9WVR3PbH3sws7?productVariantID=vCA4cBwW7U09nSUhtrABdQ&utm_campaign=share&utm_medium=social&utm_source=twitter

Python Desktop App Creation Recipe Using PySimpleGUI
Skill-up study group for non-programmers

電子版
￥1000

Electronic + paper
¥1000 (free shipping)
Venue (electronic + paper)
￥1000
The electronic + paper set will be shipped together after June 28th after the event ends.

Python is a popular programming language. It can be used to create various automation and efficiency programs that make our work easier. There are many books and video materials for beginners, so even non-programmers can create business automation tools. In this way, it would be cool if the tools you create with Python could be operated and displayed with a GUI as a "desktop app" rather than as drab text. It would be easier for others to use it, not just yourself. That's where the library "PySimpleGUI" comes in. As the name suggests, it is a Python library that allows you to create GUIs with simple code, and you can create beautiful GUIs with short codes. The default settings look good, so you don't have to worry about the details of the design. This book is intended to help people who are creating desktop apps for the first time to do the following with a GUI. ・Get a rough idea of ​​what kind of GUIs can be created ・Understand how to write code to create a GUI and apply it to your own tools Let's create a cool Python desktop app using PySimpleGUI!
First appearance event: Gishohaku 10
Number of pages: 84

[PySimpleGUI]

Graph Element Demo Program - Reworked....

I was putting together a new demo program to demonstrate an exciting new layout technique using the Walrus Operator.... I took a look at Demo_Graph_Elem.py as a starting point and realized that it's based on ping code that is no longer part of the project, so I rewrote it to use ping3 or if that module is not installed, it will use random data.

The screen capture slows down the graph speed, but still shows the basic operation....

new.graph.elem.demo.mp4

[PySimpleGUI]

Release 5.0.5 - Released to PyPI

The 5.0.5 release was posted to GitHub this morning. It's been a couple of months since the last release and the bug fixes and new features have been piling up.

You will find the release notes here in the documentation:
https://docs.pysimplegui.com/en/latest/documentation/versions/psg5/#505-2-jun-2024

I'm copying them here for your convenience.

5.0.5 2-Jun-2024

• Fixed open GitHub issue window so that the checklist matches the newest on GitHub
• Fix for ButtonMenu not clearing the value dictionary entry after the event is returned. Used to work this way but broke along the way.
• Added set_hscroll_position for elements
• NEW FEATURE added - parameter repeating_timer_ms added to the Window object. Causes a repeating timer to be started.
• Uncommented line of code that imports askcolor from tkinter. Not sure why it was commented out
• Fix for bug that was showing trial expired in Home Window. Added new function dict_to_string to format dictionaries nicely
• Changed function dict_to_string to use the pprint.pformat function rather the reinvent the wheel this time. At least my version did right justify keys in a field the width of the max key length. :-)
• New option in global settings to control if formatted dictionary is printed when the automatic "print event values" feature is enabled
• Changed how Input.update select parm works:
  • If set to True, then the input is selected (highlighted)
  • The new addition is that if False, it clears the selection
• Added arrow and arrow_type to Graph.draw_line method
• Made aliases for HorizontalSeparator using word "Line" (HorizontalLine, HLine, Line)
• Updated the checklist in the builtin GitHub Issue logger to use the newest checklist. Was using an old one.
• Changed docstring for Table element and others that have "Select Mode" parameter to str
• Added right_click_menu paramter to Combo element
• Added window.right_click_menu_element. Will either be None or the element that was right clicked if right click menu used
• Fix in def dict_to_string. The pformat call didn't add the sort_dict parm until Python 3.8 so need to check python ver
• Made priority support code field in markdown for GitHub issue be the same level as the manual form on GitHub
• Added new function execute_pip_get_local_package_version so that local version of pip installed package can be easily obtained
• Changed execute_command_subprocess so that the interpreter can have spaces for things like parameters (i.e. py -3.11)
• Changed the function execute_pip_get_local_package_version to use the tempfile package so that there can be multiple requests outstanding at a time
• Fixed all links to the online documenation in the built-in SDK Call Reference Window (You know about this window, right?)
  • Type psghelp from the command line.
  • Or from the Home Window, click the help tab and the button "SDK Reference Window"

[PySimpleGUI]

Udemy Discount Coupon

I've posted another Udemy coupon that brings the price down to the cost it was last year. You'll find it in the GitHub issue marked as having the coupons. There's also a graphic on the front page of the documentation that automatically applies the coupon. Click the graphic and it'll take you to the course and apply the coupon code.

https://Docs.PySimpleGUI.com

[PySimpleGUI]

The License Evolution

I've really enjoyed the positive spirit of our users and the project overall. A quick word on the license change and it being a surprise to some people.

While these words are deleted from the forks of PySimpleGUI being promoted as a new home for some, they have been in the readme on GitHub, in the documentation, and on PyPI for 4 years. This change, away from an open source license was not only in all readme's, but you'll find in these over 1,200 announcements where I mention this change would eventually be taking place if the project is not able to be sustainable, numerous times.

My goal is to have this project continue on and to keep building the vision for PySimpleGUI. It's not possible to do without an income and ability to pay the costs. That's a simple fact.

I'll keep trying to do the best job I can... I'm far from perfect.

I'm not sure how much clearer I could have been about the situation.

PySimpleGUI has an open-source license and it would be great if it could remain that way. If you or your company (especially if you're using PySimpleGUI in a company) are benefiting financially by using PySimpleGUI, you have the capability of extending the life of the project for you and other users.

As always, I really appreciate how our users are a vocally grateful group of people. It's make the experience a dream come true.

[PySimpleGUI]

New Demo Program - Walrus Operator in Layouts

I've added a new Demo Program that demonstrates how to use a Walrus Operator inside a PySimpleGUI layout. It's handy for elements that you call a lot of methods for. The Walrus Operator saves having to look up the element using the key.

Here is the code from the Demo Program - Demo_Layouts_Using_Walrus_Operator.py

import PySimpleGUI as sg
import random

"""
    Using Python's Walrus Operator in Layouts

    Some elements you call many different member functions for. Rather than looking up the element by the key and storing
        into a variable, you can use the walrus operator to store the element, right from the layout itself.
"""
layout = [[sg.Text('Using Walrus Operator In Layouts', font='_ 16')],
          [graph_elem := sg.Graph((500, 500), (0, 0), (100, 100), key='-GRAPH-')],
          [sg.Button('Draw'), sg.Button('Exit')]]

window = sg.Window('Walrus Operator In Layouts', layout, auto_save_location=True)

# graph_elem = window['-GRAPH-']      # This is the way elements are normally looked up and stored in a variable

while True:
    event, values = window.read()
    if event == sg.WIN_CLOSED or event == 'Exit':
        break
    if event == 'Draw':
        emoji = random.choice(sg.EMOJI_BASE64_HAPPY_LIST)
        location = random.randint(0, 100), random.randint(0, 100)
        graph_elem.draw_image(data=emoji, location=location)

window.close()

Enjoy!

[PySimpleGUI]

Taking a Little Break

I'm taking some time away from PSG technical work so my responses will be slower for a bit.

[PySimpleGUI]

PayPal Now Accepted!

We have added PayPal as a payment option for purchasing licenses. Hopefully that will make purchasing your license easier for everyone.

[PySimpleGUI]

5.0.6 Released to PyPI

Just uploaded release 5.0.6 to PyPI.

There were problems using PyInstaller and cx_freeze reported so I really wanted to get the fixes posted to PyPI quickly for those.

Release notes (and are in the docs):

• Made the Window member variable right_click_menu_element a property so that it'll show up in the call reference documentation
• Changed several docstrings that had type "enum" for parms like SELECT_MODE. They were "enum" and were changed to "str"
  The reason for the change - PyCharm is highlighting those parms with a warning
• Change to handle cx_freeze UnicodeDecodeError
• A better change to handle cx_freeze UnicodeDecodeError. As a test, will print "Frozen app detected" if successfully detected
• Removed the test print "Frozen app detected" if cx_freeze detected
• Fix for PyInstaller module not found error
• Changed how hashlib is imported. Improved a couple of error messages.

Have a great weekend!

[PySimpleGUI]

5.0.6.1 Maint Release - New Table Element Cell Editing Feature

In 5.0.6.1 I've added two new features to the Table element.

1. A new parameter enable_cell_editing that if true enables you to double-click or use return key to edit a cell's value
2. A new property Table.values which returns the current value of the entire table

To end the edit, press the return key or click anywhere outside the cell.

The Demo Program Demo_Table_Element_Header_or_Cell_Clicks.py was modified to demonstrate this parameter being enabled. Of course, you'll need to upgrade to the maintenance release 5.0.6.1 for this feature to work with the demo until it's releases to PyPI.

User's have needed to use PySimpleGUIQt in the past to get this kind of functionality. Now you can edit your table, in place, without moving to the Qt port.

Enjoy!

Here's what it looks like in action...

Editing.a.Table.mp4

[PySimpleGUI]

Sunset of PySimpleGUI 4

In February 2024, PySimpleSoft announced that PySimpleGUI 4 support would expire on Sunday, June 30 as part of a commercial model for PySimpleGUI 5. This announcement has been displayed continuously on multiple platforms and the sunset is now in effect.

Unlike other open-source software projects, PySimpleGUI code was developed and written entirely by its in-house team, with occasional help from paid contractors. PySimpleGUI did not accept nor utilize contributions from other developers. Since its launch in 2018, PySimpleGUI’s model has been to provide free licensing use until financial constraints mandated a commercial license model. That time has arrived.

The commercial license model is critical for PySimpleGUI to continue to operate and provide enhanced support for users. We are proud to help millions of users create programs more efficiently, elegantly and quickly. We look forward to continuing to provide innovative features, security and documentation.

[PySimpleGUI]

Support Provided for PySimpleGUI 5

Now that PySimpleGUI 4 has sunset, it will not be supported any longer here on the PySimpleGUI GitHub. The automated IssueBot that we use to verify the issues being submitted will soon begin to reject issues opened for versions of PySimpleGUI that are version 4.

You do not need a Commercial License in order to open an Issue for PySimpleGUI 5. Hobbyists and Commercial users are both supported. Commercial License holders are provided a priority support code, enabling their issues to receive a higher priority in handling.

Thank you for the encouraging emails ! They've certainly been apprecciated.

[PySimpleGUI]

New "Smart Icon" Demo Program

I've posted a new demo program showing how to make a "Smart Desktop Icon"
https://github.com/PySimpleGUI/PySimpleGUI/blob/master/DemoPrograms/Demo_Smart_Desktop_Icon.pyw

I've used this code a number of times in the past, but never really released it stripped down like this demo. It looks like a desktop icon, but in reality, it's a small PySimpleGUI window. This enables you to do all kinds of fun things like change the icon at runtime... maybe you've got an email client and want the icon to indicate new mail has arrived.

The Demo current handles double-click events by launching a program, has a right click menu and randomly changes the icon every 5 minutes. This way you've got a design pattern to modify.

Enjoy!

[PySimpleGUI]

Away Until 5-Aug-2024

I (uhm, of course this is mike), am going to be away until Monday August 5th, will not be checking messages nor issues, but others are still monitoring and replying to licensing questions via email, etc.

[PySimpleGUI]

New Demo Browser Version 5.3.0 Released

There was a bug in the import checking / auto installing code. While in there, I added the ability to run any program that you provide a path to... Press F3 to be taken to the field labeled Path (F3): where you can paste the path and then press the Run button to run your code.

[PySimpleGUI]

Release 5.0.7 20-Oct-2024 posted to PyPI

This one has some awesome new features like editing table cells. It also has a critical fix for users of Python 3.13.0.

The documentation has been updated to include the release notes and an updated Call Reference that has the new parameters and functions for the new features.

• New Table feature Editing individual table values using double-click/return key
• New Table feature values property returns the table's current values
• New Table feature Pressing Escape Key during cell edit will abort the edit and restore value
• New Vertical Separator alias added to match the Horizontal ones added earlier. VLine, VerticalLine
• New Table feature If user double-clicks and modifies a cell in a table, then an event with a tuple is generated that is similar to the Clicked tuple. The constant TABLE_EDITED_INDICATOR will be part of tuple
• Table Element Finishing up the cell editing by adding more parms to the Table element for edit colors and select color
  • cell_edit_colors controls colors of cells during editing
  • cell_edit_select_colors controls colors of the sections during editing
• Menu Element Added generating an event when a top level menu item has no submenu. NOTE this is not a normal Windows behavior.
• dict_to_string changed so width used with pformat is defined by constant DEFAULT_DICT_TO_STRING_WIDTH which is 80.
• Made retroactive by changing the key in the global settings. Old default was 1.
• This function is used when print_event_values=True when making the window.
• Menu Element Added support for using a key with a top-level menu item since these can now be events
• Fix for incorrectly calculating row when checking for type when Table editing
• Test fix for Y-scrolling of columns that have other scrollable elements in them
• More changes to the scrollable Column to try and fix the Y-scrolling issue
• Applied above changes to the X-scrolling of columns (both using mouse wheel and scrollbars)
• Fix for Table cell editing. Checked to make sure not already editing when get an edit request
• Fix for mouse scroll wheel crash when leaving a scrollable area and returning
• Fixed maintanence spelling error (ugh... sorry everyone...)
• Upgraded version of Python 3.13.0 used to build PySimpleGUI

ENJOY!

[PySimpleGUI]

Happy 2025!

I hope everyone had a wonderful and enjoy holiday season!

There are a couple of changes in the latest maintenance releases that will be of interest to Mac users that install via Homebrew and to those on the bleeding edge of Python releases.

Tk 9.0

For the Mac, support for Tk 9.0 was added. It's been tested on a couple of Macs and has been working great. User @mikehgithub
was extremely helpful in testing both Mac and Linux for us (THANK YOU MIKE!).

It's been regression tested against all the versions of Python from 3.6 through 3.14 on windows and the many versions of tkinter 8.6.* that they use.

The addition of Tk 9.0 was unexpected as it's not been yet added to the official Python.org roadmap by the PSF that I'm aware of. The newest version posted is 4.13 Alpha and it has 8.6.15.

Python 3.14 Alpha support

While very few users are running 3.14, support for it was added to the release 5.0.7.3. You will need to manually install the maintenance release using the command:

python3 -m pip install --upgrade https://PySimpleGUI.net/wheels/PySimpleGUI-5.0.7.3-py3-none-any.whl

If you want to use PySimpleGUI with 3.14 you'll need to install that specific release until it's posted to PyPI (soon).

---

PyPI Release Soon

The support for Tk 9.0 is the more pressing issue since it's causing crashes when PySimpleGUI is used with the default Homebrew. IMO, the Homebrew team jumped a little too quickly on this version of tkinter as it's not been release by the PSF meaning it's not been fully tested with cpython.

[PySimpleGUI]

Release of 5.0.8 coming to PyPI soon (maint release 5.0.7.8 is the candidate at the moment)

The regression testing and testing some new features is almost completed. Next step is to release to PyPI.

In this release you'll find

• Support for Python 3.14 Alpha
• Support for Tk 9.0
• New command line options to enable installing specific versions of PySimpleGUI

3.14 support (Pi for Py?)

Here you can see 3.14 running just fine!

Tk 9.0

Tk 9.0 now works with PySimpleGUI.. .hopefully when the PSF releases this users will already have the new code running.

New Command Line Options

Some of the built-in PySimpleGUI capabilities rely on being able to output to windows, but if there's a serious problem, such as the TK 9.0 issue, then you won't be able to use these tools to upgrade to a maint release that has fix. In the new release, several new command line options were added.

If you can use the GUI interface, then you can use the standard psgupdrade command. It now has an optional additional parameter enabling you to specify a build number. For example to get maint release 5.0.7.7:
psgupgrade 5.0.7.7

If you cannot use a GUI (things are badly broken) then maybe the new "nogui" feature will help:
python -m PySimpleGUI upgradenogui

Running this command you will see a list of available maint releases printed on the console. If you then add the release you want to install onto the end of the command it will install it. Again using 5.0.7.7 you would run:
python -m PySimpleGUI upgradenogui 5.0.7.7

This capability removes the need for you to pip install using an http address of the wheel

Unfortunately, the new options added for installing via the command line won't help the Mac folks needing to upgrade, but since this release is going to PyPI, that won't be a problem as the command line is used to install from PyPI. This feature was added so that PySimpleGUI can be used to get maint releases with a specific version number.

You can also get the versions by running:
python -m PySimpleGUI version

You'll see this kind of detail printed out so that you can use it if you need to submit a bug that's stopping you from getting to the versions using the normal psgver/psgmain methods.

Python Interpeter: C:\Python\python3.6\python.exe
Python version: 3.6.8
Platform: Windows
Platform version: ('10', '10.0.19041', 'SP0', 'Multiprocessor Free')
Port: PySimpleGUI
tkinter version: 8.6.6
PySimpleGUI version: 5.0.7.8
PySimpleGUI filename: C:\Python\python3.6\lib\site-packages\PySimpleGUI\PySimpleGUI.py

[PySimpleGUI]

Command line options in 5.0.7.12 (This or a version higher will eventually be in 5.0.8 on PyPI)

A number of options have been added to the command line and to the psgupgrade command.

Invoking PySimpleGUI from command line

You can already open PySimpleGUI's Home Window by typing python -m PySimpleGUI. This is how you can also access the old and newer command line options.

Summary of commands

python -m PySmpleGUI upgrade
Open GUI upgrade utility (same as psgupgrade)

python -m PySmpleGUI upgrade x.x.x.x
Upgrade to a specific maint release version number

python -m PySmpleGUI upgradenogui
Show list of available maint releases on the console

python -m PySmpleGUI upgradenogui x.x.x.x
Upgrade to a specific maint release on the console

python -m version
Display version numbers of Python, tkinter, PSG, etc on the console. It's the same info as the psgver command, but shown on the console.

python -m help
Display the SDK help window and list of command line options

The New Features

There are two primary features that have been added, both dealing with upgrading your PySimpleGUI installation with a maintenance release. Two will help us when something breaks and you're unable to get any windows to show.

version

The version option displays the same data that's shown in a window when the psgver command is run.

upgradenogui

Enables you to upgrade to a specific version number. If none is provided, the list of available maintenance releases is printed so that you can choose one.

upgrade or upgrade x.x.x.x

Added ability to add an optional specific version number to upgrade to

psgupgrade x.x.x.x

You can add an optional specific version number if using the psgupgrade command line command.

Here's an example for the upgrade. Either of these commands:

psgupgrade 5.0.7.10
python -m PySimpleGUI upgrade 5.0.7.10

Will display this window so that you can upgrade to the version 5.0.7.10 that was requested.

[PySimpleGUI]

PyPI Release of 5.0.8

5.0.8 06-Jan-2025

• Added ability to indicate no emoji should be used in error popup. Needed so that recursive error calls aren't made from image element error
• Support for Tk 9.0. An early version of 9.0 was released on the Mac via Homebrew
• Support for Python 3.14 Alpha
• Swapped Window method in start_thread as the main definition and perform_long_operation as the alias for easier understanding
• New command line options:
  • version - prints versions numbers on the command line without creating any windows. Run python -m PySimpleGUI version to get the version info output to the console
  • upgradenogui - prints the maint releases available without making nay windows
  • upgradenogui x.x.x.x - upgrades to maint release specified by x.x.x.x without making nay windows
  • Added new command line function to the main when building a release... hopefully this will work...
• Added specific version number optional parm to the psgupgrade command to make specific maint release installs easier
• Added printing of command line options to the "help" command line option. Will print the options and then open the SDK Help Window

[PySimpleGUI]

Renewals of PySimpleGUI 5 Licenses

PySimpleGUI 5, when launched, was subscription based. We decided to move to a perpetual license a few months later after getting feedback from users. The current license is perpetual. Priority support is good for 1 year if you're a commercial user. All Hobbyist licenses expire after one year, so you will need to renew your license each year.

If you would like to renew your license:

• Hobbyist License - Log into your account on PySimpleGUI.com and delete the account. Create a new one and you'll be given a new key
• Commercial License - Your license doesn't expire, but your priority support does after 1 year. If you would like to renew, please email license@PySimpleGUI.com

[PySimpleGUI]

Two important announcements....

Please see the readme for a couple of important project updates

[PySimpleGUI]

Two Important updates about PySimpleGUI

1. New Package Location

We were recently informed by PyPI that PySimpleGUI does not meet updated PyPI Terms of Service, that it needs to be removed, and hosted on a private server. As a result, you’ll need to add a parameter to your pip install commands in order to access the PySimpleGUI private PyPI server.
The parameter to add is:

-i https://PySimpleGUI.net/install

The basic install/upgrade command was:

python -m pip install –-upgrade PySimpleGUI

or for Linux/Mac

python3 -m pip install –-upgrade PySimpleGUI

The new command with the new parameter is:

python -m pip install --upgrade -i https://PySimpleGUI.net/install PySimpleGUI

2. PySimpleGUI Shutdown

We gave it our best shot…. After 7 years of attempting to make the PySimpleGUI project sustainable, we are stopping the PySimpleGUI project.

If you've followed the project over the years, you'll have read about the difficulties that all open-source projects face in generating enough income to pay for the project, seen the requests for sponsorships, and attempts to generate income via a Udemy course. There was not enough income to cover the costs of running a business and, of course, wasn’t able to generate any income for our small team. This isn’t a sustainable situation.

One Year Update PySimpleGUI 5

It's been a little over a year since the release of PySimpleGUI 5. Of the 100,000’s of Version 5 users, 10,000's of which were large corporate users, only 600 people paid the $99 for a commercial license.

End of PySimpleGUI Project

The revenue generated was not enough to cover the basic costs, so we've made the difficult decision to end the PySimpleGUI project.

Support for Commercial Users

Unlike traditional software companies, where stopping business means support ends immediately, we thought it would be classier to go the extra mile by continuing to provide support to Commercial License users this year as a way of saying "thank you" for your help in trying to give the project a viable future. Please provide your Priority Support code or your submission will be automatically blocked. We'll do the best we can to help with the limited resources we've got.

Your license doesn’t expire so you’ll be able to continue to run your applications at the end of the year we’re providing maintenance and beyond. We’ll be distributing an offline version of the documentation so that you’ll have it for the future.

Hobbyists

Hobbyists can continue to use PySimpleGUI 5 until their keys expire. After that you'll need to switch to version 4, which you'll find 1,000s of copies on GitHub with at least 1 being community supported.

If you wish to use PySimpleGUI without the key expiring or want support, then you can buy a Commercial License which is good perpetually.

Websites Availability

The PySimpleGUI registration and documentation websites will continue to operate for a couple of months to give commercial customers an opportunity to create distribution keys. No new Hobbyist keys will be available.

Thank you to everyone

PySimpleGUI has been an experience of a lifetime, and we’ve
enjoyed watching & helping people create incredible applications.

Business Partnership Inquires

If you're a business with a serious partnership that you wish to discuss, email mike@PySimpleGUI.com.

[PySimpleGUI]

Commercial License may falsely report expiration... Upgrade to 5.0.10 to avoid this error

There is a bug in PySimpleGUI versions that was reporting the license had expired for Commercial Licenses. This is clearly incorrect as Commercial Licenses do not expire. The bug was fixed in 5.0.10 and released on 2-Apr-2025. Please upgrade to avoid problems with your Developer Key. Distribution keys shouldn't be impacted by the bug.