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 steve.dower
Recipients eryksun, iMath, mmaswg, ohno, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-10-28.21:07:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1635455223.16.0.896836819685.issue30082@roundup.psfhosted.org>
In-reply-to
Content
I'd rather only have one force_hide option that does its best to hide everything.

Yes, it's probably unintuitive for GUI apps, it might even be maliciously misused, but it does have occasional legitimate uses. And besides, an app can easily ignore SW_HIDE if it wants.

Bear in mind that the test suite should (mostly) operate without ctypes. So if you use ctypes to verify the test, make it a separate test that skips if ctypes cannot be imported, and have a test that runs it without verifying the window is actually hidden. That way we always at least _run_ the code, even if we only (usually) verify that it's actually hiding the window.
History
Date User Action Args
2021-10-28 21:07:03steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun, iMath, ohno, mmaswg
2021-10-28 21:07:03steve.dowersetmessageid: <1635455223.16.0.896836819685.issue30082@roundup.psfhosted.org>
2021-10-28 21:07:03steve.dowerlinkissue30082 messages
2021-10-28 21:07:03steve.dowercreate