[issue24860] handling of IDLE 'open module' errors

2015-08-13 Thread Terry J. Reedy
Terry J. Reedy added the comment: I see this as two related changes: a) Leave the module name query box open when there is a error, so the user can either correct a mistake (or hit Cancel) without reopening the box and re-entering the module name. Good idea. b) Put the error message in the

[issue24860] handling of IDLE 'open module' errors

2015-08-13 Thread Mark Roseman
Mark Roseman added the comment: Exactly. The querydialog code (which will replace the simpledialog askstring/askinteger calls) displays errors as shown in querydialog.png, with the error messages disappearing as soon as you hit another key. You can also pass in a 'validator' to check if the

[issue24860] handling of IDLE 'open module' errors

2015-08-13 Thread Mark Roseman
New submission from Mark Roseman: In EditorWindow.open_module... once switch to querydialog, display errors (e.g. module not found) in askstring dialog itself, not open up subsequent 'showerror' dialog -- components: IDLE messages: 248539 nosy: kbk, markroseman, roger.serwy,

[issue24860] handling of IDLE 'open module' errors

2015-08-13 Thread Terry J. Reedy
Terry J. Reedy added the comment: Where is querydialog? (It looks like something than should be in tkinter ;-). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24860 ___

[issue24860] handling of IDLE 'open module' errors

2015-08-13 Thread Mark Roseman
Mark Roseman added the comment: Work in progress, have a few more tweaks to make, but here's a snapshot... -- Added file: http://bugs.python.org/file40176/querydialog.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24860