jsarguments not fully accessible when 'defining' js-file as object
Hi everyone,
when defining a custom object name as v8 or js with a specific JavaScript-file, using the following line in an objectmappings.txt-file like so:
max define jsargs_parse v8 @filename jsargs_parse.js;the object is correctly created as an instance of v8 with the file loaded.
However, the jsarguments skip the first/initial argument in this case, which does not happen when the object is instantiated as v8 or js manually.
Seeing that this is likely not intended and since, of course, the first argument needs to be present for any other argument to be interpreted, I assume this is a bug — unless there is a native way to fetch the first argument, that I am unaware of.
Can anyone shed some light on this?
Thanks!

Max Patch
Copy patch and select New From Clipboard in Max.