[GEM-dev] 2textures + gemframebuffer

cyrille henry cyrille.henry at la-kitchen.fr
Mon Mar 31 17:43:12 CEST 2008


yes, you're right, pix_set is better than pix_image + a dummy image.
but pix_set dimention can not be changed. so pix_resize is maybe even better.

i just update the gem exemple in order to use pix_set.

cyrille

Jack a écrit :
> I don't know if i understand all, but why don't use [pix set 512 512] 
> (with a gemframebuffer dim 512 512) instead of [pix_image] + [openpanel] 
> + … ?
> if [pix_set] could accept a message like |dimen X Y(, it would be nice.
> See patch attach.
> But i agree, an automatic method would be great (without pix_image or 
> pix_set).
> ++
> 
> Jack
> 
> 
> 
> Le 31 mars 08 à 13:45, cyrille henry a écrit :
> 
>>
>>
>> IOhannes m zmoelnig a écrit :
>>> IOhannes m zmoelnig wrote:
>>>>
>>>> so is it this what you had in mind? (using the texture-info of
>>>> [gemframebuffer] and a [pix_texture] to setup the texcoords correctly)
>> well.
>> in fact, it should work without the connection from the gemframbuffer 
>> to the pix_texture.
>> it does not, because of the multitexture bug. (see chris answer from 
>> 11/11/2007)
>>
>> but yes, your solution is great. and work when the 3 gemframbuffer are 
>> the same size.
>> unfortunatly, it's not possible to use thid for the exemple 06, as the 
>> last part of the rendering does not use frambuffer.
>>
>> cyrille
>>
>>
>>
>>
>>>>
>>>>
>>> oops, i now see that i have forgotten the attachment...sorry
>>>
>>>
>>> fmga,sdr
>>> IOhannes
>>>
>>
>> _______________________________________________
>> GEM-dev mailing list
>> GEM-dev at iem.at
>> http://lists.puredata.info/listinfo/gem-dev
> 




More information about the GEM-dev mailing list