Hello Jonas,
you are right, I have overlooked the invocation CountViews. It should also be invoked in context of the affected Outline object.
Concerning the difference, the methods provided by Outline view do limit to views belonging to the affected Outline only. A view is considered as belonging to an Outline if all following three conditions are true:
1. the view has the property Embedded set true
2. the view is arranged in front of the Outline view
3. there is no other Outline view separating the both. In such case the view would belong to the second Outline.
You use the Outline version of the methods (e.g. FindNextView) only if you want to restrict the search operation to views controlled by the Outline. This has no effect on the Add/Remove operations. To remove a view you do this always in context of the GUI component the view (and the Outline) belong to.
Technically, Outline does not manage the associated views by itself. The views are managed by the GUI component only. Outline provides only a kind of technique to identify the views associated to it, to arrange and scroll the views. The views, however, continue belonging to the GUI component.
Concerning the observation in Variables window, this effect is known. The Variables window displays the contents stored in the memory associated to the property Embedded. The property Embedded, however, determines its contents dynamically from an internal viewState variable. Similar occurs to the property Visible or Enabled. We plan to modify this special behaviour in further versions.
Does it help you further?
Best regards
Paul Banach