[issue46181] Destroying an expaned Combobox prevents Entry focus until Alt+Tab

Change by Serhiy Storchaka : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46181] Destroying an expaned Combobox prevents Entry focus until Alt+Tab

Terry J. Reedy added the comment: >From what I understand, this issue is about a somewhat esoteric tk-design or >program bug and should be closed as either 'not a bug' or '3rd-party'. -- ___ Python tracker

[issue46181] Destroying an expaned Combobox prevents Entry focus until Alt+Tab

Jonathan Lahav added the comment: Here's a discussion about the issue. I asked about it in comp.lang.tcl: https://groups.google.com/g/comp.lang.tcl/c/C-uQIH-wP5w Someone there explains what's happening. -- ___ Python tracker

[issue46181] Destroying an expaned Combobox prevents Entry focus until Alt+Tab

E. Paine added the comment: Reproduced using Wish built from the current Tk head (on Windows - I'm unable to reproduce on Linux). --- Strangely, invoking destroy in the trace callback raises a very strange error that appears to be missing the first two lines (tkinter may be hiding this

[issue46181] Destroying an expaned Combobox prevents Entry focus until Alt+Tab

Terry J. Reedy added the comment: Win10, Py 3.11: run combobug.py, click down arrow, click entry. 'changed' is printed to stdout (console or IDLE Shell). Cursor not visible and clicking on remaining entry box does nothing. Click on another window and back to entry box. Cursor is present in

[issue46181] Destroying an expaned Combobox prevents Entry focus until Alt+Tab

New submission from Jonathan Lahav : Happens on Windows. Observation: When an expanded Combobox is destroyerd, widgets in the window can't get focus until Alt+Tab forth and back. Buttons can still be clicked, but focus can't be obtained by widgets, entries fro example, not by clicking nor by