On Thu, 10 Oct 2002 21:56:29 -0500 Daniel Joyce =
<daniel.a.joyce at worldnet.att.net> wrote:
>Someone was mentioning that clipping and scrolling could be slow on=20
>large lists because the scrollpanes still redraw all their internal=20
>morphs, and then just clip down...
>
>Well, the morphs themselves have obscene, Morphic's layout has=20
>definitely improved, buut, there are some insane internals...
>
>List item morphs, for example, have their rightmost xbounds at 9999!
>
>And this supposedly set from somewhere inside when they recompute =
their=20
>bounds. Shouldn't a list item set it's right bounds at the edge of=20
>morph that contains it?

That means
a) it need to know what list it is in
b) it needs to change whenever the list changes

>I'm trying to track down where this weirdness comes from...

from PluggableListMorph>>list:
...
	morphList do: [:m | m bounds: (loc extent: 9999 at h).  loc _ loc + =
(0 at h)].
...

Beyond obscene and insane, what other problems do you see with this?

Cheers,
Bob