Xref: utzoo comp.sys.amiga.tech:831 comp.sys.amiga:19340
Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: DiskObject
Message-ID: <54486@sun.uucp>
Date: 25 May 88 17:39:22 GMT
References: <4725@watdcsu.waterloo.edu>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Distribution: na
Organization: Sun Microsystems, Mountain View
Lines: 29

In article <4725@watdcsu.waterloo.edu> (Dave Oh) writes:
> If I were to AllocRemember the DiskObect into CHIP ram, would the
> subsequent Gadgets and Images be located there too? 

No. The reason being that the other objects are pointed to by this
structure and haven't been allocated at all! In your example :
       
>  dobj = AllocRemember(&myRememberList,sizeof(struct DiskObject),          
>         MEMF_CHIP|MEMF_CLEAR);
>If I had this, would my dobj->do_Gadget.GadgetRender image be in Chip ram too?

Now you would have to follow that with an 
   dobj->do_Gadget.GadgetRender = AllocRemember(&mrl,sizeof(struct Image),
					MEMF_CHIP+MEMF_CLEAR);
(assuming you will have images for your icons.)

Also you don't have to put gadget or disk object structures in chip ram,
only the *image data* in image rendered gadgets. For for your typical gadget
that uses Images for rendering in the image structure only the 
ImageData pointer has to point to chip ram, everything else can be in
fast ram. All other types of gadgets can be completely in fast ram (this
includes borders and IntuiText etc). Basically, just remember your image
data has to be in chip ram, and that includes little images used for 
gadgets and the Bitmaps associated with windows and screens. 


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.