BobVork

To put it simply, I'm trying to get the jit.gl.mesh object to output the openGL matrix. It should support the matrixoutput flag, but nothing happens when I set it. I tried banging the meh object manually, I tried automatic 0, however, nothing comes out either on of the outlets.

I couldn't find anything related to this on the forums, so I suppose I'm doing something wrong.

For the record: I'm using Mac OS X, (10.4.8),

and tried both jitter 1.5.2 and 1.6.3 b2.

To put it simply, I'm trying to get the jit.gl.mesh object to output the openGL matrix. It should support the matrixoutput flag, but nothing happens when I set it. I tried banging the meh object manually, I tried automatic 0, however, nothing comes out either on of the outlets. 

I couldn't find anything related to this on the forums, so I suppose I'm doing something wrong. 

For the record: I'm using Mac OS X, (10.4.8),
and tried both jitter 1.5.2 and 1.6.3 b2.


jit-gl-mesh-and-matrixoutput

I can't see the logic in this either. I made an example patch for you:

It probably never supported this feature in the first place, so don't

bang your head too hard trying. All jit.gl.* objects inherit the

matrixoutput attribute by fact of being jit.gl objects. There are a

few that don't actually do anything when this is set, jit.gl.mesh

apparently being among them. I don't think jit.gl.mesh not supporting

this is such a big deal. It only draws data that you feed it. You

can pack that data into 1 big multiplane matrix yourself if you need

It probably never supported this feature in the first place, so don't
bang your head too hard trying.  All jit.gl.* objects inherit the
matrixoutput attribute by fact of being jit.gl objects.  There are a
few that don't actually do anything when this is set, jit.gl.mesh
apparently being among them.  I don't think jit.gl.mesh not supporting
this is such a big deal.  It only draws data that you feed it.  You
can pack that data into 1 big multiplane matrix yourself if you need
it that way.

It's true that I'm feeding the data myself, but the advantage of the mesh object is that it supports some more advanced stuff like rotation that are a bit harder to do manually.

Anyway, thanks for the reply. I already was afraid that it simply didnt support matrixoutput.

Quote: wesley.hoke@gmail.com wrote on Wed, 24 January 2007 11:34

----------------------------------------------------

> It probably never supported this feature in the first place, so don't

> bang your head too hard trying. All jit.gl.* objects inherit the

> matrixoutput attribute by fact of being jit.gl objects. There are a

> few that don't actually do anything when this is set, jit.gl.mesh

> apparently being among them. I don't think jit.gl.mesh not supporting

> this is such a big deal. It only draws data that you feed it. You

> can pack that data into 1 big multiplane matrix yourself if you need

Okay.. so is there a way for users to find out which gl objects support which messages?

Quote: wesley.hoke@gmail.com wrote on Wed, 24 January 2007 11:34
----------------------------------------------------
> It probably never supported this feature in the first place, so don't
> bang your head too hard trying.  All jit.gl.* objects inherit the
> matrixoutput attribute by fact of being jit.gl objects.  There are a
> few that don't actually do anything when this is set, jit.gl.mesh
> apparently being among them.  I don't think jit.gl.mesh not supporting
> this is such a big deal.  It only draws data that you feed it.  You
> can pack that data into 1 big multiplane matrix yourself if you need
> it that way.
>
> HTH,
> wes
>
----------------------------------------------------

>>Okay.. so is there a way for users to find out which gl objects 

Unfortunately, we don't maintain a secret list anywhere (except maybe 

inside of JKC's brain) of what objects support what messages. For the 

most part, lack of support for GL features in specific instances is due 

to these features not really making sense for a particular object. This 

is certainly the case with jit.gl.mesh's matrixoutput attribute, since 

it really just provides a display for whatever matrix data is passed in, 

as well as jit.gl.sketch, which is a lower level interface to OpenGL.

At some point, a diligent user might take it upon his/herself to, say, 

write all this up on Vade's wiki, but for now the best way to learn 

about peculiar issues is to do searches of the forum archives when you 

>>Okay.. so is there a way for users to find out which gl objects 
support which messages?

Unfortunately, we don't maintain a secret list anywhere (except maybe 
inside of JKC's brain) of what objects support what messages.  For the 
most part, lack of support for GL features in specific instances is due 
to these features not really making sense for a particular object.  This 
is certainly the case with jit.gl.mesh's matrixoutput attribute, since 
it really just provides a display for whatever matrix data is passed in, 
as well as jit.gl.sketch, which is a lower level interface to OpenGL. 

At some point, a diligent user might take it upon his/herself to, say, 
write all this up on Vade's wiki, but for now the best way to learn 
about peculiar issues is to do searches of the forum archives when you 
come across something odd. 

Jit.gl.mesh and matrixoutput