>Can you use FB commands such as PLOT, COLOR, PEN in a gWorld or do you
>have to use the toolbox funcations (CALL LINETO etc). I've got one
>gWorld performing as it should, but when I get a gWorld copying to
>gWorld copying to the screen, I'm not getting a reliable copy - its
>frequently blank space. (Yes, I know I've probably got a bug somewhere).
>
>The FB manuals seem to imply that I shouldn't use FB commands in a
>gWorld and there isn't any examples where they are used, the toolbox
>commands being used instead.

I have not had any problem using the FB versions of these commands "in 
moderation" - probably because they _really_ just call the ToolBox - but 
I've gotten into the habit of using the "raw" ToolBox calls, so I may not 
have seen problems that could crop up. I'd say it's "safer" to use the 
ToolBox calls.

"Blank space" is usually due to not _having_ a gWorld you think you have, 
or not locking down the pixels before copying.

>Incidently when I create a gworld where is the memory coming from: the
>program partition (as per the GET INFO memory allocation) or the general
>free RAM in the system?

Right out of your program's partition. This is why it's so critical to 
either have _lots_ of room, or limit the color depth of your gWorlds. A 
program that runs fine on a 256-color monitor will quickly run out of 
memory if it's run in "millions" of colors, if the gWorlds are 
"defaulting" to the system color depth.

Bill