| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I61d077758c83027cbfc1b99d32cb68efc0829ffd
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ia39a52e7e8d968b05fd7a2d64ab3b3030a9f528e
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I8f883dd0fd06172032dd78ff60437c906c2fe8dd
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename the former tst_declarative to tst_sanity and
extend it with tests to prevent:
a) use of anchors, and
b) multiple attached object instances of the same type.
Anchors are not allowed for two reasons:
- performance (QQuickAnchors is a QObject), and
- to let users relayout delegates (x/y/width/height bindings
can be overridden, anchors not so easily)
Multiple attached object instances (eg. Theme) can easily happen by
accident. "Theme.fooColor" can be used in the control root, but in all
delegate items, "control.Theme.fooColor" must be used instead.
Change-Id: I4045d5bd717fa21db79d1c3bd618fc450e292fa4
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Id0d3489c0c047c837bf2aab5bafcd75f9db3b966
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Iee61e89d8519e7e3d27f1bf1c35af210f48bc7c9
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
| |
Not allowed:
- .js files
- signal handlers
- function declarations
Change-Id: I31247f154b96718ca95835120c9e7326e3c97968
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I1bf29fab227f1f2642994f9167c9a6957abcbb65
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
| |
The recently introduced contentWidth/Height was ambiguous. It had even
different semantics than in Containers, TextXxx & Flickable etc. Thus,
replace with availableWidth/Height.
Change-Id: Iaeef25ec82b395c602724d222ca73666460ffd29
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
- width follows only if x and width are both not specified
- height follows only if y and height are both not specified
Change-Id: Ib881daa9da339baac53f7f9d4de6e5bdad7723e2
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
It was emitted only when LayoutMirroring.enabled changed, but
it also needs to be emitted when layoutDirection changes...
Change-Id: I9424fdf232c11669780c9abace5c162a0df69dbe
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Icbb39aa1c3ac6f4b00adbc59c09a6c79e99bafd3
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I44df09c17d6d20cfd929af4e331e15f48b19587e
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: If10ef6f111b4a91216bbb2d0b52bc182533edaa8
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This API is cleaner than having to connect to each signal
handler namually.
We solve the 'pressed' signal problem by connecting to the
other signal accessor, namely 'onPressed'. And we do so for
all signals.
We also lay foundation to capture the signal parameters as
each signal is emitted. What we may do with those values is
not clear yet.
Auto-tests updated accordingly.
Change-Id: Ieda96a43072ca7dff2b183e07f6f67aa49c8cf5d
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|
|
|
|
|
|
|
| |
Also made a few cosmetic changes to the output of ControlSpy.
Change-Id: Iec6982b3de3dda3aaa312e29801d0708ef8d739e
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Allows specifying expected sequences on signals for a control,
and optionally test for property values when each signal is
emitted.
Rewrote Button auto-test suite using ControlSpy.
Change-Id: Id27c1b9ca7ee070898bcd008379e06959341ee04
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We now support the following pattern:
1. Press the mouse button => emit pressed
2. Move the mouse cursor outside the button => pressed = false
3. Release the mouse button => emit canceled
Note that getting the mouse grabbed away by another item, at any
stage, will also emit the canceled signal.
Change-Id: I97e485327370ea47943dfef75553000cee449a01
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
This way it works out of the box and can be used with visible true/false
etc. It's also in line with what qtquickcontrols (1) do.
Change-Id: Ib82b0a60a7a78b6646452704f4ffb96fbd16923c
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I4d6f555faac81e56c32c6baf0a9ede14849a5855
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I8bfc5a89aa75addd4cb1a5c0d5b58ea8b2bcf67c
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I5942457258e1c666a0d67dbc5a9a5611d4ed5967
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I37e2ab2c1f64f907b5895f41ee278b58af4e2655
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
|
|
|
|
|
| |
Change-Id: Ia5387aa16325453c676a2542f80c827d4c069ca9
Reviewed-by: J-P Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I0186cd36f0b42ca015b70a09af27f8a3517d4a60
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
| |
SplitView is a very centric control. It won't be provided in Qt Quick
Controls 2.0, but maybe later when desktop support is re-considered.
Qt Quick Controls 2.0 will focus on embedded and mobile. SplitView is
still available in 1.x
Change-Id: I3bc1c7a525d4e1e75153205ca806dc4dcee7e601
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I56eea0c3cdd03486a1e94be2dddb03249788582d
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I006ee566647e31d1a14919d164d7dd68539aae10
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ia0f875955aef223259fd172b2f64109b3bd92229
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Ia1556502ece0bc385375e61653169bdc855f592e
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|
|
Change-Id: Ib8c0c4160958e5cfea29a6e9df1b3f1fb19715fc
Reviewed-by: Jari-Pekka Nurmi <jpnurmi@theqtcompany.com>
|