Task-number: QTBUG-84469
Change-Id: I9109f92d059fd4152aee1f37597c5564d477fbf9
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

This is required to remove the ; from the macro with Qt 6.

Task-number: QTBUG-82978
Change-Id: I56268bc09fe861effc514acb4033bf8873873ab0
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>

This enables other modules depending on quickcontrols and declarative
to resolve their conflicts.

Change-Id: Iea28fa75157034d85dc24f44491ca986902db547
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

Change-Id: I3022d2eabeef6d387135427b553de8a6d80dff13

The previous binding was not getting re-evaluated when the model was
being reset or when rows were been inserted or removed.
Here we use a counter variable, whose value change will force the
evaluation of the binding.

Fixes: QTBUG-53097
Change-Id: I76afebbda78ab477cf65631337a8bad51ca5428d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

It is being deprecated. Amends
d1697d81866abaf217b6647b0f42a13fa974636b.

Change-Id: I7ec2e8d5d07b86eebeb9e16c35f70e3c93a4b037
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>

Use correct (i.e large enough distance) to ensure the current index
changes.

Fixes: QTBUG-80152
Change-Id: I26873e83fbd520965495104177ba09a38f566257
Reviewed-by: Liang Qi <liang.qi@qt.io>

 Conflicts:
	.qmake.conf

Change-Id: Ide73d291e885a0455765263716ea2b972d7ae62b

The decision to store the original QModelIndex as a role has the
unfortunate consequence that we need to emit the dataChanged() signal
whenever its value change. The previous implementation of the "move
rows" operation failed in delivering this update in most cases.

While addressing that, this commit also fixes some similar issues with
the HasChildren role not being notified in certain scenarios.

Also, when the last child of an expanded item gets moved away and later
placed back in the original position, the item should not remember its
expanded state, but rather accept the children while staying collapsed.

Last but not least, it's important that the endMoveRows() protected
method is called *after* the original tree model has completed its
movement, because otherwise its elements might be accessed while in the
wrong state.
Similarly, we don't want the dataChanged() signals to be emitted while
rows are moved or removed; we queue up these events and fire them only
after the item indexes have settled.

Fixes: QTBUG-59606
Change-Id: Ib981c912ea19908e1283cc463331c3053d4d6e7d
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>