Guillaume Evrard

i'm on a quiet complex patch and i'm starting to get these error when using vst~ inside a poly~ :

fseventwatcher: doesn't understand "finit"

"finit" is a message i'm sending to the patcher inside the poly~.

it looks like a memory corruption, when i double click on my poly~, it opens nothing, or a different patcher that have nothing to see with the content of the poly~ (like an abstraction located in another patch), it has even open the object_palette object in a new window (with a title), which is an internal object to max...

i'll investigate on this a bit, but i'm not sure to have a method to reproduce it...

fseventwatcher: doesn't understand "finit"
typedmess: finit: corrupt object
typedmess: finit: corrupt object
getfn (vis): corrupt object
zgetfn (setname): corrupt object

max-5-1-6-really-strange-behavior

sending "dispose" to thispatcher located inside a poly~ is the worst idea you can have...

once you've done this, double-click on the poly~ to have the weird blue errors, or to open a random abstraction loaded in max.

i can anticipate a bit ej's reply : "dispose is evil". ;)

Max 5.1.6 really strange behavior