On 8/7/16, 2:06 AM, "yishayw" <[email protected]> wrote:
>We have code that removes all elements in a container. It does something
>like
>
>while (container.numElements) {container.removeElementAt(0)}
>
>The problem was that ContainerBase.removeElementAt(0) actually did
>ContainerBase.contentView.removeElementAt(0) while container.numElements
>was
>returning ContainerBase.numElements, not
>ContainerBase.contentView.numElements.
>
>I fixed that, but I was wondering if ContainerBase.$numElements should be
>fixed as well. I'm not sure exactly what the $ methods do in
>ContainerBase.
>Are they meant to insure the contentview is not used as a delegate?
$numElements looks ok to me. The $ functions are used by ContainerViews
to add elements to the "chrome" of the container itself, since addElement
otherwise adds it to the contentView. Scrollbars, TitleBars and stuff
like that get added by the ContainerViews outside of the contentView.
Thanks for fixing the bug.
-Alex
