home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!ira.uka.de!rz.uni-karlsruhe.de!rz.uni-karlsruhe.de!ry41
- From: ry41@rz.uni-karlsruhe.de (Bernhard Moellemann)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: LockIBase
- Date: 23 Dec 1992 12:20:03 GMT
- Organization: University of Karlsruhe, Germany
- Lines: 31
- Distribution: comp
- Message-ID: <1h9lhjINNk0p@nz12.rz.uni-karlsruhe.de>
- References: <JTP.92Dec23025528@laphroaig.cs.hut.fi>
- NNTP-Posting-Host: tp72.rz.uni-karlsruhe.de
- MIME-Version: 1.0
- Content-Type: text/plain; charset=ISO-8859-1
- Content-Transfer-Encoding: 8bit
-
- Keywords:
-
- In article <JTP.92Dec23025528@laphroaig.cs.hut.fi>, jtp@cs.hut.fi (Jukka Partanen) writes:
-
- > What's the correct locking protocol if one wants to find a
- > particular screen, and then do something with it? The RKM
- > states that one shouldn't call any high level calls while
- > holding the IntuitionBase lock.
-
- The _correct_ protocol is:
-
- if ( scr=LockPubScreen(name) ) {
- DoStuff(scr);
- UnLockPubScreen(NULL,scr);
- }
-
- If it is no public screen rethink your strategy. There is no safe way to
- play around with a screen that is not yours. So there is _no_ "correct
- locking protocol".
-
- > [...] Isn't there a better way to
- > make sure that a particular screen (not necessarily a public
- > screen) isn't closed while I'm referencing it?
-
- Simply don't touch other peoples screens. Then all is easy and clean.
-
- --
- Bernhard M÷llemann <spare space> Chairman of the Nessy-Fan-Club //
- internet=zza@rz.uni-karlsruhe.de <space> FIDO=2:241/7506.42 IRC=ZZA //
- nessynet=008 Lifenet=77:7700/11.42 greetings to my Marsupilami \\ //
- 2000/500 Technical Reference Manual: "A1000, the original Amiga" \X/
-