Trivial tkinter button works on Python 3.5, initially unresponsive on Python 3.6, 3.7 The Next CEO of Stack OverflowTkinter window unresponsive in embedded pythonPython tkinter ttk one radio button appears the wrong sizePython/Tkinter: drawing an Entry on top of a ButtonPython tkinter: button disappearing after label updateTkinter root widget won't initialize with python 3.5Python Tkinter Window not closingpython tkinter menu , how to change font?Python 3.6, using tkinter, gives me the spinning beachball forever. (mac)Python 3.6 + tkinter: Stop while loop with Buttontkinter: mainloop() opens root window twice
How to make a variable always equal to the result of some calculations?
MAZDA 3 2006 (UK) - poor acceleration then takes off at 3250 revs
How do I construct this japanese bowl?
Shade part of a Venn diagram
Was a professor correct to chastise me for writing "Prof. X" rather than "Professor X"?
Is it my responsibility to learn a new technology in my own time my employer wants to implement?
Why does standard notation not preserve intervals (visually)
When Does an Atlas Uniquely Define a Manifold?
How to safely derail a train during transit?
Are there languages with no euphemisms?
How does practicing restraint and performing actions of merit purify the mind?
How can I open an app using Terminal?
Is a stroke of luck acceptable after a series of unfavorable events?
If the heap is initialized for security, then why is the stack uninitialized?
Is HostGator storing my password in plaintext?
How do I go from 300 unfinished/half written blog posts, to published posts?
Increase performance creating Mandelbrot set in python
How to be diplomatic in refusing to write code that breaches the privacy of our users
Science fiction (dystopian) short story set after WWIII
What do "high sea" and "carry" mean in this sentence?
Why here is plural "We went to the movies last night."
Need some help with wall behind rangetop
How easy is it to start Magic from scratch?
Go Pregnant or Go Home
Trivial tkinter button works on Python 3.5, initially unresponsive on Python 3.6, 3.7
The Next CEO of Stack OverflowTkinter window unresponsive in embedded pythonPython tkinter ttk one radio button appears the wrong sizePython/Tkinter: drawing an Entry on top of a ButtonPython tkinter: button disappearing after label updateTkinter root widget won't initialize with python 3.5Python Tkinter Window not closingpython tkinter menu , how to change font?Python 3.6, using tkinter, gives me the spinning beachball forever. (mac)Python 3.6 + tkinter: Stop while loop with Buttontkinter: mainloop() opens root window twice
On Python 3.6 and 3.7 on MacOS 10.12.6, a tkinter.Button does not initially respond to clicks - but the same code works perfectly on Python 3.5.
If I run the following script:
import tkinter as tk
root = tk.Tk()
button = tk.Button(root, text='Button')
button.pack()
root.mainloop()
then on Python 3.6 and 3.7, a window appears with a single button as expected, it does not visually appear to be disabled, but clicking on it has no effect.
Resizing the window or clicking elsewhere within it does not fix the issue.
However, if I bring another application to the foreground and then bring the Python application back to the front, everything works perfectly, and I am then unable to make the issue reappear.
In Python 3.5, running the test script brings up the application and the button is immediately responsive to clicks - as expected. Experimentation was unable to reproduce any issues in 3.5. The script also runs fine in Python 2.7 if tkinter is replaced by Tkinter.
Changing the pack layout manager to grid gave exactly the same results.
I went so far as to reboot the machine, with no change.
I am close to 100% certain that the Python 3.6 and Python 3.7 binaries and libraries are in a good state. They are essentially clean installs as I work entirely in virtualenvs. And my non-trivial tkinter application runs identically on Python 3.5, 3.6 and 3.7, except for this one problem.
python python-3.x tkinter
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
|
show 3 more comments
On Python 3.6 and 3.7 on MacOS 10.12.6, a tkinter.Button does not initially respond to clicks - but the same code works perfectly on Python 3.5.
If I run the following script:
import tkinter as tk
root = tk.Tk()
button = tk.Button(root, text='Button')
button.pack()
root.mainloop()
then on Python 3.6 and 3.7, a window appears with a single button as expected, it does not visually appear to be disabled, but clicking on it has no effect.
Resizing the window or clicking elsewhere within it does not fix the issue.
However, if I bring another application to the foreground and then bring the Python application back to the front, everything works perfectly, and I am then unable to make the issue reappear.
In Python 3.5, running the test script brings up the application and the button is immediately responsive to clicks - as expected. Experimentation was unable to reproduce any issues in 3.5. The script also runs fine in Python 2.7 if tkinter is replaced by Tkinter.
Changing the pack layout manager to grid gave exactly the same results.
I went so far as to reboot the machine, with no change.
I am close to 100% certain that the Python 3.6 and Python 3.7 binaries and libraries are in a good state. They are essentially clean installs as I work entirely in virtualenvs. And my non-trivial tkinter application runs identically on Python 3.5, 3.6 and 3.7, except for this one problem.
python python-3.x tkinter
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
Okay, but what's your question? What kind of answer are you looking for?
– Aran-Fey
Mar 8 at 13:14
change your line to this:button = tk.Button(root, text='Button', command=lambda:print('Hello!')), this will test if button really works
– Andrii Chumakov
Mar 8 at 13:35
1
There's nothing wrong with your code. I think the OSX version of tkinter is a little buggy.
– Bryan Oakley
Mar 8 at 13:40
@AndriiChumakov : I just edited the code to do that explicit test, and it works in the tiny test too.
– Tom Swirly
Mar 8 at 13:57
1
@Tom you are not the 1st to use it on mac. That is why Bryan is saying its a bit buggy on OSX. Because others have had problems. I wonder if doingroot.update_idletasks()right before you create the button may fix the problem. I know there are some focus issues in tkinter it will fix so its worth giving it a try here.
– Mike - SMT
Mar 8 at 14:30
|
show 3 more comments
On Python 3.6 and 3.7 on MacOS 10.12.6, a tkinter.Button does not initially respond to clicks - but the same code works perfectly on Python 3.5.
If I run the following script:
import tkinter as tk
root = tk.Tk()
button = tk.Button(root, text='Button')
button.pack()
root.mainloop()
then on Python 3.6 and 3.7, a window appears with a single button as expected, it does not visually appear to be disabled, but clicking on it has no effect.
Resizing the window or clicking elsewhere within it does not fix the issue.
However, if I bring another application to the foreground and then bring the Python application back to the front, everything works perfectly, and I am then unable to make the issue reappear.
In Python 3.5, running the test script brings up the application and the button is immediately responsive to clicks - as expected. Experimentation was unable to reproduce any issues in 3.5. The script also runs fine in Python 2.7 if tkinter is replaced by Tkinter.
Changing the pack layout manager to grid gave exactly the same results.
I went so far as to reboot the machine, with no change.
I am close to 100% certain that the Python 3.6 and Python 3.7 binaries and libraries are in a good state. They are essentially clean installs as I work entirely in virtualenvs. And my non-trivial tkinter application runs identically on Python 3.5, 3.6 and 3.7, except for this one problem.
python python-3.x tkinter
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
On Python 3.6 and 3.7 on MacOS 10.12.6, a tkinter.Button does not initially respond to clicks - but the same code works perfectly on Python 3.5.
If I run the following script:
import tkinter as tk
root = tk.Tk()
button = tk.Button(root, text='Button')
button.pack()
root.mainloop()
then on Python 3.6 and 3.7, a window appears with a single button as expected, it does not visually appear to be disabled, but clicking on it has no effect.
Resizing the window or clicking elsewhere within it does not fix the issue.
However, if I bring another application to the foreground and then bring the Python application back to the front, everything works perfectly, and I am then unable to make the issue reappear.
In Python 3.5, running the test script brings up the application and the button is immediately responsive to clicks - as expected. Experimentation was unable to reproduce any issues in 3.5. The script also runs fine in Python 2.7 if tkinter is replaced by Tkinter.
Changing the pack layout manager to grid gave exactly the same results.
I went so far as to reboot the machine, with no change.
I am close to 100% certain that the Python 3.6 and Python 3.7 binaries and libraries are in a good state. They are essentially clean installs as I work entirely in virtualenvs. And my non-trivial tkinter application runs identically on Python 3.5, 3.6 and 3.7, except for this one problem.
python python-3.x tkinter
python python-3.x tkinter
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
asked Mar 8 at 13:11
Tom SwirlyTom Swirly
1,87011935
1,87011935
Okay, but what's your question? What kind of answer are you looking for?
– Aran-Fey
Mar 8 at 13:14
change your line to this:button = tk.Button(root, text='Button', command=lambda:print('Hello!')), this will test if button really works
– Andrii Chumakov
Mar 8 at 13:35
1
There's nothing wrong with your code. I think the OSX version of tkinter is a little buggy.
– Bryan Oakley
Mar 8 at 13:40
@AndriiChumakov : I just edited the code to do that explicit test, and it works in the tiny test too.
– Tom Swirly
Mar 8 at 13:57
1
@Tom you are not the 1st to use it on mac. That is why Bryan is saying its a bit buggy on OSX. Because others have had problems. I wonder if doingroot.update_idletasks()right before you create the button may fix the problem. I know there are some focus issues in tkinter it will fix so its worth giving it a try here.
– Mike - SMT
Mar 8 at 14:30
|
show 3 more comments
Okay, but what's your question? What kind of answer are you looking for?
– Aran-Fey
Mar 8 at 13:14
change your line to this:button = tk.Button(root, text='Button', command=lambda:print('Hello!')), this will test if button really works
– Andrii Chumakov
Mar 8 at 13:35
1
There's nothing wrong with your code. I think the OSX version of tkinter is a little buggy.
– Bryan Oakley
Mar 8 at 13:40
@AndriiChumakov : I just edited the code to do that explicit test, and it works in the tiny test too.
– Tom Swirly
Mar 8 at 13:57
1
@Tom you are not the 1st to use it on mac. That is why Bryan is saying its a bit buggy on OSX. Because others have had problems. I wonder if doingroot.update_idletasks()right before you create the button may fix the problem. I know there are some focus issues in tkinter it will fix so its worth giving it a try here.
– Mike - SMT
Mar 8 at 14:30
Okay, but what's your question? What kind of answer are you looking for?
– Aran-Fey
Mar 8 at 13:14
Okay, but what's your question? What kind of answer are you looking for?
– Aran-Fey
Mar 8 at 13:14
change your line to this:
button = tk.Button(root, text='Button', command=lambda:print('Hello!')), this will test if button really works– Andrii Chumakov
Mar 8 at 13:35
change your line to this:
button = tk.Button(root, text='Button', command=lambda:print('Hello!')), this will test if button really works– Andrii Chumakov
Mar 8 at 13:35
1
1
There's nothing wrong with your code. I think the OSX version of tkinter is a little buggy.
– Bryan Oakley
Mar 8 at 13:40
There's nothing wrong with your code. I think the OSX version of tkinter is a little buggy.
– Bryan Oakley
Mar 8 at 13:40
@AndriiChumakov : I just edited the code to do that explicit test, and it works in the tiny test too.
– Tom Swirly
Mar 8 at 13:57
@AndriiChumakov : I just edited the code to do that explicit test, and it works in the tiny test too.
– Tom Swirly
Mar 8 at 13:57
1
1
@Tom you are not the 1st to use it on mac. That is why Bryan is saying its a bit buggy on OSX. Because others have had problems. I wonder if doing
root.update_idletasks() right before you create the button may fix the problem. I know there are some focus issues in tkinter it will fix so its worth giving it a try here.– Mike - SMT
Mar 8 at 14:30
@Tom you are not the 1st to use it on mac. That is why Bryan is saying its a bit buggy on OSX. Because others have had problems. I wonder if doing
root.update_idletasks() right before you create the button may fix the problem. I know there are some focus issues in tkinter it will fix so its worth giving it a try here.– Mike - SMT
Mar 8 at 14:30
|
show 3 more comments
1 Answer
1
active
oldest
votes
I do not have a Mac to test on but your issue sounds very similar to a focus problem that can occur on windows when you open a file dialog before the mainloop has had its first complete loop. The issue has the same symptoms like not allow focus to get back to the window until you bring up some other app and then go back to the tkinter app and then it works.
The way to correct the focus issue is to apply root.update_idletasks() before the problem (IE. right before opening the file dialog) and in this case right before your button.
As the OP has pointed out they had to add the root.update_idletasks() before and after the widget and I am not sure why this was the fix here for OSX. For those reading this with the same issue on Mac go ahead and try this option for a work around.
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
This fixes the problem. Note that I had to callroot.update_idletasks()twice - once before and once after packing the button. Neither single call on its own worked!
– Tom Swirly
Mar 8 at 15:04
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
1
@TomSwirly you said you added the update before and after thepack()have you tried just adding it right before you define the button?
– Mike - SMT
Mar 8 at 15:15
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
|
show 1 more comment
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55063940%2ftrivial-tkinter-button-works-on-python-3-5-initially-unresponsive-on-python-3-6%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I do not have a Mac to test on but your issue sounds very similar to a focus problem that can occur on windows when you open a file dialog before the mainloop has had its first complete loop. The issue has the same symptoms like not allow focus to get back to the window until you bring up some other app and then go back to the tkinter app and then it works.
The way to correct the focus issue is to apply root.update_idletasks() before the problem (IE. right before opening the file dialog) and in this case right before your button.
As the OP has pointed out they had to add the root.update_idletasks() before and after the widget and I am not sure why this was the fix here for OSX. For those reading this with the same issue on Mac go ahead and try this option for a work around.
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
This fixes the problem. Note that I had to callroot.update_idletasks()twice - once before and once after packing the button. Neither single call on its own worked!
– Tom Swirly
Mar 8 at 15:04
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
1
@TomSwirly you said you added the update before and after thepack()have you tried just adding it right before you define the button?
– Mike - SMT
Mar 8 at 15:15
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
|
show 1 more comment
I do not have a Mac to test on but your issue sounds very similar to a focus problem that can occur on windows when you open a file dialog before the mainloop has had its first complete loop. The issue has the same symptoms like not allow focus to get back to the window until you bring up some other app and then go back to the tkinter app and then it works.
The way to correct the focus issue is to apply root.update_idletasks() before the problem (IE. right before opening the file dialog) and in this case right before your button.
As the OP has pointed out they had to add the root.update_idletasks() before and after the widget and I am not sure why this was the fix here for OSX. For those reading this with the same issue on Mac go ahead and try this option for a work around.
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
This fixes the problem. Note that I had to callroot.update_idletasks()twice - once before and once after packing the button. Neither single call on its own worked!
– Tom Swirly
Mar 8 at 15:04
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
1
@TomSwirly you said you added the update before and after thepack()have you tried just adding it right before you define the button?
– Mike - SMT
Mar 8 at 15:15
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
|
show 1 more comment
I do not have a Mac to test on but your issue sounds very similar to a focus problem that can occur on windows when you open a file dialog before the mainloop has had its first complete loop. The issue has the same symptoms like not allow focus to get back to the window until you bring up some other app and then go back to the tkinter app and then it works.
The way to correct the focus issue is to apply root.update_idletasks() before the problem (IE. right before opening the file dialog) and in this case right before your button.
As the OP has pointed out they had to add the root.update_idletasks() before and after the widget and I am not sure why this was the fix here for OSX. For those reading this with the same issue on Mac go ahead and try this option for a work around.
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
I do not have a Mac to test on but your issue sounds very similar to a focus problem that can occur on windows when you open a file dialog before the mainloop has had its first complete loop. The issue has the same symptoms like not allow focus to get back to the window until you bring up some other app and then go back to the tkinter app and then it works.
The way to correct the focus issue is to apply root.update_idletasks() before the problem (IE. right before opening the file dialog) and in this case right before your button.
As the OP has pointed out they had to add the root.update_idletasks() before and after the widget and I am not sure why this was the fix here for OSX. For those reading this with the same issue on Mac go ahead and try this option for a work around.
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
edited Mar 8 at 15:12
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
answered Mar 8 at 15:03
Mike - SMTMike - SMT
9,74121535
9,74121535
This fixes the problem. Note that I had to callroot.update_idletasks()twice - once before and once after packing the button. Neither single call on its own worked!
– Tom Swirly
Mar 8 at 15:04
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
1
@TomSwirly you said you added the update before and after thepack()have you tried just adding it right before you define the button?
– Mike - SMT
Mar 8 at 15:15
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
|
show 1 more comment
This fixes the problem. Note that I had to callroot.update_idletasks()twice - once before and once after packing the button. Neither single call on its own worked!
– Tom Swirly
Mar 8 at 15:04
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
1
@TomSwirly you said you added the update before and after thepack()have you tried just adding it right before you define the button?
– Mike - SMT
Mar 8 at 15:15
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
This fixes the problem. Note that I had to call
root.update_idletasks() twice - once before and once after packing the button. Neither single call on its own worked!– Tom Swirly
Mar 8 at 15:04
This fixes the problem. Note that I had to call
root.update_idletasks() twice - once before and once after packing the button. Neither single call on its own worked!– Tom Swirly
Mar 8 at 15:04
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
@TomSwirly that may just be part of the buggy issues with OSX. I have not had a chance to really work with python on Mac so I cannot say for sure why. I am glad that this little work around was the trick here.
– Mike - SMT
Mar 8 at 15:05
1
1
@TomSwirly you said you added the update before and after the
pack() have you tried just adding it right before you define the button?– Mike - SMT
Mar 8 at 15:15
@TomSwirly you said you added the update before and after the
pack() have you tried just adding it right before you define the button?– Mike - SMT
Mar 8 at 15:15
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
In fact, I added that line in all three places - before creating the button, before packing and after packing - and tried all eight combinations to make sure.
– Tom Swirly
Mar 8 at 15:28
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
@TomSwirly good to know.
– Mike - SMT
Mar 8 at 15:29
|
show 1 more comment
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55063940%2ftrivial-tkinter-button-works-on-python-3-5-initially-unresponsive-on-python-3-6%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Okay, but what's your question? What kind of answer are you looking for?
– Aran-Fey
Mar 8 at 13:14
change your line to this:
button = tk.Button(root, text='Button', command=lambda:print('Hello!')), this will test if button really works– Andrii Chumakov
Mar 8 at 13:35
1
There's nothing wrong with your code. I think the OSX version of tkinter is a little buggy.
– Bryan Oakley
Mar 8 at 13:40
@AndriiChumakov : I just edited the code to do that explicit test, and it works in the tiny test too.
– Tom Swirly
Mar 8 at 13:57
1
@Tom you are not the 1st to use it on mac. That is why Bryan is saying its a bit buggy on OSX. Because others have had problems. I wonder if doing
root.update_idletasks()right before you create the button may fix the problem. I know there are some focus issues in tkinter it will fix so its worth giving it a try here.– Mike - SMT
Mar 8 at 14:30