home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Screen Problem in C.
- Date: 20 Jan 1996 13:13:52 +0100
- Organization: dis-
- Message-ID: <4dqma0$pu4@serpens.rhein.de>
- References: <DLE6wv.7FB@inter.NL.net> <1222.6593T260T330@norconnect.no>
- NNTP-Posting-Host: serpens.rhein.de
-
- kenneth@norconnect.no (Kenneth C. Nilsen) writes:
-
- >You can use this information in your programs, but to prevent the first
- >screen to be changed before you use the data after read, you must lock the
- >intuition base so that no one can change the current screen/window status.
- >Do this by intuition.library/LockIBase(). Read the pointer to first screen in
- >the intuition.library base (FirstScreen). Last, make a call to
- >UnlockIBase(ibLock) to allow others to use the intuition as well.
-
- Unfortunately this doesn't help since after UnlockIBase() the pointer
- may become invalid at any time. So you have to do anything you want
- with the pointer while holding the lock (this rules out anything complex).
-
- Regards,
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-