On Wed, Aug 29, 2018 at 6:28 PM Jason H wrote:
>
> I'd like it to be Qt / Version / Platform like
> Qt 5.10.1 for Desktop
> Qt 5.10.1 for iOS
> Qt 5.10.1 for iOS Simulator
+1, and while at it, replace "Desktop" with a platfor
mpiler, also for external styles. The .qml files can be optionally
left out at deployment time.
https://codereview.qt-project.org/#/c/228360/
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
to the
next 5.9 LTS release too. Thanks for bringing this up.
--
J-P Nurmi
On 8 Apr 2018, at 13:32, m...@herrdiel.de<mailto:m...@herrdiel.de> wrote:
Update: could this be related to https://bugreports.qt.io/browse/QTBUG-67446?
That bug's workaround (setting an id in background) works here, too.
the highlighted state in the delegate background
instead.
- What's the purpose of the opaque Rectangle inside the ScrollIndicator?
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
declarative, but given that the
table layout for visible items is still missing, there’s nothing you can play
with yet, unfortunately. So far the focus has been on refactoring the
underlying itemview framework to make it suitable for building a Ta
n objects does not scale well for more
than a few columns.
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
te types,
multi-selection, and so on
(http://lists.qt-project.org/pipermail/development/2017-January/028344.html).
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
raphicsItems, there is no need to explicitly
enable touch events for QQuickItems.
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi,
Try this:
C2.StackView.onStatusChanged: console.log("Status is " +
C2.StackView.status)
--
J-P Nurmi
> On 27 Jan 2017, at 18:48, Shantanu Tushar <shaan...@gmail.com> wrote:
>
> Hi,
>
> I realized today that this doesn't work-
>
> import QtQu
> On 31 Oct 2016, at 17:00, Jason H <jh...@gmx.com> wrote:
>
>
> I'm also on 5.6.2 because we had bugfixes arrive in that that we need that
> aren't in 5.7.0, but they will be in 5.7.1
>
>
>> Sent: Monday, October 31, 2016 at 11:56 AM
>> From: &quo
cess via ComboBox::popup, and call
open() on it.
- http://doc.qt.io/qt-5/qml-qtquick-controls2-combobox.html#displayText
-prop
- http://doc.qt.io/qt-5/qml-qtquick-controls2-combobox.html#popup-prop
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.
to steal events from the
MouseArea. When preventStealing is false, Flickable's childMouseEventFilter()
steals the press from the MouseArea when it detects a flick or drag.
--
J-P Nurmi
From: Interest <interest-bounces+jpnurmi=qt...@qt-project.org> on be
c.qt.io/qt-5/qtquickcontrols2-customize.html#customizing-combobox
Hi Nuno,
There’s an example in the latest doc snapshots:
http://doc-snapshots.qt.io/qt5-5.7/qtquickcontrols2-customize.html#customizing-combobox
--
J-P Nurmi
___
Interest mailing list
Hi Freddy,
Add "QT += quickcontrols2" to your application's .pro file.
http://doc.qt.io/qt-5/qtquickcontrols2-index.html
--
J-P Nurmi
On 4 Oct 2016, at 06:59, Freddy Martinez Garcia
<freddy311...@gmail.com<mailto:freddy311...@gmail.com>> wrote:
Hi guys... as the doc sa
The documentation for ComboBox::popup seems rather scarce, so I've added a
related note to https://bugreports.qt.io/browse/QTBUG-55904.
- http://doc.qt.io/qt-5/qml-qtquick-controls2-combobox.html#popup-prop
- http://doc.qt.io/qt-5/qml-qtquick-controls2-popup.html
--
J-P Nurmi
ler.settings.baseColor
}
contentItem: Text {
id: label
// ...
}
}
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
:
https://codereview.qt-project.org/#/c/167017/
They were merged to the dev-branch before 5.8 was branched off.
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
same variable could be used for
qmlimportscanner...
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
o make it look like that. While
primitive containers can be used in any context, item models are deliberately
designed to feed data to item views. That is the context where 'count' wins
'length' hands down.
--
J-P Nurmi
___
Interest mailing li
eems rather
> arbitrary to continue to use count. >
> Specific places:
> All models. DelegateModel, DelegateModelGroup, ListModel, etc.
It's not that arbitrary. "Count" is used all over in item views and item
models, in C++ and in QML.
--
J-P Nurmi
___
ed? For something like ListView, both .length and .size
would be ambiguous, whereas .count is not that easy to misunderstand, is it?
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
ntly limit the amount of QML.
Interesting choice. I would have done the exact opposite. Application logic in
C++ and UI declaration in QML. Declaring fluid animated UIs in QML is a joy,
writing animations in C++ is not so.
--
J-P Nurmi
___
Interest mai
/QTBUG-28957
that you're probably better off with the Shortcut QML type.
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
ched property work
regardless, though. It should just forward it to the content item of the
window. This has been discussed several times, but I don't remember why it
wasn't done yet.
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://li
culates the
required implicit height to fit all children). If you want ColumnLayout and
RowLayout to resize the children to fill width and height, respectively, you
can use the “Layout.fillWidth: true” and “Layout.fillHeight: true” attached
properties for the children. For Label you have basically two o
orrect ToolBar foreground color out of the
box, when using one of the pre-defined primary colors.
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
g_ios.png" : "img_android.png"
}
thanks
Hi,
Notice that you can combine file selectors, for example:
- img.png // the base image must always exist
- +material/img.png // used with the material style, except on ios
- +material/+ios/img.pn
> On 06 May 2016, at 23:27, Elvis Stansvik <elvst...@gmail.com> wrote:
>
> 2016-05-06 22:41 GMT+02:00 J-P Nurmi <jpnu...@qt.io>:
>>
>>
>> The Stack.status property must be attached to an item that is in a
>> StackView. In the snippet above, it is
id: rect // <==
anchors.fill: parent
color: "green"
Connections {
target: rect.Stack.status === rect.Stack.Active ? button :
null // <==
onClicked: console.log("clicked")
}
}
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi ekke,
One possibility for tinting images could be to use ColorOverlay from
QtGraphicalEffects:
http://doc.qt.io/qt-5/qml-qtgraphicaleffects-coloroverlay.html
--
J-P Nurmi
On 06 May 2016, at 19:49, ekke
<e...@ekkes-corner.org<mailto:e...@ekkes-corner.org>> wrote:
just notice
Is so there are going to be some minor API differences
between the tech preview in 5.6 beta and the final release in 5.7.0.
Button {
contentItem: Item { … }
}
--
J-P Nurmi
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
31 matches
Mail list logo
