Thread Subject: Callback Cross close function

Hi,
I'm developing a compiled GUI application.
It works fine, but I have a problem:
I can't succeed in making the program to free memory when i
close it clicking on the X (cross) button of my application.

How can I write a callback for the X button?
How can I deallocate all memories, destroy all classes and
free memory (is a clear all enough before of returning?)
If you could help me, I would be very grateful!
Thank you very much in advance!!! -Luca-

"Luca Cerone" <cerone@to-see.it> wrote in message
<g0cb3g$17m$1@fred.mathworks.com>...
> Hi,
> I'm developing a compiled GUI application.
> It works fine, but I have a problem:
> I can't succeed in making the program to free memory when
i
> close it clicking on the X (cross) button of my
application.
>
> How can I write a callback for the X button?
> How can I deallocate all memories, destroy all classes and
> free memory (is a clear all enough before of returning?)
> If you could help me, I would be very grateful!
> Thank you very much in advance!!! -Luca-

To start with, use the "CloseRequestFcn" of the figure to
specify a callback function for whenever the figure is
requested to close (including using the X button). Note
that at the end of this function, use the DELETE function
to actually delete the figure.

As far as I know, CLEAR ALL is unnecessary to clear
variables from memory. Having the executable quit should
be enough to handle this.

However, things such as timers, serial objects, and OOP
classes need to be carefully considered during their
creation to ensure the appropriate cleanup and deletion
occurs during the "CloseRequestFcn". I do not believe
there is any command within MATLAB to automatically cleanup
and delete everything.

Note that the method for "cleaning up" things which require
it are well documented within MATLAB. For example, check
out the documentation for TIMER and SERIAL. They both show
the necessary "cleanup" steps.

> To start with, use the "CloseRequestFcn"
Thanks I just found it on Matlab Help 2 minutes ago ^_^

> As far as I know, CLEAR ALL is unnecessary to clear
> variables from memory. Having the executable quit should
> be enough to handle this.

I don't know why, but even using delete I get a warning say
something about UiOpenFileDialog class that is still exists
and won't be clean up...

> Note that the method for "cleaning up" things which require
> it are well documented within MATLAB. For example, check
> out the documentation for TIMER and SERIAL. They both show
> the necessary "cleanup" steps.

I'll try looking for Cleanup in Matlab Help (I'm sorry if I
ask something stupid, but the fact is that for a non-english
speaker, sometimes it's difficult to use the right wordkey
for search!)

Thank you very much in advance!
Hope to see you soon!