That should work. If you have a problem with it, please contact technical support – link at the right of this blog.

–Loren

aviobj = close(aviobj)

thanks

I should have said to use “ishandle” to check to see if the handle to your GUI is a valid handle.

You can use “isvalid” to check to see if the handle of waitbar is valid before updating it.

If you want the closing of the waitbar to trigger something else, you can assign a “DeleteFcn” for your waitbar.

The reason I ask, is that I have a GUI with a pushbutton callback. The callback calls another function (FNCx) with a long execution time. Before calling FNCx, however, the callback launches another GUI (much like a waitbar display). The waitbar is updated from within the FNCx. If the user brute force closes the custom waitbar GUI it causes an error when FNCx attempts to update the waitbar because the handle of the waitbar GUI is no longer valid.

If there were a means to detect a brute force close it would help simplify my code.

Regards,
Ken

As far as I know, there is no way to change it. There’s an outside chance that there’s a way to change the callback, but I don’t know if that’s possible, but if so, it should be in the documentation. Unfortunately, I have no access to MATLAB at the moment.

–Loren

Is there a way to “cancel” an onCleanup object’s task (i.e., delete the object without triggering its task)?

MATLAB doesn’t have any facility for handling Ctrl-C at the programming level that I know of. I don’t know why you don’t want to use a function, but that solution would be my preferred one, for this, and probably a bunch of other reasons.

–Loren

I know this is an old thread (exactly 2 years now that I think of it!), but I hope that you are still reading it.

I want to use something like onCleanup when a script m-file is aborted via Ctrl-C. My use case is that I have opened a number of Excel-workbooks as handles and write to them with a modified version of xlswrite (for speed considerations I don’t want to use the regular xlswrite which opens/closes the workbooks every time). I want the workbooks to be closed when the program is aborted, but onCleanup isn’t triggerd because the scripts variables don’t go out of scope. Obviously I could wrap the whole program into a function but that is not really what I want. Can you think of any workarounds?

thank you
Paul

A plain function handle could be fine in some cases, I think. In any case, you can rewrite @func as @()func() if it really doesn’t take any input.

–loren