This content has been marked as final. Show 3 replies
> Did anyone know that MM correct this problem or any workarounds for that?
Yes - with MX2004 a new function was added to fix the issue you observe.
Check the docs for 'makeScriptedSprite()'
1). channel(1).makeScriptedSprite() / removeScriptedSprite()
2). _movie.puppetSprite(1, true / false)
3). sprite(1).puppet = true / false
and always had same results :(
Changing any sprite propertys (member, loc, rect, etc.) from lingo level when sprite is puppet and after that restoring it's controll to score (de-puppet sprites ) work fine...
...but after any access to scriptInstanceList (add/remove behaviour to sprite scriptInstanceList when is puppet) and after that restore score controll (set scriptInstanceList to empty list and de-puppet sprite) - all score predefined behaviours fail...
> 1). channel(1).makeScriptedSprite() / removeScriptedSprite()
> 2). _movie.puppetSprite(1, true / false)
> 3). sprite(1).puppet = true / false
I'm not sure what you're saying, but if you use
make/removeScriptedSprite() you shouldn't use touch either the 'puppet'
or 'scriptInstanceList' properties of your sprite