On Sat, 04 Nov 2000, Jon M. Taylor wrote:
> There may not always BE an offscreen part of the framebuffer on
> all targets. In particular, the targets which do not support one or more
> DirectBuffer mappings cannot use this method.
Hard to disagree with that. I guess my point is that somebody should be able
to know what is available and use it if it is.
>
> > I wrote a little demo (with minor changes to the fbdev
> > code) program that allowed me to draw offscreen (outside of the virtual area)
> > and then use ggiCopyBox to blit it to the viewable (virtual/pannable) area when
> > needed. What am I missing here?
>
> Did you try it on all targets?
No. Actually I've given it more thought and I appreciate the problems
associated with this more now. Perhaps, If we could make this memory
accessible through the normal api then it would be most useful. That way
anything that can be done to a displayable area can be done offscreen as well.
One way to do this might be to have a non-displayable, non-clippable frame.
This way the user would be able to blit to and from this area easily using
ggiCopyBox. All the user would need is a mechanism to know whether or not the
frame was displayable and it's dimensions. A call to ggiSetDisplayFrame with a
non-displayable frame would fail.
I could go on, but that's enough for now. Again, I'm not the expert here, but
take it for what it is.
--
Lee Brown Jr.
[EMAIL PROTECTED]
