having trouble with gllight msg to jit.gl.sketch


    May 23 2007 | 8:55 am
    I've just updated to Jitter 1.6.3.rc1 . And a jit.gl.sketch seems not to respond to "reset, glenable lighting, glenable normalize, glenable light1, gllight light1 ambient 0. 0. 0. 1., gllight light1 specular 0. 0. 0. 1., gllight light1 diffuse 1. 1. 1. 1., gllight light1 position 1. 0. 0. 1.," type of messages ..(it was in Jitter 1.6.3.b2).
    Cheers
    Pascal

    • May 23 2007 | 8:14 am
      On May 23, 2007, at 1:55 AM, pascal wrote:
      > > I've just updated to Jitter 1.6.3.rc1 . And a jit.gl.sketch seems > not to respond to "reset, glenable lighting, glenable normalize, > glenable light1, gllight light1 ambient 0. 0. 0. 1., gllight light1 > specular 0. 0. 0. 1., gllight light1 diffuse 1. 1. 1. 1., gllight > light1 position 1. 0. 0. 1.," type of messages ..(it was in Jitter > 1.6.3.b2).
      As always, simple example, please?
      However I can clarify what's changed. In jit.gl.sketch, now to solve other state bleed through problems (a more common usage problem), we push the attribute stack, so if you make these changes in jit.gl.sketch, it won't affect other objects unless you use the drawobject sketch command, or use @immediate 1. If this is going to be a big problem for people, I suppose I could change it so that jit.gl.sketch has a @pushstate attribute (default on) which you and others who need the old behavior (@immediate 0 @pushstate 0) could have your cake and eat it too.
      -Joshua
    • May 23 2007 | 3:49 pm
      Sorry ..( for the example patch ..) ..I'll try with your indications Anyway..here is a very small example that was setting the parameters of light1 ( for ex ..) ..That did work in 1.6.3.b2 :
    • May 23 2007 | 4:05 pm
      On May 23, 2007, at 8:49 AM, pascal wrote:
      > > Sorry ..( for the example patch ..) ..I'll try with your > indications Anyway..here is a very small example that was setting > the parameters of light1 ( for ex ..) ..That did work in 1.6.3.b2 :
      Thanks, yes this clearly illustrates that you are exploiting the state bleeding properties of jit.gl.sketch (which is a problem for many other users). I've added a pushstate attribute to the next version (released shortly) you can set to 0 to get this state bleeding behavior back with @pushstate 0.
      -Joshua