Prev: batch + mex files
Next: "ConnectionCallback" Bug in Simulink?
From: us on 26 Jul 2010 08:51
shoo <jgburgess(a)gmail.com> wrote in message <4a5f2db2-3a55-4ae8-a8c0-bae3e313b272(a)d17g2000yqb.googlegroups.com>...
> Hi,
>
> On Friday I started a function I knew was going to take a while...
> although I didn&#8217;t think it would take this long as it is now Monday
> and matlab is still 'busy'.
>
> I didn&#8217;t (stupidly) add code to output the progress of the
> function :<
>
> Is there a way i can stop the process like ctrl+c, but then resume it
> again? Or a way to find out how far into the process its got.
>
> I don't know when to give up and press ctrl+c.
>
>
> Thanks,
> Jon

no
us
From: shoo on 26 Jul 2010 08:56
On Jul 26, 1:51 pm, "us " <u...(a)neurol.unizh.ch> wrote:
> shoo <jgburg...(a)gmail.com> wrote in message <4a5f2db2-3a55-4ae8-a8c0-bae3e313b...(a)d17g2000yqb.googlegroups.com>...
> > Hi,
>
> > On Friday I started a function I knew was going to take a while...
> > although I didn&#8217;t think it would take this long as it is now Monday
> > and matlab is still 'busy'.
>
> > I didn&#8217;t (stupidly) add code to output the progress of the
> > function :<
>
> > Is there a way i can stop the process like ctrl+c, but then resume it
> > again? Or a way to find out how far into the process its got.
>
> > I don't know when to give up and press ctrl+c.
>
> > Thanks,
> > Jon
>
> no
> us

didnt think so =[
 | 
Pages: 1
Prev: batch + mex files
Next: "ConnectionCallback" Bug in Simulink?