lol. I am really retarded today. I redundantly restated what I said in
the subject, and then I spelled it wrong.
On 12/11/06, hank williams <[EMAIL PROTECTED]> wrote:
> Oh, by the way, this relates to the openItems property of the Treee class.
>
> Hank
>
> On 12/11/06, hank williams <[EMAIL PROTECTED]> wrote:
> > The documentation for the openItems field says that it is read/write
> > and that the default is NULL, which presumably means no items are
> > open. But it appears there is no way to set open items to closed.
> > Below is the setter function for openItems and the first thing it does
> > is say if the parameter is null just skip it. This would seem to
> > contradict the implication of the documentation which is that null is
> > a valid value.
> >
> > But even looking closer it appears you can only use this property to
> > *open* an item. I've heard of property names being descriptive, but
> > this is going a little too far! Setting the value only opens items!!!!
> > As far as I can see there is no way this setter will ever close an
> > item.
> >
> > I'd love to hear that this is a bug and its being fixed or that I am
> > missing something. It would also be great if there is a work around
> > since I cant figure out a good way to take a snapshot of the tree
> > state for saving.
> >
> > public function set openItems(value:Object):void
> > {
> > if (value != null)
> > {
> > for each (var item:* in value)
> > {
> > _openItems[itemToUID(item)] = item;
> > }
> > openItemsChanged = true;
> > invalidateProperties();
> > }
> > }
> >
> >
> > Hank
> >
>
