[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Changes by Martin v. Löwis : -- priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Changes by Christian Heimes: -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Kurt B. Kaiser added the comment: Assigning to tiran since I'm not building Python on XP. Changing to Tkinter, also. Is the file open bug fixed also by the suggested change? -- assignee: kbk -> tiran components: +Tkinter -IDLE __ Tracker <[EMAIL PROTE

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Amaury Forgeot d'Arc added the comment: I don't think this check is necessary. Some users may want to target specific windows versions, and compile their own modules with a higher WINVER. OTOH, python.org should compile with WINVER=0x0500, so that distributed binaries can run on most win32 platf

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Changes by Christian Heimes: -- priority: -> high resolution: -> fixed status: open -> pending __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bu

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Christian Heimes added the comment: Christian Heimes wrote: > Is 0x0500 fine for Windows 2000? Should we add WINVER=0x0500 to the > Python project files, too? http://msdn2.microsoft.com/en-us/library/aa383745.aspx Minimum system required Minimum value for _WIN32_WINNT and WINVER Windows

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Christian Heimes added the comment: Amaury Forgeot d'Arc wrote: > I found that the huge font in menus is due to an error in the call to > SystemParametersInfo. > Digging more, vc2008 defines WINVER=0x0600, which corresponds to Windows > Vista, and is too high for Windows XP: this value activates

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Amaury Forgeot d'Arc added the comment: I found that the huge font in menus is due to an error in the call to SystemParametersInfo. Digging more, vc2008 defines WINVER=0x0600, which corresponds to Windows Vista, and is too high for Windows XP: this value activates the definition of extra fields i

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Joseph Armbruster added the comment: Tiran, agreed. You can reproduce this issue quickly outside of IDLE with this snippet: from Tkinter import * import tkMessageBox class App(Frame): def __init__(self, master): Frame.__init__(self,master) self.master.title("Wierd Menu") self.con

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Christian Heimes added the comment: We are aware of several Windows related bugs with IDLE. I assume they are related to our Tcl/Tk build. -- nosy: +tiran __ Tracker <[EMAIL PROTECTED]> __

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Changes by Kurt B. Kaiser: -- keywords: +py3k __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

Changes by Guido van Rossum: -- assignee: -> kbk nosy: +kbk __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe:

[issue1601] IDLE not working correctly on Windows (Py30a2/IDLE30a1)

New submission from Mark Summerfield: (1) IDLE starts up on Windows OK, but if I press Alt+F the file menu comes up giant sized (i.e., each menu entry is almost as tall as the screen). (2) If I open a file using Ctrl+O, the Open dialog pops up fine, but when I select a file and click Open, IDLE c