Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-26 Thread cyrille henry
Claude Heiland-Allen a écrit : PSPunch wrote: I thought the dgemhead and repeat methods were just a matter of preference. If one is trendy and the other out dated, I guess I can just drop the one said to be less efficient. as far as I understand it, there are now 3 methods: 1: double

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread cyrille henry
PSPunch a écrit : The attached example works great. Going slightly off topic, if I am not mistaken, the rectangle on the top of the cube is rendered twice as seen in some other cases I've seen in patches using the dual gemhead technique. Disabling the [gemhead] by sending it a 0 seems

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread PSPunch
Hi cyrille what is the problem with : [loadbang] | [0 Yes, that will work. For example, [gemwin] starts out disabled and without the window showing, or say, [metro] being off by default. It is reasonable that [gemhead] is on by default, but being able to state in the object itself,

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread zmoelnig
Quoting PSPunch [EMAIL PROTECTED]: Yes, that will work. For example, [gemwin] starts out disabled and without the window showing, or say, [metro] being off by default. It is reasonable that [gemhead] is on by default, but being able to state in the object itself, self concluding, that it is

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread Frank Barknecht
Hallo, [EMAIL PROTECTED] hat gesagt: // [EMAIL PROTECTED] wrote: however, since i am currently planning to replace [gemhead] with an abstraction, which would allow you define the behaviour as you like it, i don't want to add complexity to the current implementation. don't know when this

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread cyrille henry
Frank Barknecht a écrit : Hallo, [EMAIL PROTECTED] hat gesagt: // [EMAIL PROTECTED] wrote: however, since i am currently planning to replace [gemhead] with an abstraction, which would allow you define the behaviour as you like it, i don't want to add complexity to the current

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread Frank Barknecht
Hallo, cyrille henry hat gesagt: // cyrille henry wrote: the best would be not to use the double gemhead trick, but the repeat (or until) trick instead : it's faster, and don't have this problem, so i think it's easier to understand. Yes: Everyone is on the latest Gem should use gemlist

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread cyrille henry
Jack a écrit : We are talking about [gemlist]. Is there a difference with [any] ? gemlist is a gem object, that work only with gem data any is an (iem) external that work with any data. you can replace gemlist with any in your patch, but gemlist should work without any dependency (except

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread Jack
OK, thank you for the precisions. ++ Jack Le 25 août 08 à 19:32, cyrille henry a écrit : Jack a écrit : We are talking about [gemlist]. Is there a difference with [any] ? gemlist is a gem object, that work only with gem data any is an (iem) external that work with any data. you can

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread PSPunch
Thanks all for the ideas. I thought the dgemhead and repeat methods were just a matter of preference. If one is trendy and the other out dated, I guess I can just drop the one said to be less efficient. -- David Shimamoto ___ Pd-list@iem.at

Re: [PD] Disabling a [gemhead] by default (Re: Writing texture to different sides of cube in GEM)

2008-08-25 Thread Claude Heiland-Allen
PSPunch wrote: I thought the dgemhead and repeat methods were just a matter of preference. If one is trendy and the other out dated, I guess I can just drop the one said to be less efficient. as far as I understand it, there are now 3 methods: 1: double [gemhead] 2: [repeat] 3: [until] with