Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!udel!new
From: new@udel.EDU (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Locking & forbiding
Message-ID: <17273@louie.udel.EDU>
Date: 9 Jun 89 17:43:37 GMT
References: <7cBq029532iy01@amdahl.uts.amdahl.com> <108333@sun.Eng.Sun.COM> <d2YG02GD32Hm01@amdahl.uts.amdahl.com> <108749@sun.Eng.Sun.COM> <1aY.02kv33t701@amdahl.uts.amdahl.com>
Sender: usenet@udel.EDU
Reply-To: new@udel.EDU (Darren New)
Organization: University of Delaware
Lines: 13

I have been doing something like this with a program I wrote called yatbc,
(yet another title bar clock) which puts the time and free mem in
the title bar of the window that is active when it starts.
This is a real hack, as it does no checking. It simply grabs the
active window pointer out of the IntuitionBase and calls SetTitle with
that pointer every time the title string changes. I wrote it mainly
because while developing I always have the one window open and
I don't like the screen-breaking that occurs with separate-window
clocks. I've never had any problem doing this, even when I accidentally
close the window and have to reopen another. The process sticks around,
but maybe Intuition is checking that it's args are correct or something
because I've never known it to cause a crash. If anyone wants this,
EMail me. Hope this helps... -- Darren