Yes, the problem was that WorldState>>#runStepMethodsIn: processed only 1 deferred UI message per cycle, which made the kinect server update really slow because I wrapped all ui changes inside a WorldState>>#addDeferredUIMessage:.
I added the issue 3562<http://code.google.com/p/pharo/issues/detail?id=3562> with a proposed fix I took from the Etoys image. I now realize I didn't mentioned the connection with Kinect in the issue description... my bad. The issue is closed now so it seems the fix was accepted :) Cheers! Richo On Sun, Feb 6, 2011 at 6:42 PM, Stéphane Ducasse <[email protected]>wrote: > Hi ricardo > > you mentioned that pharo is really slow for using kinect and can you tell > us more? > > TX > Stef
