|
From: Jeff H. <je...@Ac...> - 2005-07-25 17:36:14
|
> Agreed. I was thinking of something along these lines > for -command return code interpretations: > > TCL_OK -- > Default behavior -- dismiss the dialog if '-persistent false', > leave it up if '-persistent true'. > TCL_BREAK -- > Always dismiss the dialog (overriding '-persistent true') > TCL_CONTINUE -- > Always leave the dialog up (overriding '-persistent false') > TCL_RETURN -- > (same as TCL_OK?) The -persistent option to me seems more like "destroy" vs "withdraw", rather than stay up or not. Otherwise, that break and continue differentiation seems ok. > TCL_ERROR -- > Return the error result to the caller (normally > the event loop, which will eventually call bgerror). > Not sure what else should happen -- probably ought > to release the grab if '-modal true' was set. Always ensure the appropriate catch's are in the code to release grab if the user causes an error situation. > Other -- > Return the completion code/result/other return options > to to the caller. Jeff |