From: Gautier write-only <gautier_niouzes@hotmail.com>
Subject: Re: Q: Stopping a task running a long simulation
Date: Thu, 11 Mar 2010 18:03:38 -0800 (PST)
Date: 2010-03-11T18:03:38-08:00 [thread overview]
Message-ID: <1f3de7cf-9bc0-481c-8019-ce053b5fdfe3@g11g2000yqe.googlegroups.com> (raw)
In-Reply-To: e4b75f1d-b0a7-4067-8433-dbe74add709f@b9g2000pri.googlegroups.com
> However, I'd be surprised by the behavior if you abort the task but
> Compute keeps using CPU for any length of time.
Yes, that would be a bit counter-intuitive (since the call to Compute
is part of the task).
What happens is that the abort is in the main window's Destroy method,
which occurs after its closing, so I guess it is just waiting at the
abort statement. And if I understand well, a delay 0.0 in the main
Compute loop would facilitate the aborting (I'll experiment it).
Anyway, in the end I'll use the more deterministic way discussed
elsewhere.
Thanks
Gautier
prev parent reply other threads:[~2010-03-12 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 13:08 Q: Stopping a task running a long simulation Gautier write-only
2010-03-11 18:11 ` Anh Vo
2010-03-12 0:24 ` tmoran
2010-03-12 1:15 ` Gautier write-only
2010-03-12 1:27 ` Adam Beneschan
2010-03-12 1:50 ` Gautier write-only
2010-03-12 2:03 ` Gautier write-only [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox