Matthew Aidekman

I've run into enough trouble with jit.js.listener.bug that its time 

is there a way to call jit.print in js ? AND if not how do 

other people troubleshoot jit.js.listener bugs?

while I'm at it. is there a comprehensive list of jit.js 

keywords,methods, etc??? Allow me to humbly suggest that cycling 

include js.jit documentation into the javascript PDF. it may be 

redundant but one serves as an educational text, the other serves as 

a reference. I also seem to recall seeing Luke D. using MSP in JS at 

I've run into enough trouble with jit.js.listener.bug that its time  
to ask.

is there a way to call jit.print in js ?    AND     if not how do  
other people troubleshoot jit.js.listener bugs?

while I'm at it.  is there a comprehensive list of jit.js  
keywords,methods, etc???   Allow me to humbly suggest that cycling  
include js.jit documentation into the javascript PDF.     it may be  
redundant but one serves as an educational text, the other serves as  
a reference.  I also seem to recall seeing Luke D. using MSP in JS at  
AES.  Is that documented anywhere?


js-jit-print

Since this question involves a Jitter object, I'm going to move this thread to the Jitter topic, although I suppose it would be at home in the JavaScript topic as well. In the future, if the question regards jit.* something, and it's not jit.cellblock, the Jitter topic/list is the more appropriate place for this question. I know old habits are hard to break, but topic segregation is useful, especially when someone is searching. Thanks.

BTW, since I'll be the first to admit that I'm not omniscient when it comes to topic segregation, if anyone ever feels like one of these topic moves is incorrect, please don't hesitate to pipe up with an explanation as to why the move was wrong. If it's prima facie I'll move it back.

https://cycling74.com/mailman/listinfo/jitter

Absolutely totally my fault.
happy new year all.
-matt
jitter mailing list
jitter@cycling74.com
https://cycling74.com/mailman/listinfo/jitter


Doesn't something like the following work?

var myprint = new JitterObject("jit.print");

If the above doesn't make sense to you, please take some time to re- 

read the JS Jitter tutorials and examples.

There might be an issue with a null second arg to matrixcalc, in 

which case, you can just pass in a dummy matrix, or the input matrix 

name, since jit.print ignores any output matrix anyway.

function jit_matrix(mname)
{
	myprint.matrixcalc(mname,null);
}

If the above doesn't make sense to you, please take some time to re- 
read the JS Jitter tutorials and examples.

There might be an issue with a null second arg to matrixcalc, in  
which case, you can just pass in a dummy matrix, or the input matrix  
name, since jit.print ignores any output matrix anyway.

-Joshua
jitter mailing list
jitter@cycling74.com
https://cycling74.com/mailman/listinfo/jitter


> Doesn't something like the following work?

> var myprint = new JitterObject("jit.print");

> re-read the JS Jitter tutorials and examples.

> .. issue w/ null second arg to matrixcalc....., ... pass in a dummy 

Thanks for the reply Joshua. No luck though. I troubleshot my 

problem a differnt way so this is not urgent. I did not mean to 

imply that I was unwilling to read the tutorial.

sing anything else simply yeilds no result and no error.

var colors = new JitterMatrix(3,"float32",5,1);

var dummy = new JitterMatrix(3,"float32",5,1);

    colors.setcell(i,0,"plane",0,"val",0)

    colors.setcell(i,0,"plane",1,"val",.2)

    colors.setcell(i,0,"plane",2,"val",.4)

function printerer(mname)// maybe printer is a keyword?

    myprint.matrixcalc(mname,dummy.name);

> Doesn't something like the following work?
> var myprint = new JitterObject("jit.print");
> function jit_matrix(mname)
> {myprint.matrixcalc(mname,null);}
>
> re-read the JS Jitter tutorials and examples.
> .. issue w/ null second arg to matrixcalc....., ... pass in a dummy  
> matrix, .......
> -Joshua

Thanks for the reply Joshua.  No luck though. I troubleshot my  
problem a differnt way so this is not urgent.  I did not mean to  
imply that I was unwilling to read the tutorial.

using null quits max
sing anything else simply yeilds no result and no error.

I tried your code and the following
var myprint = null;
var myprint = new JitterObject("jit.print");
var colors = null;
var colors = new JitterMatrix(3,"float32",5,1);
var dummy = null;
var dummy = new JitterMatrix(3,"float32",5,1);
colors.name = "fleh";
for (var i = 0;i
	{
	colors.setcell(i,0,"plane",0,"val",0)
	colors.setcell(i,0,"plane",1,"val",.2)
	colors.setcell(i,0,"plane",2,"val",.4)
	}

function printerer(mname)// maybe printer is a keyword?
{
	myprint.matrixcalc(mname,dummy.name);
}


On Jan 2, 2007, at 7:13 PM, matthew aidekman wrote:

> hanks for the reply Joshua. No luck though. I troubleshot my 

> problem a differnt way so this is not urgent. I did not mean to 

> imply that I was unwilling to read the tutorial.

> sing anything else simply yeilds no result and no error.

Aha. Upon initial glance I saw no reason why it shouldn't work. On 

closer inspection, I noticed that jit.print's matrix_calc erroneously 

assumes that a matrix and not a linked list will be passed into the 

object, and will only work as called from C. SDK users are 

recommended to *not* follow jit.print's example. Authored long before 

JS/Java support and barely touched since.

So, we can remedy in the future, but for now, you'll need to iterate 

across the matrix by hand to simulate the functionality of jit.print 

on your own. Thanks for pointing this out, and sorry or the 

On Jan 2, 2007, at 7:13 PM, matthew aidekman wrote:
> hanks for the reply Joshua.  No luck though. I troubleshot my  
> problem a differnt way so this is not urgent.  I did not mean to  
> imply that I was unwilling to read the tutorial.
>
> using null quits max
> sing anything else simply yeilds no result and no error.

Aha. Upon initial glance I saw no reason why it shouldn't work. On  
closer inspection, I noticed that jit.print's matrix_calc erroneously  
assumes that a matrix and not a linked list will be passed into the  
object, and will only work as called from C. SDK users are  
recommended to *not* follow jit.print's example. Authored long before  
JS/Java support and barely touched since.

So, we can remedy in the future, but for now, you'll need to iterate  
across the matrix by hand to simulate the functionality of jit.print  
on your own. Thanks for pointing this out, and sorry or the  
misinformation and inconvenience.

it seems that the problem still persists. Any chance to get this fixed?

js.jit.print