On Wednesday, 2. May 2012 01:28:19 Chris Muller wrote:
> Ensuring your drawOn: is fast is crucial for good frame-rate.
> 
> Try profiling all processes, that should reveal something..

Thanks. Did that (kind of). I appears that I had some kind of layout loop, 
where an owner morph rearranges its children in a self written #doLayoutIn: 
method. However the child morphs seem to issue a #layoutChanged when moved. 

The thing is: I have to scroll an infinite horizontal "ribbon", and I am sure 
that changed horizontal positions of submorphs do not cause any parent to 
require re-layouting (other than clipping). 

I ended up overwriting #position: in the child morphs, such that 
#layoutChanged is no longer called and I let the parent rearrange its 
submorphs in a #timeChanged method rather than #doLayout.

But I am still not happy with  the code. You don't just move submorphs around 
with the usual #left: #right methods and friends when a parent morph enforces 
a particular layout, right?


Reply via email to