Bert Freudenberg wrote:
Did you close everything in the world first (shift-click helps)?
Damn, that was it! Two class browsers and a workspace. Closed that, runs like hell. ;) Thanks for the hint, should have tried that, instead of diving into the morphic insides and checking message tallys.
It seems that the morph had higher priority in getting step method called (not drawOn - step), compared to the other morphs in the world, when it was grabbed. When it wasn't, the other morphs were getting the step calls and system was skipping the poor guy. Am I right, more or less?