On 12/12/06, Michael Schmalle <[EMAIL PROTECTED]> wrote:
> And since it is a property that can be read and written we should be able to set the list of which items are open and which are closed. What are you talking about here? > If they intended to make it work such that setting openItems just adds to a list of open items then they should have made it a function and not property. I didn't say this;
I may have been reading into your note because this is exactly what setting openItems does. If you look at the code I posted in the other thread, you will see that nothing is ever removed. If you set openItems it just adds the items you set to the list of open items. The only way to start fresh is to close them using the expandItems function. I said, you can retrieve the list of open items, run a check on whcih you
want closed, pop them out and reset the property by setting it to the new popped list. Which is now minus the items you want closed and they will be closed on the next commitProperties() pass. Thus, using the property to set a new state of opendItems.
Yeah, but the code doesnt work this way.
Properties reflect state. Yeah, and they also set state. Which in this case you are setting the new state of openItems by taking out items of the open list that you want closed. Maybe were talking about two different things here.
I think we were missunderstanding each other. My complaint is that it doesnt work the way that you are saying. If it worked that way I would be fine. Regards Hank
