Doug Way wrote:

> Related to that, at some point it might be interesting to put a fancier
> algorithm in DamageRecorder>>recordInvalidRect: which determines whether
> damage rectangles should be combined together based on how large they are, how
> far apart they are, etc.

I once had an idea related to "hinting" morphs about redrawing. Hints about
how to invalidate/redraw would be invoked by calling other methods than
plain ol' invalidRect:. One such hinted method might do what you want. The
important part is that not all morphs would enforce the same invalidation
policy. For instance, your strategy seems to fit morphs of a certain nature,
like the Halo. Morphs with heavy animation, like bouncing atoms, might like
another one.

Henrik