Zachary Ware added the comment: I can confirm this on the current 2.7 branch and, oddly, on a fresh build of v2.7.6. This looks like it was caused by the way Tcl/Tk was compiled, specifically the 'COMPILERFLAGS=-DWINVER=0x0500' and 'OPTS=noxp' options which are supposed to be for Win2k support. Removing just 'OPTS=noxp' causes a compilation failure (due to WINVER redefinition), but removing both makes ttk work properly.
Steve: how did you compile Tcl/Tk for the 2.7.7 installer? Martin: how have you compiled Tcl/Tk for past installers? In particular, Python 3.2's ttk works perfectly Win2k, but is properly themed on Windows 7, which leads me to believe that you did not use the 'Win2k compatibility' options. ---------- nosy: +loewis _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21665> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
