Le ven. 9 août 2024 à 01:56, Mike Trahearn <
miketrahe...@imagineuisoftware.com> a écrit :
> To Ulf’s point,
>
> You would indeed not be able to restore a previous value using text:
> fooObject?.title ?? text because it will have been overwritten whenever
> fooObject?.title yields a valid value.
>
ion for a c++ defined `Q_PROPERTY`.
For more advanced use cases where you don't want to reset the value, use
Binding and restoreMode.
Cheers,
Pierre-Yves Siret
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Le ven. 22 déc. 2023 à 14:19, André Somers a
écrit :
> The point I wanted to raise was that having four separate properties isn't
> ideal, and that we could give ourselves a lot of room for improvement by
> having a `corners` grouped property that can contain more than just a
> single real value
e constraints of not adding magical conversions, can we do something
to add std::optional support to the C++/QML interrop? Or is that a big nono
for now, waiting for Qt 7 or never to see the light of the day?
I believe adding more strongly typed stuff like that is the way forward to
have bett
Le jeu. 20 juil. 2023 à 15:41, Kai Uwe Broulik a
écrit :
> Hi everyone,
>
> something that came up during this year’s KDE Akademy was that we
> believe Q_PROPERTY should be able to handle std::optional, such that you
> get a null QVariant out of it if it has no value. The main use case
> being in
f Qt history would have been
easier.
I don't think QML versioning would help. Having completely different
function signatures between `import QtQuick x` versus `import QtQuick y`
would be super error prone.
Maybe a compile time flag? a runtime one? To switch bet
>
> With Widgets, GraphicsView or my framework the system depends on the
> min/preferred/max hints being evaluated by a size policy. F.e
> QSizePolicy::hasHeightForWidth() tells the layout classes, what to do.
>
> QQuickItem has the implicitSize ( = implicit preferred size ) only - no
> other expli
I feel like custom getters and the ability to mark a property dirty are
needed too.
You might have a property that's provided by an outside system, and you
maybe don't want to query it every time it changes, only when there's an
observer bound to that property.
About the
QProperty fullname;
Hello,
This can be done with QQmlFileSelector :
QQmlApplicationEngine engine;
QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get(&engine);
#if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0)
qmlFileSelector->setExtraSelectors({"5.12"});
#endif
engine.load(QUrl(QStringLiteral("qr
> The filter pipeline starts with a file or camera device, and various
> filters are applied sequentially to frames. However I spend a lot of time
> converting frames to QImages for analysis and painting. I'm hoping there's
> a faster way to do this. Some of the filters alter the frame, some just
>
Le ven. 5 oct. 2018 à 18:34, Edward Welbourne a
écrit :
> NIkolai Marchenko (5 October 2018 18:30) wrote:
> > I would like to remind people that there has already been a deprecation
> thread "
> > [Development] Deprecation of Qt Quick Controls 1" by
> > Frederik Gladhorn this Februrary.
> > A cou
2018-08-06 14:22 GMT+02:00 Mitch Curtis :
>
>
> > -Original Message-
> > From: Development > project.org> On Behalf Of Paolo Angelelli
> > Sent: Monday, 6 August 2018 1:43 PM
> > To: development@qt-project.org
> > Subject: [Development] Programmable delegate selection for QML views
> >
>
2018-03-06 11:50 GMT+01:00 Mitch Curtis :
> *From:* Development [mailto:development-bounces+mitch.curtis=
> qt...@qt-project.org] *On Behalf Of *Pierre-Yves Siret
> *Sent:* Tuesday, 6 March 2018 11:29 AM
> *To:* André Somers
> *Cc:* Qt development mailing list
> *Subject:
2018-03-06 11:12 GMT+01:00 André Somers :
>
>
> On 06/03/2018 11:04, Mitch Curtis wrote:
>
>> https://codereview.qt-project.org/#/c/221758/ makes
>> QObject::dumpObjectTree() and QObject::dumpObjectInfo() invokable so that
>> they can be used from QML. I think that this could be useful to debug
>>
2017-10-19 20:44 GMT+02:00 Shawn Rutledge :
> (thread started on the interest list, but I don’t think my comments belong
> there)
>
> On Oct 19, 2017, at 18:06, Sean Harmer wrote:
>
> > Hi,
> >
> > you've hit one of the issues we did with exposing C++ and QML APIs.
> Namely, QQmlListProperty. Thi
ith multiple columns, and the old way of (ab)using roles as
> columns. :)
>
> --
> J-P Nurmi
>
> On 14 Jan 2017, at 14:06, Pierre-Yves Siret wrote:
>
> Hi,
> I started implementing SortFilterProxyModel cause we needed it and
> published it here : https://github.com/oK
One of the shortcoming of my SFPM is that it is not really meant to be used
for multiple columns, only roles, and it doesn't support tree models.
Pierre-Yves Siret
2017-01-14 13:37 GMT+01:00 J-P Nurmi :
> Hi,
>
> I'd like to request a WIP branch for the Qt Quick item views. There
17 matches
Mail list logo