Hi,
On Thursday, February 8, 2018 9:22:24 AM EET Eike Hein wrote:
> Hi,
>
> in addition, kde.org ships a qqc2-desktop-style for Controls 2 that
> implements QStyle theming (it's an improved derivative of the code
> used in qqc1) and has no other KDE dependencies. It's viable to ship
> with an app
On Wednesday, 7 February 2018 19:32:25 PST Kevin Kofler wrote:
> We are now in early February. By your schedule, 5.11 will be out on the last
> day of May. That's a whopping 4 months without a Qt release from the
> current (non-LTS) branch! In that time, at least 2 batches of Chromium
> security up
On 02/08/2018 12:27 PM, Kevin Kofler wrote:
> NIkolai Marchenko wrote:
>> even stuff like that?
>> https://imgur.com/a/tTFeO
>
> Maybe try using QListWidget::setItemWidget? That should even let you assign
> some widget layed out in Qt Designer.
The KWidgetItemDelegate class in KDE's KItemViews
Hi,
in addition, kde.org ships a qqc2-desktop-style for Controls 2 that
implements QStyle theming (it's an improved derivative of the code
used in qqc1) and has no other KDE dependencies. It's viable to ship
with an app, and available in most distributions as a system package
as well as inside KD
Lars Knoll wrote:
> * Instead we put our focus on getting 5.11 out as quickly as we can. Let’s
> branch now, create first alpha and then beta packages as quickly as
> possible. Not having to merge from 5.10 will ease this significantly.
> Getting 5.11 out quick will hopefully also make Webengine no
NIkolai Marchenko wrote:
> even stuff like that?
> https://imgur.com/a/tTFeO
Maybe try using QListWidget::setItemWidget? That should even let you assign
some widget layed out in Qt Designer.
Also FYI, since QListWidget is a subclass of QListView, you can actually
also use a QAbstractItemDelegat
Well, thank you for your example, but I would rather code a completely
custom combobox in QML than go this route
(even with my qml skills noobish at best it seems a more reasonable idea,
than coding a "widgets monster" )
And for the time being I will just stick with Controls 1 as I want to be
impr
Am Mittwoch, 7. Februar 2018, 15:35:34 CET schrieb NIkolai Marchenko:
> even stuff like that?
> https://imgur.com/a/tTFeO
> I doubt it. I really don't want to delve into manual painter usage and
> styleoptions when I can just quickly make such stuff with qml listview.
> And basically the only thing
I meant, I will *lose* model:10 syntax like this
(mailing lists and unfixable wording errors, ugh)
On Wed, Feb 7, 2018 at 6:02 PM, NIkolai Marchenko
wrote:
> Thanks, I will see how it works. Though I will use the model: 10 syntax
> like this :(
>
> On Wed, Feb 7, 2018 at 5:46 PM, Helmut Mülner
Thanks, I will see how it works. Though I will use the model: 10 syntax
like this :(
On Wed, Feb 7, 2018 at 5:46 PM, Helmut Mülner
wrote:
> Ø And basically the only thing that really hurts me with controls 2 is
> that combobox becomes quite horrible
>
>
>
> I use something like this for a decen
I really don't want to go there for a project I am not paid to develop :)
On Wed, Feb 7, 2018 at 5:54 PM, Konstantin Tokarev
wrote:
>
>
> 07.02.2018, 17:42, "NIkolai Marchenko" :
> > even stuff like that?
> > https://imgur.com/a/tTFeO
> > I doubt it. I really don't want to delve into manual pain
07.02.2018, 17:42, "NIkolai Marchenko" :
> even stuff like that?
> https://imgur.com/a/tTFeO
> I doubt it. I really don't want to delve into manual painter usage and
> styleoptions when I can just quickly make such stuff with qml listview.
FWIW, in company where I work we routinely did such UIs
* And basically the only thing that really hurts me with controls 2 is that
combobox becomes quite horrible
I use something like this for a decent looking combobox:
ComboBox {
id: comboBox
Layout.fillWidth: true
height: 30
Layout.maximumHeight: 30
On Tuesday, 6 February 2018 23:09:59 PST Simon Hausmann wrote:
> And by the look of it we are also going to need another merge from dev to
> 5.11 for qtdeclarative as the merge from 5.10 was submitted to dev instead
> of 5.11, along with the blacklisting.
I notice that happening for qtbase and gav
even stuff like that?
https://imgur.com/a/tTFeO
I doubt it. I really don't want to delve into manual painter usage and
styleoptions when I can just quickly make such stuff with qml listview.
And basically the only thing that really hurts me with controls 2 is that
combobox becomes quite horrible
O
07.02.2018, 16:13, "NIkolai Marchenko" :
> And no, widgets is not an alterlative to proper qml controls on desktop when
> you want custom interface.
> I have an app that uses qml to draw a custom listview for users, it would be
> extremely hard to replicate it with widgets and why should I do t
Have you tried the Fusion style in 5.10?
https://doc.qt.io/qt-5/qtquickcontrols2-fusion.html
From: Development
[mailto:development-bounces+mitch.curtis=qt...@qt-project.org] On Behalf Of
NIkolai Marchenko
Sent: Wednesday, 7 February 2018 2:10 PM
To: Helmut Mülner
Cc: Qt development mailing lis
TableView is in the works:
https://blog.qt.io/blog/2017/11/23/ready-qt-quick-controls-2-3/
Controls 2 has ScrollView:
https://doc.qt.io/qt-5/qml-qtquick-controls2-scrollview.html
Qt.labs.calendar has MonthGrid and associated types:
https://doc.qt.io/qt-5/qml-qt-labs-calendar-monthgrid.html
I'
KDE has some codes that enables simulation of the "native" style through
QtQuickControls 2 if it can be useful :
https://github.com/KDE/qqc2-desktop-style
However, even though Qt Quick Controls (and Qt Quick in general) are both
very nice, I think that a big missing part is CSS-like properties, th
And no, widgets is not an alterlative to proper qml controls on desktop
when you want custom interface.
I have an app that uses qml to draw a custom listview for users, it would
be extremely hard to replicate it with widgets and why should I do that
when I have qml?
On Wed, Feb 7, 2018 at 4:10 PM,
I basically can't use Controls 2 in my application because combobox in
controls 2 has extremely out of place style for desktop applications, is
too bloated and you can't control it enough to make it look more like
Controls 1.
Admittedly, I almost do not use QML in my apps but I wasn't able to find
> It should come as no big surprise that we are not working much on Qt Quick
Controls 1.
After some discussions inside The Qt Company, we concluded that it would
make sense to clarify the situation.
We see the value Controls 1 provides - more platform native styling - but it
comes at a high price.
Hi all,
It should come as no big surprise that we are not working much on Qt Quick
Controls 1.
After some discussions inside The Qt Company, we concluded that it would make
sense to clarify the situation.
We see the value Controls 1 provides - more platform native styling - but it
comes at a hi
23 matches
Mail list logo
