outlet_rm: wasn't in table & chainapply errors

Oct 18, 2010 at 1:22pm

outlet_rm: wasn't in table & chainapply errors

What do those errors mean (and BTW what does a blue background in Max’ window mean?)

I found this topic (and others)
http://cycling74.com/forums/topic.php?id=20476
but it didn’t help much.

In my case, I have those messages when dynamically deleting buffers. Depending on the way I use my patch, I got a outlet_rm or a chainapply error.

It’s a bit difficult now to do a reduced patch (and I don’t have much time), but if somebody @ c74 needs one, I ‘ll do my best.

Latests Max and OSX.

#52806
Oct 27, 2010 at 4:01pm

Nobody seemed to care, so I started a mail to support@cycling.com and while preparing a patch for them, I had an idea:

those errors a sent to the Max window when an object associated with a pvar is deleted (thru scripting but also by hand in edit mode).

The soluition is to first send a setname message to the pvar instance before deleting the object.

Try in pvar.maxhelp: click on setname funny, go in Edit mode and delete the green number box, you’ll get a “outlet_rm: wasn’t in table” error.

p

#189845

You must be logged in to reply to this topic.