From: <no...@so...> - 2000-11-09 01:46:30
|
Bug #122014, was updated on 2000-Nov-08 17:46 Here is a current snapshot of the bug. Project: Tk Toolkit Category: Events Status: Open Resolution: None Bug Group: 8.3.2 Priority: 5 Summary: bgerror doesn't skip messages with break Details: OS: Windows, Linux According to the documentation: "If several background errors accumulate before bgerror is invoked to process them, bgerror will be invoked once for each error, in the order they occurred. However, if bgerror returns with a break exception, then any remaining errors are skipped without calling bgerror." In the 8.0 version, "return -code break" works as expected. In the 8.3.2 version, the "return -code break" command in the bgerror handlers causes an exception and messages continue to be displayed. To reproduce: launch wish8.3.2 button .b -text "Button" -command foobar pack .b proc bgerror {error} { return -code break } Then click on the button. Notice the message in the standard output: bgerror failed to handle background error. Original error: invalid command name "foobar" Error in bgerror: invoked "break" outside of a loop For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=122014&group_id=12997 |