Yep, I noticed this too... I think the value is just a pointer to the array. If this is so, it's probably impossible to access the array in js.
On 17/02/07, K-UDA <[EMAIL PROTECTED]> wrote:
Hello, Timo. I changed an input channel and tested it. The return value was the same. I duplicated a material object and tested it. The return value was different. You had better ask to Realsoft about it. I am sorry that I cannot help you. Best regards, K-UDA ----- Original Message ----- From: "Timo Mikkolainen" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, February 12, 2007 1:32 PM Subject: Re: Array handling in JS > In the linux version everything gets printed to stdout (commandline), > so I see everything properly. The actual popup is just an annoyance, > if anything I'd like to get rid of it. > When you look at the printed arrays, they look like pointers (as in, > their values are close to eachother and changing the vsl object's > input doesn't change the number). > > On 12/02/07, K-UDA <[EMAIL PROTECTED]> wrote: >> Hello, Timo. >> You are looking at the result of "line 554 print("");". >> Please watch "realsoft\logs\Realsoft 3D.log". >> Best regards, >> >> K-UDA >> ----- Original Message ----- >> From: "Timo Mikkolainen" <[EMAIL PROTECTED]> >> To: <[email protected]> >> Sent: Monday, February 12, 2007 9:42 AM >> Subject: Re: Array handling in JS >> >> >> > http://koti.welho.com/tmikkola/scripts/testMat.js >> > >> > See printObjectProperties(vslObject) >> > >> > On 11/02/07, Matthias Kappenberg <[EMAIL PROTECTED]> wrote: >> >> Hi Timo, >> >> >> >> is it possible to post a snippet? >> >> >> >> Matthias >> >> >> >> >> >> ----- Original Message ----- >> >> From: "Timo Mikkolainen" <[EMAIL PROTECTED]> >> >> To: <[email protected]> >> >> Sent: Saturday, February 10, 2007 12:47 PM >> >> Subject: Array handling in JS >> >> >> >> >> >> > I'm trying to read the input channels of a vsl object in JS, but I >> >> > don't know how to read the 'arrays' the JS functions return. I've >> >> > tried foo[0], foo.length, foo.head and whatnot; nothing works. The >> >> > arrays are returned by GetInputTypes(), GetInputChannels(), etc in >> >> > r3matprp.js. >> >> > >> >> >> > >> > >> > >
