>Question:
> Since the scroll bar region is an add on to the rectangle defining the
>output window, when the GWorld is copied back to the screen is there also a
>"GWorld scroll bar region" that is also copied back?, and if so, why is that
>region getting junk drawn into it when the GWorld and output retangles are
>the same?  I would have thought that the GWorld rectangle doesn't have a
>scroll bar region and then when coping back with copibits, the scroll bar
>region of my regular output window shouldn't be effected.  But it does get
>effected!  Does the scroll bare region of the GWorld (if it exists) need to
>be "cleared" too.  This is rather confusing to me.
>
Hi Eric,

Sounds to me as if you need to check carefully what rects you are passing 
to FN NEWGWORLD and to COPYBITS. I suspect you are using a rect from your 
window record which apparently includes the scroll bar. You may need to 
alter this rect to eliminate the bar from both the gWorld and the drawing 
area. 

Unless you specifically want the image scaled, the rect you COPYBITS 
_from_ should be the same size as the rect you COPYBITS _to_. I have 
gotten some strange results by having just one pixel difference!--and for 
a large image it can really slow things down.

Wish I could give a more explicit description of how to fix your problem, 
but I'd almost bet it has to do with the rects. The existence of a scroll 
bar suggests to me that you are (or could be) using a gWorld larger than 
your viewing area, so the image can be scrolled. This makes sense, but 
further complicates understanding the rects involved, and could explain 
why you are getting interference with your scroll bar. Make sure the 
window rect you are COPYBITSing to doesn't cover the scroll bar, and make 
sure the rect you're copying from is the same size. Then it should work.

You might be interested in something I am doing, where I draw the visible 
portion of my image to the gWorld, copy it to the window, and set up a 
routine to complete the drawing (of the currently hidden parts) in the 
gWorld during null events. Easier said than done, but it's working great 
for me.

Hang in there. You'll get those atoms put together yet!
 0"0
 =J= a  y
  "