Applets running in Classic
Applets running in Classic
- Subject: Applets running in Classic
- From: Paul Berkowitz <email@hidden>
- Date: Sat, 09 Jun 2001 11:30:36 -0700
There are two huge problems I've come upon with classic stay-open applets
running in Classic:
1) I can't find a way to quit them. Unlike all other classic apps, when you
click in the Application Switcher to bring them to the front, the File menu
is dimmed, so you can't quit them there or with command-period. And script
editors can't quit them either, neither editors running in Classic (which
can't apparently execute the quit command) nor OS X editors.
2) Terrible consequences with memory leaks. Presumably they leak all the
time, but it doesn't seem to have any serious consequences when booted from
OS 9.1. I can leave a stay-open applet running for days without any problems
that I notice. Bit in OS X, where I think applications can just draw as much
memory as they need without limit until there is no more left (?), after
several hours Classic grinds to a halt and needs to be force-quit and
restarted. There must be other classic which will do this too, but i guess I
don't need to leave those running all the time.
My stay-open applet repeatedly pings the net to keep my routers open so I
can reach it remotely from my work computer, and I like it running all the
time. By removing it from my OS 9 Startup folder so it doesn't start up from
Classic, I seem to have solved the problem of Classic freezing : this applet
is definitely the culprit. I think I can come up with a routine whereby it
will only start up if the partition on which OS 9.1 resides, and not the
partition hosting OS X, is the startup disk. I'll then see if I can come up
with a separate OS X applet to do the same thing when logging in to OS X (if
I can avoid using the classic osax commands I'm currently using in the
script). I expect that there will not be any "memory leak" from OS X applets
(?).
Is this memory leak problem endemic to any classic applet?
I seem to recall that Smile is designed to have no memory leak whatsoever.
Presumably Smile would have to be open the whole time running open scripts
in the background, as a memory-free alternative to using an applet? [For
once, this is just for my own use, so I could do this if it works.]
--
Paul Berkowitz