Aug 6, 2006 at 3:34pm
Can anybody explain what exactly causes the following bug and how to prevent this from happening?
I make a js-file containing only this line:
this.patcher.newobject(“number”, 200, 260, 35, 9);
..and then I connect another object to this one.
I then save the file, re-open it, and discover that the connection-cord has been replaced…
This is on a windowsXP system with max 4.5.5
Aug 13, 2006 at 8:47am
Okay, here’s another one:
I create a js-object containing only this line:
unpack=this.patcher.newdefault(272,90,”unpack”, “0.”, “0.”, “0.”);
I save it, so an unpack-object is made. I then test it and see that this unpack object just won’t work. It doesn’t generate any output upon receiving a list.
But if I retype (part of) this unpack-object, it suddenly starts behaving the way it should. The one question arising from all this is “Why?!?”
Is it just me or has Max gone crazy?
Aug 13, 2006 at 9:43am
> I create a js-object containing only this line:
it probably does output a list, if you send it a list of symbols,
this.patcher.newdefault(272,90,”unpack”, “f”, “f”, “f”);
also, i guess you should better put your line inside a function, and
Aug 13, 2006 at 12:11pm
Great, it works like a charm now!
…even though this connection-thing (described in the first message) is still bugging me.
Aug 13, 2006 at 12:44pm
> …even though this connection-thing (described in the first
as i said, it’s _not_ recommended to have a scripting command in the
stick it in a function definition and call it _once_. make your
You must be logged in to reply to this topic.