Removed Macs being forced to system default. Checked in the latest readme components
This commit is contained in:
PySimpleGUI
parent
9cc43153b5
commit
0d7473eedb
|
|
@ -1,6 +1,6 @@
|
|||
#!/usr/bin/python3
|
||||
|
||||
version = __version__ = "4.13.1.2 Unreleased - Element.set_cursor, NEW theme(), Combo.update allows any value, table & tree header font defaults to window font, default theme now Dark Blue 3"
|
||||
version = __version__ = "4.13.1.3 Unreleased - Element.set_cursor, NEW theme(), Combo.update allows any value, table & tree header font defaults to window font, default theme now Dark Blue 3, Macs no longer default to colorless windows and buttons"
|
||||
|
||||
port = 'PySimpleGUI'
|
||||
|
||||
|
|
@ -215,13 +215,10 @@ NICE_BUTTON_COLORS = ((GREENS[3], TANS[0]),
|
|||
(YELLOWS[0], GREENS[3]),
|
||||
(YELLOWS[0], BLUES[2]))
|
||||
|
||||
COLOR_SYSTEM_DEFAULT = '1234567890' # Colors should never be this long
|
||||
if sys.platform == 'darwin':
|
||||
DEFAULT_BUTTON_COLOR = COLOR_SYSTEM_DEFAULT # Foreground, Background (None, None) == System Default
|
||||
OFFICIAL_PYSIMPLEGUI_BUTTON_COLOR = COLOR_SYSTEM_DEFAULT # Colors should never be this long
|
||||
else:
|
||||
COLOR_SYSTEM_DEFAULT = '1234567890' # A Magic Number kind of signal to PySimpleGUI that the color should not be set at all
|
||||
DEFAULT_BUTTON_COLOR = ('white', BLUES[0]) # Foreground, Background (None, None) == System Default
|
||||
OFFICIAL_PYSIMPLEGUI_BUTTON_COLOR = ('white', BLUES[0]) # Colors should never be this long
|
||||
OFFICIAL_PYSIMPLEGUI_BUTTON_COLOR = ('white', BLUES[0])
|
||||
|
||||
CURRENT_LOOK_AND_FEEL = 'DarkBlue3'
|
||||
|
||||
DEFAULT_ERROR_BUTTON_COLOR = ("#FFFFFF", "#FF0000")
|
||||
|
|
@ -12812,7 +12809,6 @@ def main():
|
|||
# ------------------------ PEP8-ify The SDK ------------------------#
|
||||
|
||||
change_look_and_feel = ChangeLookAndFeel
|
||||
set_theme = ChangeLookAndFeel
|
||||
convert_args_to_single_string = ConvertArgsToSingleString
|
||||
convert_flex_to_tk = ConvertFlexToTK
|
||||
easy_print = EasyPrint
|
||||
|
|
@ -12848,7 +12844,6 @@ popup_timed = PopupTimed
|
|||
popup_yes_no = PopupYesNo
|
||||
sgprint = Print
|
||||
sgprint_close = PrintClose
|
||||
quit = Quit
|
||||
rgb = RGB
|
||||
set_global_icon = SetGlobalIcon
|
||||
set_options = SetOptions
|
||||
|
|
|
|||
1664
docs/index.md
1664
docs/index.md
File diff suppressed because it is too large
Load Diff
|
|
@ -28,16 +28,21 @@ HOW DO I INSERT IMAGES ???
|
|||
|
||||
|
||||
[](http://pepy.tech/project/pysimplegui) tkinter
|
||||
|
||||
[](https://pepy.tech/project/pysimplegui27) tkinter 2.7 (WARNING - DISAPPEARING Entirely on 12/31/2019!!!)
|
||||
|
||||
[](https://pepy.tech/project/pysimpleguiqt) Qt
|
||||
|
||||
[](https://pepy.tech/project/pysimpleguiWx) WxPython
|
||||
|
||||
[](https://pepy.tech/project/pysimpleguiWeb) Web (Remi)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -191,12 +196,18 @@ and returns the value input as well as the button clicked.
|
|||
[How to submit an Issue](https://github.com/PySimpleGUI/PySimpleGUI/issues/1646)
|
||||
|
||||
|
||||
The YouTube videos - If you like instructional videos, there are over 15 videos
|
||||
The YouTube videos - If you like instructional videos, there are over 15 videos made by PySimpleGUI project
|
||||
- [5 part series of basics](https://www.youtube.com/playlist?list=PLl8dD0doyrvHMoJGTdMtgLuHymaqJVjzt)
|
||||
- [10 part series of more detail](https://www.youtube.com/playlist?list=PLl8dD0doyrvGyXjORNvirTIZxKopJr8s0)
|
||||
- [The Naked Truth (An updaate on the technology)](https://youtu.be/BFTxBmihsUY)
|
||||
- There are numerous short videos also on that channel that demonstrate PySimpleGUI being used
|
||||
|
||||
YouTube Videos made by others. These have much higher production values than the above videos.
|
||||
|
||||
- A ***fantastic*** tutorial [PySimpleGUI Concepts - Video 1](https://youtu.be/cLcfLm_GgiM)
|
||||
- Build a calculator [Python Calculator with GUI | PySimpleGUI | Texas Instruments DataMath II](https://youtu.be/x5LSTDdffFk)
|
||||
- Notepad [Notepad in Python - PySimpleGUI](https://youtu.be/JQY641uynKo)
|
||||
- File Search Engine [File Search Engine | Project for Python Portfolio with GUI | PySimpleGUI](https://youtu.be/IWDC9vcBIFQ)
|
||||
|
||||
# About The PySimpleGUI Documentation System
|
||||
|
||||
|
|
@ -260,10 +271,10 @@ PySimpleGUI runs on Windows, Linux and Mac, just like tkinter, Qt, WxPython and
|
|||
### OS
|
||||
|
||||
* Windows 7, 8, 10
|
||||
* Linux on PC - Tested on **many** distributions
|
||||
* Linux on PC - Tested on several distributions
|
||||
* Linux on Raspbnerry Pi
|
||||
* Linux on Android - Can use either Termux or PyDroid3
|
||||
* Mac OS (Sorry don't know much about Macs other than Macs don't like tkinter)
|
||||
* Mac OS
|
||||
|
||||
|
||||
#### Python versions
|
||||
|
|
@ -439,6 +450,35 @@ PySimpleGUIWeb is first and foremost a **GUI**, a program's front-end. It is des
|
|||
|
||||
If more than 1 person connects at a time, then both users will see the exact same stuff and will be interacting with the program as if a single user was using it.
|
||||
|
||||
## Android Version
|
||||
|
||||
PySimpleGUI runs on Android devices with the help of either the PyDroid3 app or the Termux app. Both are capable of running tkinter programs which means both are capable of running PySimpleGUI.
|
||||
|
||||
To use with PyDroid3 you will need to add this import to the top of all of your PySimpleGUI program files:
|
||||
|
||||
```python
|
||||
import tkinter
|
||||
```
|
||||
|
||||
This evidently triggers PyDroid3 that the application is going to need to use the GUI.
|
||||
|
||||
You will also want to create your windows with the `location` parameter set to `(0,0)`.
|
||||
|
||||
Here's a quick demo that uses OpenCV2 to display your webcam in a window that runs on PyDroid3:
|
||||
|
||||
```python
|
||||
import tkinter
|
||||
import cv2, PySimpleGUI as sg
|
||||
USE_CAMERA = 0 # change to 1 for front facing camera
|
||||
window, cap = sg.Window('Demo Application - OpenCV Integration', [[sg.Image(filename='', key='image')], ], location=(0, 0), grab_anywhere=True), cv2.VideoCapture(USE_CAMERA)
|
||||
while window(timeout=20)[0] is not None:
|
||||
window['image'](data=cv2.imencode('.png', cap.read()[1])[1].tobytes())
|
||||
```
|
||||
|
||||
You will need to pip install opencv-python as well as PySimpleGUI to run this program.
|
||||
|
||||
Also, you must be using the Premium, yes paid, version of PyDroid3 in order to run OpenCV. The cost is CHEAP when compared to the rest of things in life. A movie ticket will cost you more. Which is more fun, seeing **your Python program** running on your phone and using your phone's camera, or some random movie currently playing? From experience, the Python choice is a winner. If you're cheap, well, then you won't get to use OpenCV. No, there is no secret commercial pact between the PySimpleGUI project and the PyDroid3 app team.
|
||||
|
||||
|
||||
## Source code compatibility
|
||||
|
||||
|
|
@ -493,13 +533,17 @@ Repl.it is not meant to serve up applications and web pages. Trying to use it t
|
|||
|
||||
It's surprising that Python GUI code is completely cross platform from Windows to Mac to Linux. No source code changes. This is true for both PySimpleGUI and PySimpleGUIQt.
|
||||
|
||||
However, **Macs** suck. They suck on tkinter in particular. The "Look and feel" calls are disabled for Macs. Colored buttons in particular are broken. And, you are unable to specify filetypes when using the FileBrowse button. None of this is PySimpleGUI code issues, of course, they're all in tkinter. Consider using Qt instead of tkinter on the Mac. Or, if using tkinter, create your own button images.
|
||||
Historicly, PySimpleGUI using tkinter have struggled on Macs. This was because of a problem setting button colors on the Mac. However, two events has turned this problem around entirely.
|
||||
|
||||
***Look through the open and closed issues if you're a Mac person with a problem. It's highly likely the problem has been at least seen previously and there may even be a fix or workaround***
|
||||
1. Use of ttk Buttons for Macs
|
||||
2. Ability for Mac users to install Python from python.org rather than the Homebrew version with button problems
|
||||
|
||||
*Switching to "Light Mode" is known to fix some of the problems.* They honestly are tkinter/Mac problems.
|
||||
It's been a long road for Mac users with many deciding to use PySimpleGUIQt so that multi-colored windows could be made. It's completely understandable to want to make attractive windows that utilitize colors.
|
||||
|
||||
PySimpleGUI now supports Macs, Linux, and Windows equally well. They all are able to use the "Themes" that automatically add color to your windows.
|
||||
|
||||
Be aware that Macs default to using ttk buttons. You can override this setting at the Window and Button levels. If you installed Python from python.org, then it's likely you can use the non-ttk buttons should you wish.
|
||||
|
||||
Make sure you're running tkinter 8.6 and up. However, as I'm learning 8.6 can mean almost anything as the minor release numbers are not provided (8.6.1, etc). Turns out 8.6 has been in development for YEARS. The 8.6 that comes with Python 3.7.4 doesn't support table colors for example even though it's version 8.6.
|
||||
|
||||
|
||||
# Support
|
||||
|
|
@ -744,6 +788,8 @@ Creating and reading the user's inputs for the window occupy the last 2 lines of
|
|||
```python
|
||||
import PySimpleGUI as sg
|
||||
|
||||
sg.change_look_and_feel('Dark Blue 3') # please make your creations colorful
|
||||
|
||||
layout = [ [sg.Text('Filename')],
|
||||
[sg.Input(), sg.FileBrowse()],
|
||||
[sg.OK(), sg.Cancel()]]
|
||||
|
|
@ -751,6 +797,7 @@ layout = [[sg.Text('Filename')],
|
|||
window = sg.Window('Get filename example', layout)
|
||||
|
||||
event, values = window.Read()
|
||||
window.close()
|
||||
```
|
||||
|
||||
|
||||
|
|
@ -850,8 +897,9 @@ Just because you can't match a pair of socks doesn't mean your windows have to a
|
|||
|
||||
In PySimpleGUI release 4.6 the number of themes was dramatically increased from a couple dozen to over 100. To use the color schemes shown in the window below, add a call to `change_look_and_feel('Theme Name)` to your code, passing in the name of thd desired color theme. To see this window and the list of available themes on your releeae of softrware, call the function `preview_all_look_and_feel_themes()`. This will create a window with the frames like those below. It will shows you exactly what's available in your version of PySimpleGUI.
|
||||
|
||||
|
||||
In release 4.9 another 32 Color Themes were added... here are the current choices
|
||||
|
||||
|
||||
|
||||
Make beautiful looking, alpha-blended (partially transparent) Rainmeter-style Desktop Widgets that run in the background.
|
||||
|
||||
|
|
@ -983,6 +1031,7 @@ Features of PySimpleGUI include:
|
|||
- Calendar chooser
|
||||
- Color chooser
|
||||
- Button Menu
|
||||
- TTK Buttons or "normal" TK Buttons
|
||||
- Checkboxes
|
||||
- Radio Buttons
|
||||
- Listbox
|
||||
|
|
@ -1097,7 +1146,7 @@ Beginners certainly can add more `if event == 'my button':` statements to the ev
|
|||
|
||||
The hope is that beginners that are interested in graphic design, and are taking a Python course, will have an easy way to express themselves, right from the start of their Python experience. Even if they're not the best programmers they will be able express themselves to show custom GUI layouts, colors and artwork with ease.
|
||||
|
||||
> Fill the GUI Gap
|
||||
> Fill the GUI Gap (Democratize GUIs)
|
||||
|
||||
There is a noticeable gap in the Python GUI solution. Fill that gap and who knows what will happen. At the moment, to make a tradiional GUI window using tkinter, Qt, WxPython and Remi, it takes much more than a week, or a month of Python education to use these GUI packages.
|
||||
|
||||
|
|
@ -1155,6 +1204,8 @@ More information about installing tkinter can be found here: https://www.techinf
|
|||
|
||||
### Installing for Python 2.7
|
||||
|
||||
**IMPORTANT** PySimpleGUI27 will disappear from the GitHub on Dec 31, 2019. PLEASE migrate to 3.6 at least. It's not painful for most people.
|
||||
|
||||
`pip install --upgrade PySimpleGUI27`
|
||||
or
|
||||
`pip2 install --upgrade PySimpleGUI27`
|
||||
|
|
@ -1165,7 +1216,6 @@ You may need to also install "future" for version 2.7
|
|||
or
|
||||
`pip2 install future`
|
||||
|
||||
Python 2.7 support is relatively new and the bugs are still being worked out. I'm unsure what may need to be done to install tkinter for Python 2.7. Will update this readme when more info is available
|
||||
|
||||
Like above, you may have to install either pip or tkinter. To do this on Python 2.7:
|
||||
|
||||
|
|
@ -1304,38 +1354,17 @@ Then use either "high level" API calls or build your own windows.
|
|||
|
||||
Yes, it's just that easy to have a window appear on the screen using Python. With PySimpleGUI, making a custom window appear isn't much more difficult. The goal is to get you running on your GUI within ***minutes***, not hours nor days.
|
||||
|
||||
***WARNING*** Do NOT use PySimpleGUI with Python 3.7.3 and 3.7.4. tkiter is having issues with that release. Things like Table colors stopped working entirely. None of us want to debug tkinter code. It's difficult enough debugging your code and PySimpleGUI code. A lot of time has already been spent debugging this one so no need for you to suffer too.
|
||||
|
||||
### Python 3.7
|
||||
|
||||
It puzzles me why a beginner would install 3.7. Or even a seasoned programmer. What specific feature of 3.7 are you using that is not in 3.6? If you are unable to answer this, then ***it's strongly suggested that you run 3.6***, an immensely solid release of Python with all those goodie inside like f-strings. If you must run 3.7, try 3.7.2 instead. It does work with PySimpleGUI with no known issues.
|
||||
If you must run 3.7, try 3.7.2. It does work with PySimpleGUI with no known issues.
|
||||
|
||||
***PySimpleGUI with Python 3.7.3 and 3.7.4+.*** tkinter is having issues with all the newer releases. Things like Table colors stopped working entirely. It's unclear if there's been a change that makes the tkinter API no longer working which means they are not backwards compatible. That would be a real shame. If so, more work needs to be done in PySimpleGUI
|
||||
|
||||
## Using - Python 2.7
|
||||
## Python 2.7
|
||||
|
||||
Those using Python 2.7 will import a different module name
|
||||
On December 31, 2019 the Python 2.7 version of PySimpleGUI will be **deleted** from the GitHub. Sorry but Legacy Python has no permanent home here. The security experts claim that supporting 2.7 is doing a diservice to the Python community. I understand why. There are some very narrow cases where 2.7 is required. If you have one, make a copy of PySimpleGUI27.py quickly before it disappears for good.
|
||||
|
||||
```python
|
||||
import PySimpleGUI27 as sg
|
||||
```
|
||||
|
||||
|
||||
|
||||
## Code to Automatically Import Correct Version
|
||||
|
||||
Many of the demo programs use this check to see which package to use:
|
||||
```python
|
||||
import sys
|
||||
if sys.version_info[0] >= 3:
|
||||
import PySimpleGUI as sg
|
||||
else:
|
||||
import PySimpleGUI27 as sg
|
||||
```
|
||||
|
||||
|
||||
This will automatically import the correct library based on the Python version number reported by the Python interpreter.
|
||||
|
||||
NOTE: It's 2019 and 2.7 support is being systematically removed. This construct will be removed from the demo programs shortly. 2.7 users can still run these demos, but they will need to change the import from PySimpleGUI to PySimpleGUI27. It save 4 lines of code and an import from sys in the process.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -30,6 +30,11 @@ https://github.com/PySimpleGUI/PySimpleGUI/tree/master/PySimpleGUIWeb/Demo%20Pro
|
|||
There are not many programs under each of the port's folders because the main Demo Programs should run on all of the other platforms with minimal changes (often only the import statement changes).
|
||||
|
||||
|
||||
You will also find a lot of demos running on Trinket
|
||||
http://Trinket.PySimpleGUI.org
|
||||
|
||||
|
||||
|
||||
## Packages Used In Demos
|
||||
|
||||
|
||||
|
|
@ -213,36 +218,80 @@ You'll quickly wonder how you ever coded without it.
|
|||
|
||||
Well, there are a few quirks, and problems of course. Check the [GitHub Issues database](https://github.com/PySimpleGUI/PySimpleGUI/issues) for a list of them.
|
||||
|
||||
As previously mentioned this is also where you should post all problems and enhancements.
|
||||
As previously mentioned **this is where you should post all problems and enhancements.**
|
||||
|
||||
Random crashes have been rared. The code is stable and hasn't been "quirky" nor have there been many "emergency" releases.
|
||||
|
||||
|
||||
## MACS + tkinter = SUCKS
|
||||
## MACS & tkinter
|
||||
|
||||
Not sure why, but for over a year and a half, setting the color of buttons does not work on Macs. There have been numerous other problems. Checking the Issues database is the best place to see what they are. If there was a magic wand it would have been used long ago to fix these problems, but there does not appear to be a magic fix.
|
||||
Macs and PySimpleGUI did not play well together up until Nov 2019 and the release of ttk buttons. Prior to that buttons had to be white. Now the Mac can use any color for buttons and they work great. Images on buttons work as well.
|
||||
|
||||
The problems were the normal tk.Button was not working correctly on the Mac. You couldn't set the button color. If you tried it appeared as if the text was missing.
|
||||
|
||||
Users have recently reported the ability to install Python 3.7 from the Python.org website and not use the Homebrew version. This resolved all of the button color problems.
|
||||
|
||||
Regardless of where you get your Python / tkinter, Macs can now enjoy using all of the look and feel color themes that Windows and Linux users are able to achieve.
|
||||
|
||||
Many PySimpleGUI users have switched from PySimpleGUI to PySimpleGUIQt due to the button problems. IF you're one of them, ***you should consider switching back***. One reason to return to PySimpleGUI is that features tend to get iumplemented on PySimpleGUI (tkinger version) and then later on the other ports. There are a number of other reasons to give tkinter another try.
|
||||
|
||||
This was already mentioned at the top of this document but want to make sure it's covered as a "known issue"
|
||||
|
||||
## Multiple threads
|
||||
|
||||
While not an "issue" this is a ***stern warning***
|
||||
Consider this is a ***stern warning***
|
||||
|
||||
## **Do not attempt** to call `PySimpleGUI` from multiple threads! It's `tkinter` based and `tkinter` has issues with multiple threads
|
||||
### **Do not attempt** to call `PySimpleGUI` from multiple threads! At least the `tkinter` based port because tkinter is not threadsafe and has known issues with multiple threads
|
||||
|
||||
Tkinter also wants to be the MAIN thread in your code. So, if you have to run multiple threads, make sure the GUI is the main thread.
|
||||
|
||||
Other than that, feel free to use threads with PySimpleGUI on all of the ports. You'll find a good example for how to run "long running tasks" in your event loop by looking at the demo program: `Demo_Multithreaded_Long_Tasks.py`
|
||||
Other than that, feel free to use threads with PySimpleGUI on all of the ports. You'll find a good example for how to run "long running tasks" in your event loop by looking at the demo program: `Demo_Multithreaded_Long_Tasks.py`. There are several examples of using threads with PySimpleGUI.
|
||||
|
||||
Be sure and **delete** your windows after you close them if you are running with multiple threads. There is a chance another thread's garbage collect will attempt to delete the window when not in the mainthread which will cause tkinter to crash.
|
||||
|
||||
### The dreaded "Tcl_AsyncDelete: async handler deleted by the wrong thread" error
|
||||
|
||||
This crash has plagued and mystified tkinter users for some time now. It happens when the user is running multiple threads in their application. Even if the user doesn't make any calls that are into tkinter, this problem can still cause your program to crash.
|
||||
|
||||
I'm thrilled to say there's a solution and it's easy to implement. If you're getting this error, then here is what is causing it.
|
||||
|
||||
When you close a window and delete the layout, the tkinter widgets that were in use in the window are no longer needed. Python marks them to be handled by the "Garbage Collector". They're deleted but not quite gone from memory. Then, later, while your thread is running, the Python Garbage Collect algorithm decides it's time to run garbage collect. When it tells tkinter to free up the memory, the tkinter code looks to see what context it is running under. It sees that it's a thread, not the main thread, and generates this exception.
|
||||
|
||||
The way around this is actually quite easy.
|
||||
|
||||
When you are finished with a window, be sure to:
|
||||
|
||||
* Close the Window
|
||||
* Set the `layout` variable to None
|
||||
* Set the `window` variable to None
|
||||
* Trigger Python's Garbage Collect to run immediately
|
||||
|
||||
The sequence looks like this in code:
|
||||
|
||||
```python
|
||||
import gc
|
||||
|
||||
# Do all your windows stuff... make a layout... show your window... then when time to exit
|
||||
window.close()
|
||||
layout = None
|
||||
window = None
|
||||
gc.collect()
|
||||
```
|
||||
|
||||
This will ensure that the tkinter widgets are all deleted in the context of the mainthread and another thread won't accidently run the Garbage Collect
|
||||
|
||||
|
||||
|
||||
# Contributing
|
||||
|
||||
## Core Code
|
||||
## Write Applications
|
||||
|
||||
***Core code changes/pull requests are not being accepted at this time.***
|
||||
The way for you to contribute to the PySimpleGUI is to create and share PySimpleGUI GUIs. **Everyone** learns from seeing other peoples' implementations. It's through user's creating applications that new problems and needs are discovered. These have had a profound and positive impact on the project and helped to create thw you see today.
|
||||
|
||||
## Demos
|
||||
## Pull Requests
|
||||
|
||||
***PySimpleGUI changes/pull requests are not being accepted at this time.***
|
||||
|
||||
You're welcome to share a PySimpleGUI program you've written that you think fits the model of a PySimpleGUI Demo Program.
|
||||
|
||||
## GitHub Repos
|
||||
|
||||
If you've created a GitHub for your project that uses PySimpleGUI then please submit it to be included in this document or on the PySimpleGUI GitHub site. Also, you'll find a lot more people will look at your code, explore your repo if you have posted **screen shots in your readme**. People *love* success stories and showing your GUI's screen shows you've been successful. Everyone wins!
|
||||
If you've created a GitHub for your project that uses PySimpleGUI then please post screenshots in in the "User's Screenshots" Issue on the PySimpleGUI GitHub. Say a little something about it and I'll also add it to the annoucements. People *love* success stories and showing your GUI's screen visually communicates your success.
|
||||
|
|
|
|||
|
|
@ -896,9 +896,158 @@ TTK WIDGETS! Welcome back Mac Users!
|
|||
* Test harness changes to help test new ttk stuff (want to shrink this window in the future so will fit on Trinket, Pi, etc
|
||||
|
||||
|
||||
## 4.8.0 PySimpleGUI 4-Dec-2019
|
||||
|
||||
Multicolored multiline text! Often asked for feature going way back
|
||||
ttk Buttons can have images
|
||||
Print in color!
|
||||
|
||||
* Multiline Element got 2 new parameters to the update method
|
||||
* text_color_for_value - color for the newly added text
|
||||
* background_color_for_value - background color of the newly added text
|
||||
* New Print/EasyPrint parameters and capability
|
||||
* text_color, background_color - control the text's color and background color when printing to "Debug Window"
|
||||
* Must be done only when used in mode where stdout is not re-routed (the default)
|
||||
* Wouldn't it be really nice if normal print calls had this parameter?
|
||||
* Print(event, text_color='green', background_color='white', end='')
|
||||
* ttk Buttons
|
||||
* can have images. No longer forces Buttons with images to be the old tk Butons. Now you can choose either
|
||||
* can update the button color
|
||||
* can update the button image
|
||||
* Set warning filter so that warnings are repeated
|
||||
* New global variables:
|
||||
* CURRENT_LOOK_AND_FEEL - The current look and feel setting in use. Starts out as "Default"
|
||||
* BROWSE_FILES_DELIMITER - Defaults to ";" It is the string placed between entries returned from a FilesBrowse button
|
||||
* TRANSPARENT_BUTTON - Depricated - was being used incorrectly as it was a relic from the early days. It's value was a color of gray
|
||||
* Window - gentle reminder if you don't choose a look and feel for your window. It's easy to stop them. Add a change_look_and_feel line
|
||||
* Test harness uses a debug window so don't be shocked when 2 windows appear when running PySimpleGUI by itself
|
||||
* Prints the "Event" in Green on White text
|
||||
* Prints the "values" normally
|
||||
|
||||
## 4.9.0 PySimpleGUI 7-Dec-2019
|
||||
|
||||
The "Finally Nailed Tabs" release
|
||||
|
||||
* Colors for Tabs!
|
||||
* When creating TabGroup can now specify
|
||||
* Text & Background color of all tabs
|
||||
* Text & Background color of selected tab
|
||||
* If nothing is specified then the Look and Feel theme will be used (which turned out GREAT)
|
||||
* Tab visibility - Can finally control individual tab's visibility using update and when creating
|
||||
* More "Look and Feel" Themes! There's no excuse to be grey again. There are now 126 themes to choose from. Here are the 32 new themes"
|
||||
DefaultNoMoreNagging
|
||||
DarkBlack1
|
||||
DarkBlue12
|
||||
DarkBlue13
|
||||
DarkBlue14
|
||||
DarkBlue15
|
||||
DarkBlue16
|
||||
DarkBlue17
|
||||
DarkBrown5
|
||||
DarkBrown6
|
||||
DarkGreen2
|
||||
DarkGreen3
|
||||
DarkGreen4
|
||||
DarkGreen5
|
||||
DarkGreen6
|
||||
DarkGrey4
|
||||
DarkGrey5
|
||||
DarkGrey6
|
||||
DarkGrey7
|
||||
DarkPurple6
|
||||
DarkRed2
|
||||
DarkTeal10
|
||||
DarkTeal11
|
||||
DarkTeal12
|
||||
DarkTeal9
|
||||
LightBlue6
|
||||
LightBlue7
|
||||
LightBrown12
|
||||
LightBrown13
|
||||
LightGray1
|
||||
LightGreen10
|
||||
LightGreen9
|
||||
LightGrey6
|
||||
* preview_all_look_and_feel_themes now has a columns parameter to control number of entries per rows
|
||||
* also made each theme display smaller due to large number of themes
|
||||
|
||||
|
||||
## 4.10.0 PySimpleGUI 9-Dec-2019
|
||||
|
||||
"Oh crap the debugger is broken!" + "Pretty Progress Bars" release
|
||||
|
||||
* Fix for built-in debugger not working
|
||||
* Important due to upcoming educational usage
|
||||
* Has been broken since 4.5.0 when a change to Finalize was made
|
||||
* ProgessBar element colors set using Look and Feel colors
|
||||
* Combination of button color, input element, and input element text are used
|
||||
|
||||
|
||||
## 4.11.0 PySimpleGUI 10-Dec-2019
|
||||
|
||||
The Element & Window bindings release
|
||||
|
||||
* Element.bind - New method of all Elements
|
||||
* Enables tkinter bindings to be added to any element
|
||||
* Will get an event returned from window.read() if the tkinter event happens
|
||||
* Window.bind - New method for Windows, just like Elements
|
||||
* Enables tkinter bindings to be added to Windows
|
||||
* Will get an event returned from window.read() if the tkinter event happens
|
||||
* TabGroup fonts - can now set the font and font size for Tab text
|
||||
|
||||
|
||||
|
||||
## 4.12.0 PySimpleGUI 14-Dec-2019
|
||||
|
||||
Finally no more outlines around TK Elements on Linux
|
||||
|
||||
* Fixed a long-term problem of the mysterious white border around (almost) all TK Elements on Linux
|
||||
* Ability to set the disabled button colors
|
||||
* New Button and Button.update parameter - disabled_button_color
|
||||
* Specified as (Text Color, Background Color) just like button colors
|
||||
* For Normal / TK Buttons - can set button text color only
|
||||
* For TTK Buttons - can set both a disabled button and text color
|
||||
* Either parameter can be None to use current setting
|
||||
* Removed use of CloseButton from Popups (still have a bug in the CloseButton code but not in popups now)
|
||||
* Combobox - removed requirement of setting disabled if want to set to readonly using update method
|
||||
* Fix for cancelling out of file/folder browse on Linux caused target to be cleared instead of just cancelling
|
||||
* Removed try block around setting button colors - if user sets a bad color, well don't do that
|
||||
* Now deleting windows after closing them for popup
|
||||
|
||||
|
||||
## 4.13.0 PySimpleGUI 18-Dec-2019
|
||||
|
||||
Table and Tree header colors, expanded Graph methods
|
||||
|
||||
* Element.expand new parameter - expand_row. If true then row will expand along with the widgets. Provides better resizing control
|
||||
* Using math.floor now instead of an int cast in Graph Element's unit conversions
|
||||
* Graph.draw_point - now using caller's graph units for specifying point size
|
||||
* Graph.draw_circle - converted radius size from user's graph units.
|
||||
* Graph.draw_circle - added line_width parameter
|
||||
* Graph.draw_oval - added line_width parameter
|
||||
* Graph.get_figures_at_location - new method for getting a list of figures at a particular point
|
||||
* Graph.get_bounding_box - returns bounding box for a previously drawn figure
|
||||
* Table and Tree Elements
|
||||
* 3 new element creation parameters
|
||||
* header_text_color - color of the text for the column headings
|
||||
* header_background_color - color of the background of column headings
|
||||
* header_font - font family, style , size for the column headings
|
||||
* Defaults to using the current look and feel setting
|
||||
* Uses similar algorithm as Tabs - Input Text background and text colors are used
|
||||
* Spin element - fixed bug that showed "None" if default value is "None"
|
||||
* Test Harness sets incorrect look and feel on purpose so a random one is chosen
|
||||
|
||||
|
||||
### Upcoming
|
||||
|
||||
Make suggestions people! Future release features
|
||||
There will always be overlapping work as the ports will never actually be "complete" as there's always something new that can be built. However there's a definition for the base functionality for PySimpleGUI. This is what is being strived for with the currnt ports that are underway.
|
||||
|
||||
The current road ahead is to complete these ports - Qt (very close), Web (pretty close), Wx (not all that close).
|
||||
|
||||
PySimpleGUIDroid is in the works....
|
||||
|
||||
In addition to the ports there is ongoing work with educators that want to bring PySimpleGUI into their classrooms. Some projects have already started with teachers. One effort is to examine a number of books that teach Python to kids and convert the exercises to use PySimpleGUI instead of tkinter or command line. Another educational effort is in integrating with Circuit Python. It's unclear exactly how PySimpleGUI will fit into the picture. A board from Adafruit is arriving soon which should help solidify what's possible.
|
||||
|
||||
|
||||
|
||||
## Code Condition
|
||||
|
|
@ -907,11 +1056,11 @@ Make suggestions people! Future release features
|
|||
Make it right
|
||||
Make it fast
|
||||
|
||||
It's a recipe for success if done right. PySimpleGUI has completed the "Make it run" phase. It's far from "right" in many ways. These are being worked on. The module is particularly poor for PEP 8 compliance. It was a learning exercise that turned into a somewhat complete GUI solution for lightweight problems.
|
||||
It's a recipe for success if done right. PySimpleGUI has completed the "Make it run" phase. It's far from "right" in many ways. These are being worked on. The module has historically been particularly poor for PEP8 compliance. It was a learning exercise that turned into a somewhat complete GUI solution for lightweight problems.
|
||||
|
||||
While the internals to PySimpleGUI are a tad sketchy, the public interfaces into the SDK are more strictly defined and comply with PEP 8 for the most part.
|
||||
While the internals to PySimpleGUI are a tad sketchy, the public interfaces into the SDK are more strictly defined and comply with PEP8 naming conventions. A set of "PEP8 Bindings" was released in summar 2019 to ensure the enternally facing interfaces all adhere to PEP8 names.
|
||||
|
||||
Please log bugs and suggestions in the GitHub! It will only make the code stronger and better in the end, a good thing for us all, right?
|
||||
Please log bugs and suggestions **only on the PySimpleGUI GitHub**! It will only make the code stronger and better in the end, a good thing for us all, right? Logging them elsewhere doesn't enable the core developer and other PySimpleGUI users to help. To make matters worse, you may get bad advice from other sites because there are simply not many PySimpleGUI experts, yet.
|
||||
|
||||
## Design
|
||||
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -298,6 +298,7 @@ def get_sig_table_parts(function_obj, function_name, doc_string, logger=None, is
|
|||
elif type(val) is str: rows.append(f'{key}="{val}"')
|
||||
elif type(val) is tuple: rows.append(f'{key}={val}')
|
||||
elif type(val) is bool: rows.append(f'{key}={val}')
|
||||
elif type(val) is bytes: rows.append(f'{key}=...')
|
||||
else:
|
||||
raise Exception(f'IDK this type -> {key, val}')
|
||||
|
||||
|
|
@ -434,8 +435,22 @@ def main(do_full_readme=False, files_to_include: list = [], logger:object=None,
|
|||
# 8888888888888888888888888888888888888888888888888888888888888888888888888
|
||||
# =========== 2 GET classes, funcions, varialbe a.k.a. memes =========== #
|
||||
# 8888888888888888888888888888888888888888888888888888888888888888888888888
|
||||
psg_members = getmembers(PySimpleGUIlib) # variables, functions, classes
|
||||
|
||||
def valid_field(pair):
|
||||
bad_fields = 'LOOK_AND_FEEL_TABLE copyright __builtins__ icon'.split(' ')
|
||||
bad_prefix = 'TITLE_ TEXT_ ELEM_TYPE_ DEFAULT_ BUTTON_TYPE_ LISTBOX_SELECT METER_ POPUP_ THEME_'.split(' ')
|
||||
|
||||
field_name, python_object = pair
|
||||
if type(python_object) is bytes:
|
||||
return False
|
||||
if field_name in bad_fields:
|
||||
return False
|
||||
if any([i for i in bad_prefix if field_name.startswith(i)]):
|
||||
return False
|
||||
return True
|
||||
|
||||
psg_members = [i for i in getmembers(PySimpleGUIlib) if valid_field(i)] # variables, functions, classes
|
||||
# psg_members = getmembers(PySimpleGUIlib) # variables, functions, classes
|
||||
psg_funcs = [o for o in psg_members if isfunction(o[1])] # only functions
|
||||
psg_classes = [o for o in psg_members if isclass(o[1])] # only classes
|
||||
psg_classes_ = list(set([i[1] for i in psg_classes])) # boildown B,Btn,Butt -into-> Button
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load Diff
|
|
@ -92,6 +92,7 @@ if method == 'with logs':
|
|||
########################################
|
||||
if enable_popup:
|
||||
import PySimpleGUI as sg
|
||||
sg.change_look_and_feel('Dark Green 2')
|
||||
lines = open('usage.log.txt', mode='r').readlines()
|
||||
sg.PopupScrolled('Completed making {}'.format(OUTPUT_FILENAME), ''.join(lines), size=(80,50))
|
||||
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ import PySimpleGUIlib
|
|||
Displays the results in a PySimpleGUI window which can be used to copy and paste into other places.
|
||||
|
||||
"""
|
||||
PySimpleGUIlib.theme('Dark Green 2')
|
||||
|
||||
layout = [[PySimpleGUIlib.Output(size=(80,50))]]
|
||||
window = PySimpleGUIlib.Window('Dump of tags', layout, resizable=True).Finalize()
|
||||
|
|
|
|||
Loading…
Reference in New Issue