Comments on: Using UIWAIT/UIRESUME to control program flow http://blogs.mathworks.com/community/2011/03/28/using-uiwaituiresume-to-control-program-flow/ News from the intersection of MATLAB, Community, and the web. Wed, 22 May 2013 17:07:59 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Mike http://blogs.mathworks.com/community/2011/03/28/using-uiwaituiresume-to-control-program-flow/#comment-7664 Mike Tue, 29 Mar 2011 13:41:33 +0000 http://blogs.mathworks.com/desktop/2011/03/28/using-uiwaituiresume-to-control-program-flow/#comment-7664 @Yair,

Thanks for that reminder; it is quite important not to mix up the two functions.

]]> By: Yair Altman http://blogs.mathworks.com/community/2011/03/28/using-uiwaituiresume-to-control-program-flow/#comment-7663 Yair Altman Tue, 29 Mar 2011 08:15:44 +0000 http://blogs.mathworks.com/desktop/2011/03/28/using-uiwaituiresume-to-control-program-flow/#comment-7663 I would like to point out the very similar built-in function duo uisuspend and uirestore, which are similar in functionality and name to the uiwait and uiresume functions presented above. It is important not to confuse between these two function sets, and most importantly, not to confuse between uiresume and uirestore after using their counterparts earlier in the code – odd things might happen if you do…

Also, note that in Matlab releases up to R2010b, uirestore has a minor bug in that it overwrites the figure’s WindowScrollWheelFcn callback with the WindowKeyPressFcn value ( http://www.mathworks.com/support/bugreports/646025 ). This bug was finally fixed in R2011a.

IMHO, it would be better to modify uisuspend and uirestore to simply call their documented counterparts uiwait and uiresume, because the current situation can easily cause confusion.

]]>