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 Lance Ware
Recipients Lance Ware, serhiy.storchaka, terry.reedy, zach.ware
Date 2016-11-24.17:44:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Good points, Zachary.

Regarding the commondialog.Dialog class, I think it would need to be enhanced to make sense using it with Fontchooser. It really doesn't do a whole lot, and the awful kludge in the show method (creating a Frame widget just so that some low-level operations can be performed) is repugnant to me. I think the whole thing is pretty out-of-date.

With the Font class, perhaps some of its functionality can be used. I will need to better understand the architecture of Font and see what I can do with it.

I think another issue that needs to be addressed is the modal/non-modal aspect of Tk fontchooser. I have access only to Windows OS, where it is modal. I have read that it is non-modal on Mac and perhaps other platforms. If that is the case, then the show method may not work properly on those other platforms. On Windows, the Tk command "tk fontchooser show" does not return control to the caller until after the user has clicked the OK or Cancel buttons. If it does return immediately on other platforms, then the show method may need do an update loop (or something better?) to keep the behavior consistent on the Python side.
Date User Action Args
2016-11-24 17:44:54Lance Waresetrecipients: + Lance Ware, terry.reedy, zach.ware, serhiy.storchaka
2016-11-24 17:44:54Lance Waresetmessageid: <>
2016-11-24 17:44:54Lance Warelinkissue28694 messages
2016-11-24 17:44:54Lance Warecreate