ListView:
As delegates are instantiated in ListView, they are parented to views
contentItem. This is now explicitly stated in the documentation.
Component:
Components are not derived from Items, so they cannot hook to anchors.
Task-number: QTBUG-24822
Change-Id: I09e04fbcc01b2858c039d22f9600ef201a9a91ab
Reviewed-by: Topi Reiniƶ <topi.reinio@digia.com>
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
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
The list view itself is a focus scope (see \l{Keyboard Focus in Qt Quick} for more details).
Delegates are instantiated as needed and may be destroyed at any time.
+ They are parented to ListView's \l {Flickable::contentItem}{contentItem}, not to the view itself.
State should \e never be stored in a delegate.
ListView attaches a number of properties to the root item of the delegate, for example
alignment of items.
\note Delegates are instantiated as needed and may be destroyed at any time.
+ They are parented to ListView's \l {Flickable::contentItem}{contentItem}, not to the view itself.
State should \e never be stored in a delegate.
*/
/*!