Be more strict about accessible text selection

Change-Id: I0eda4c29235035824105992f3db2d9a0c06dc6b5
Reviewed-by: Jan Arve Sæther <jan-arve.saether@digia.com>
Add more geometry properties to the Screen attached property

desktopAvailableHeight is useful for positioning windows, and
logicalPixelDensity is useful for ensuring that touch controls are
a reasonable size even on very high-resolution displays.

Change-Id: Id777caf6cef1df5bc01757605e3085151170760b
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
Doc: Remove "qmldemos" group

The group is a remnant of Qt Quick 1, and currently only contains 1
member. Move it to the "qtquickexamples" group.

Change-Id: I211b9b769274e139321760f4b52220449e03a6ad
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Doc: Fix example path for Qt Quick scenegraph examples

Base path (examples/quick) is now defined in qdocconf file, example
docs need to adjust their paths for \example command.

Change-Id: I18412c4adf73691903ee58c9a056b6a4998d4d6a
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Doc: Moved "QML Application Developer Resources" to qtdoc repository.

The guide is more relevant to Qt, not just Qt QML and Qt Quick. It
would need to include information about the tools and other Qt modules
which provide QML types.

Change-Id: I0cab0db015022dd27f08811a88ea4a6c3c6e917d
Reviewed-by: Sze Howe Koh <szehowe.koh@gmail.com>
Reviewed-by: Geir Vattekar <geir.vattekar@digia.com>
QQmlVMEGuard is not ok if one of the context engines is gone

Task-number: QTBUG-30632

Change-Id: Idff323f5b29688477e31030111d4f49f644115cd
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Don't crash if QQuickPath has less than 4 elements

When running the Qt Cinematic demo on Android, the assertion
ASSERT: "i >= 0 && i < elementCount()" in painting/qpainterpath.cpp
failed because of a zero default size at startup.

Change-Id: I2c46c43319cf71030cf03b1f7c6cdaec782ce11a
Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
TextEdit: Better support of QTextTable and inline images

Fix some issues with incremental updates found while
playing with the Quick Controls textedit demo.

 -Grouping text blocks into a single text node is fine as
long as it doesn't cross the boundary of a child frame
(e.g. a table), otherwise all that node logic collapses.

 -Text tables are hard to split in a sensible way, ensure
we treat them as one text node for the sake of simplicity.

 -Inline images can cause several text nodes to have the
same apparent start position. Beef up the rewinding logic
in markDirtyNodesForRange.

Change-Id: Ib4518bcd9303035fa00d9f4b16da7ca6c88e2313
Reviewed-by: Caroline Chao <caroline.chao@digia.com>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
Doc: Changed order of pages in QML reference.

New order:
    QML Syntax Basics
    QML Object Attributes
    Property Binding
    Signal and Handler Event System
    Integrating QML and JavaScript
    [etc.]

Change-Id: I19e6fc10e36963362dd862feeb697f942902aaac
Reviewed-by: Bea Lam <bea.lam@jollamobile.com>
QQuickScreen.name can change at runtime

It's generally a constant but the attached property doesn't always
have its QScreen at startup, so in practice every property needs a
notifier.  (Followup to Id777caf6cef1df5bc01757605e3085151170760b )

Change-Id: Ia3a321f98dc49b7e75f6eceb8f16b153c73a3134
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
QmlProfiler: Pixmap Cache

Change-Id: Ibc237bb162c24030438b89d54fa8802ee66b080a
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Fix MaskedMouseArea example

Task-number: QTBUG-30916

Change-Id: Icc73118f8d129b6c1ef285fd7a35f7a9a8e04391
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
Don't eat Back button in TextEdit

On Android, Key_Back is used to change to the previous state in-app,
as well as to exit the application. QTextControl does not react to the
back button, so it should not accept the event.

Task-number: QTBUG-30752
Change-Id: I010d36c93f14384b96fb0b2f0015c57a2a3d2497
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Added doc and test for active and requestActivate in QQuickWindow

Autotest is included.

Change-Id: I0f8614b502f1e51cab5612fee283c929e078108b
Reviewed-by: Gunnar Sletta <gunnar.sletta@digia.com>
Reviewed-by: Liang Qi <liang.qi@digia.com>
Protect against null item at QQuickItemView::destroyingItem

Change-Id: I92317d8f5a6d6f60160139f7486ffa8ec5985656
Reviewed-by: Alan Alpert <aalpert@blackberry.com>
Fix VS2010 compile warning

warning C4510: 'QQmlPrivate::RegisterCompositeType' : default constructor could not be generated

Task-number: QTBUG-30454
Change-Id: I16ec8995ac1df3c92353006473ca082c4ed4e5b7
Reviewed-by: Josh Faust <jfaust@suitabletech.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Elaborate on versioning docs

Task-number: QTBUG-30808
Change-Id: I1930bd91a6c2089047ac7e7d74da2c977c522e07
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
Document percieved memory leak

QJSEngine doesn't call collectGarbage upon deletion, because this
operation can be expensive and in most cases the JS engine is deleted
during application shutdown, when the memory can be deallocated cheaper.

This can lead to an apparent memory leak if multiple engines are created
and destroyed in the same process. Documenting how to avoid this.

Change-Id: Ie02cb8bedc8821e0bb04dfa52a5a2d65b4b085a3
Reviewed-by: Christopher Adams <chris.adams@jollamobile.com>
Remove from hover list on destruction

When hoverEnabled is unset the item remains in a hovered state until the
mouse leaves. In this circumstance, the item could be destroyed without
cleaning up the reference in the hovered items list.

To catch this and similar circumstances, the item is removed from the
list when destroyed, regardless of hoverEnabled status.

Task-number: QTBUG-30962
Change-Id: I982ab8c9e1077fecc885fd166d70bbbbbe8fc179
Reviewed-by: Shawn Rutledge <shawn.rutledge@digia.com>
Reviewed-by: Liang Qi <liang.qi@digia.com>
Enable touch events on Mac for PinchArea

Enabling touch events on a window causes scroll event
lag so we want to avoid avoid it as far as possible.

Enable/disable on scene changes, similar to what we do with
WA_AcceptTouchEvents for widgets, and in change
I2e5b5e2b093cccfc5253f7228f5ec0c588c60371 for MultiPointTouchArea.

Change-Id: I8cd8d172ffd93cfc4ec115917cc8662202f3b069
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>