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 klappnase
Recipients Arfrever, gpolo, klappnase, serhiy.storchaka, terry.reedy
Date 2013-12-01.10:54:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385895278.91.0.920908263303.issue17397@psf.upfronthosting.co.za>
In-reply-to
Content
> Are 'unloaded but available' themes really available to use?

Yes.

> Does Style.theme_use(available_name) work?

Yes.

> If so, it seems to me that available_name should
> be reported by theme_names.

I agree, one should think so. I am not 100% certain about that, but to me it seems that on the tcl side ttk:themes is newer and thus preferable to theme names which maybe is only still there for backwards compatibility.

Since as a Tkinter user I like Tkinter methods to behave like their Tcl/Tk counterparts (which, if nothing else, helps a lot in reading and understanding  tcl code/documentation (and possibly "translating" tcl code into Python)) I had rather kept theme_names() intact to avoid confusion. Maybe there could simply a line like "Deprecated since Python-xy, use themes() instead." be added to theme_names' doc string ?
History
Date User Action Args
2013-12-01 10:54:38klappnasesetrecipients: + klappnase, terry.reedy, gpolo, Arfrever, serhiy.storchaka
2013-12-01 10:54:38klappnasesetmessageid: <1385895278.91.0.920908263303.issue17397@psf.upfronthosting.co.za>
2013-12-01 10:54:38klappnaselinkissue17397 messages
2013-12-01 10:54:38klappnasecreate