because it is defined inside a \c Component. The component encapsulates the
QML types within, as if they were defined in a separate QML
file, and is not loaded until requested (in this case, by the
- two \l Loader objects).
+ two \l Loader objects). Because Component is not derived from Item, you cannot
+ anchor anything to it.
Defining a \c Component is similar to defining a \l {QML Document}{QML document}.
- A QML document has a single top-level item that defines the behaviors and
- properties of that component, and cannot define properties or behaviors outside
+ A QML document has a single top-level item that defines the behavior and
+ properties of that component, and cannot define properties or behavior outside
of that top-level item. In the same way, a \c Component definition contains a single
top level item (which in the above example is a \l Rectangle) and cannot define any
data outside of this item, with the exception of an \e id (which in the above example