Re: executing programs
Re: executing programs
- Subject: Re: executing programs
- From: Charles Arthur <email@hidden>
- Date: Wed, 24 Jan 2001 00:11:07 +0000
On Tue, 23 Jan 2001 11:20:59 -0500, "Stephen Gross"
<email@hidden> wrote:
>
I know I posted this one before, but I've made very little progress, so
>
I was hoping someone might have some new ideas.
>
>
Basically the problem is that when I spawn new tasks through a script,
>
the machine eventually bombs out. Take this script for instance:
>
>
=====
>
on idle
>
select item x
>
open selection
>
return 10
>
end idle
>
=====
>
>
(Item x is an applet that beeps once, and that's all).
Surely this isn't the right use of an idle script? It seems to be doing too
much, if you see what I mean. I thought idles generally just tested for a
condition - if it's met (or not, you get the picture) then you "run"
eg
on idle
if selection is item x
run
end if
return 10
end idle
However a thread which I don't think got resolved was saying that ifs in
idles led to a memory leak which could crash the machine.....
Charles
http://www.ukclimbing.com : 1,000+ British crags, 350+ British climbing walls
- searchable by distance rock type, etc, with 5-day weather forecasts for
every one - plus maps, articles, news, and the New Routes database. There's
even a cool shop attached...