[GEM-dev] Re: [PD] GEM separator / pix_separator

[B. Bogart]

Hi Sara and Johannes,

Johannes, I'm testing your texcoords changes in CVS and things are
looking pretty stable, PD has been using 861.2MB for over 24 hours and
the patch has been running for 420:00.00 (hours?) of CPU time.

Sara, maybe you can get a more recent build of Gem for OSX.

Can you send a test patch of your [separator] bug? I might be seeing the
same thing, but its hard to tell since I'm also dynamically sorting the
gemhead render order...

.b.

sara kolster wrote:
> Hi all,
>
> When using [separator] or [pix_separator], GEM displays the last created
> [separator] chain in the foreground of GEMwin. Is there a possibility of
> giving something like a set-message (used to set the render order of
> gemhead) to give a order of rendering when using separator?
>
> Thanks a lot,
>
> Sara
>
> chris clepper wrote:
>
>> On 3/16/06, *sara kolster* <sara at x-i.net <mailto:sara at x-i.net>> wrote:
>>
>>     Hi Ben,
>>
>>     Thanks for your help. When I open the patch and turn rendering on, my
>>     terminal keeps spitting out the following message:
>>
>>     /*separator : state->numTexCoords 4 != m_state.numTexCoords 0
>>
>>
>> You might have a separator object before a pix_texture which triggers
>> that message.  What it really means is that your patch is leaking
>> memory and will eat all of your RAM soon.
>>
>> cgc
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> PD-list at iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> http://lists.puredata.info/listinfo/pd-list
>>
>
>
>
>
>
>
> _______________________________________________
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20060323/11b72fc6/attachment.pgp>