[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
The merge view works together with a group view that splits the data in a stream to multiple subviews, based on
a key index. Every group view requires a merge view to merge the many subviews back into a single view.
Typically the last view in a chain containing a group view is a merge view.
The merge view has no other responsibility then becoming the single last instance in the chain
to which external listeners for updates can be attached to receive updates for the many subviews
that have this merge view as common child views.
The parent view of this view is generally the AddPropertyValueView that adds the grouped-by information
back into the data.
The following tables list the members exposed by the MergeView type.
Protected Fields
Name | Description | |
---|---|---|
![]() | parent |
Parent viewable to this view - directly accessible by subclasses.
(Inherited from ViewSupport.) |