[GEM-dev] Way to get gemframebuffer back onto main memory for pix_ operations?

[B. Bogart]

Hi Jack,

The image I'm wanting to get from the framebuffer into pix_ domain is
not, and should never be, rendered to the gemwin.

Unless I can render stuff to the gemwin that we can't see in the gemwin,
I don't see how pix_snap can help.

I suppose a workaround could be using a gemwin sized black rect to break
the scene into two chunks, with two sets of render priorities, but that
seems like a terrible kluge.

I think a pix_snap for framebuffers is a useful idea. pix_tex2pix?

.b.


Jack wrote:

>> AFAIK pix_snap will only snap the gemwin, not the gemframebuffer itself?
>> Or is this wrong?
> Wrong, [pix_snap] snap 'things' rendered before it receive a bang. So
> you can see all your scene in the gemwin and snap only one part.
> This is the same with [gemframebuffer]. You can snap only one part of
> the [gemframebuffer], that depend of the order of the rendering. Then
> you don't snap 'things' in the gemwin.