Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!usc!samsung!uakari.primate.wisc.edu!ark1!nems!mimsy!mojo!russotto
From: russotto@eng.umd.edu (Matthew T. Russotto)
Newsgroups: comp.sys.mac.programmer,aus.mac
Subject: Re: Danger Will Robinson, traps for young player.
Message-ID: <1990Aug20.144229.2341@eng.umd.edu>
Date: 20 Aug 90 14:42:29 GMT
References: <11591@wehi.dn.mu.oz> <1990Aug20.033702.5883@cs.uow.edu.au>
Sender: news@eng.umd.edu (The News System)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 17

In article <1990Aug20.033702.5883@cs.uow.edu.au> stephen@cs.uow.edu.au (The Mighty Ogbo) writes:
>JON@wehi.dn.mu.oz (Jon Eaves) writes:
>
>>I want to extract the UserName from the Chooser. No problems, just use 
>>tempHandle = GetString(CHOOSERNAME), then how do I get the "string" from
>>the tempHandle.  The process I was using was
>
>I believe a call to DetachResource() would be useful here. It unlinks
>the information in memory from the resource itself. This way you can
>go and play with the memory copy quite happily and not accidently screw
>your resource.

I think it would be bad to call DetachResource on a shared resource-- other
applications using the handle might get messed up.
--
Matthew T. Russotto	russotto@eng.umd.edu	russotto@wam.umd.edu
][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions?