This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author louielu
Recipients Al.Sweigart, littleq0903, louielu, markroseman, ned.deily, paulsfo, roger.serwy, serhiy.storchaka, suddha.sourav, taleinat, terry.reedy
Date 2017-05-10.03:52:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494388336.16.0.411986361096.issue15786@psf.upfronthosting.co.za>
In-reply-to
Content
@Terry, this is another too-fast-to-destroy problem. The latest PR commit has fixed the issue on MacOS.

When we double click on autocompletewindow, it will try to focusOut autocompletewindow then focusOn widget.text, but, we destroy too fast, after destroy, tk can't re-focusOn widget.text.

The commit will re-focus on widget.text first, then destroy the autocompletewindow.
History
Date User Action Args
2017-05-10 03:52:16louielusetrecipients: + louielu, terry.reedy, taleinat, ned.deily, roger.serwy, markroseman, Al.Sweigart, serhiy.storchaka, littleq0903, suddha.sourav, paulsfo
2017-05-10 03:52:16louielusetmessageid: <1494388336.16.0.411986361096.issue15786@psf.upfronthosting.co.za>
2017-05-10 03:52:16louielulinkissue15786 messages
2017-05-10 03:52:16louielucreate