This should give us more context when we finally do look at item containers and container generators.To support this diversion, I’m giving this “Items Control: A to Z” series a new subtitle of “(but not necessarily in order)”. Let’s just recap a couple of things before we get started…The following example demonstrates how easy it is to create observator collections.Out of the original list, a new list of view models will be built by filtering only the ones with a name starting with an "A" For more informations on what is supported and what is not, see the documentation.An Observable Collection is a dynamic collection of objects of a given type.Objects can be added, removed or be updated with an automatic notification of actions.
The new collections built this way will be automatically observable.Setting it like that does not make the List Box show the Name property of the data items in the Group Model List collection. You would instead have to set the List Box's Display Member Path property: | this answer edited Apr 8 '15 at answered Apr 8 '15 at Clemens 65k 8 49 94 Thanks! And they should have only one Children property that is observable collection of type Base Game Node but its item instance should be different as needed.You can define multiple templates provided they have something to distinguish, the type will be automatically chosen for the children of the node. And this process list is updated by a timer object which triggers the following code 10 times per second.