[issue24587] Incorrect tkinter behavior of slave widgets of Button

[Eugene K.]

New submission from Eugene K.:

I've encountered this while trying to write a program that allowed the user to 
edit button labels, by creating an Entry widget on top of the  Button, and then 
hiding the Button. 

Sample code:

http://pastebin.com/WvBbLsNj

According to feedback from stackoverflow, it works as intended on MacOS and 
Debian. It does not work in Windows (I've tried Windows 7, 8, and Server 2012 
R2, with Python versions 2.7.5 to 2.7.9.)

The problem is that the button does not want to stay hidden. E.g. I create an 
Entry widget and it initially appears on top of the Button. Then, if I click 
inside the entry box, it briefly disappears (for a second or two), showing the 
button again, and then reappears. If I hit 'tab' and move focus out of the 
Entry, it disappears completely (exposing the button again) and only reappears 
when I click back into the entry/button area.

--
components: Tkinter
messages: 246445
nosy: Eugene K.
priority: normal
severity: normal
status: open
title: Incorrect tkinter behavior of slave widgets of Button
type: behavior
versions: Python 2.7

___
Python tracker 
<http://bugs.python.org/issue24587>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24587] Incorrect tkinter behavior of slave widgets of Button

[Eugene K.]

Eugene K. added the comment:

File attached

--
Added file: http://bugs.python.org/file39895/bug.py

___
Python tracker 
<http://bugs.python.org/issue24587>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24587] Tkinter stacking versus focus behavior on Windows

[Eugene K.]

Eugene K. added the comment:

It may not be a pure Python bug, but it's definitely at least a tk bug (which 
makes it a Python bug as long as tk is the canonical UI package in Python.) 

Workarounds are nice, but a workaround fixes my specific problem here and now, 
while leaving unknown numbers of Python UI developers scratching their heads at 
the unexpected behavior of their code.

I don't object to closing this bug as long as it's forwarded to tk/tkinter 
developers first.

--

___
Python tracker 
<http://bugs.python.org/issue24587>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com