mport QtQml
Binding {
property var val // we need a new property because value has no NOTIFY
signal :(
when: typeof val !== "undefined"
value: val
restoreMode: Binding.RestoreNone
}
Usage:
Text {
NoUndefinedBinding on text { val: fooObject?.title }
}
But is that really
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
a bit of a feature creep.
After a quick look, I don't see any feature requests for additional corner
properties in Jira.
The issue reported by Kai is worth fixing though.
Using BorderImage or implementing your own custom Rectangle if you want
more control seems to be better than overly
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
side of
its implementation.
Glad to answer questions about use cases and review the end-user (more like
end-developer API).
Cheers,
Pierre-Yves
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
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
job.
>
I don't understand/visualize what you mean.
Pierre-Yves
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
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;
(QUrl(QStringLiteral("qrc:/main.qml")));
This will load qrc:/+5.12/main.qml (if there's one) instead of
qrc:/main.qml when the Qt version is >= 5.12.
Cheers,
Pierre-Yves
Le lun. 18 mars 2019 à 09:13, Albert Astals Cid via Development <
development@qt-project.org> a écrit :
> 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
Sean Harmer kdab.com> writes:
>
> On Monday 30 Mar 2015 17:38:37 Arjun Das wrote:
> > Hi ,
> >
> > I have created a simple qt3d application in c++, which has a rotating
cube.
> > I would like to add buttons to the windows to stop/start rotating the
cube.
> > I am not able to see such an examp
+1
On Mon, Jul 21, 2014 at 10:38 AM, Jocelyn Turcotte <
jocelyn.turco...@digia.com> wrote:
> On Tue, Jul 15, 2014 at 08:08:39PM +, Gladhorn Frederik wrote:
> > Hi all,
> >
> > it's my pleasure to nominate Milian Wolff as approver. He's a great guy,
> works for KDAB and has done interesting w
+1
On Fri, Dec 13, 2013 at 12:39 PM, Jocelyn Turcotte <
jocelyn.turco...@digia.com> wrote:
> Hello,
>
> Michael has been working for Nokia since 2008 and joined the QtWebKit team
> in 2011, which he then followed in Digia.
> He has since then been contributing many changes to QtWebKit and has
>
ategorization rather than big
secrets. I'm more afraid I might miss some important emails because they're
lost in a big backlog of noise.
How hard can it be to set up yet another mailing list should be the real
question. Given that anyone can subsc
se to
the Dev mailing list for no good reason.
Should we have anything to say that seems worthy of Development, I'm sure
it will still find its way back here.
Just my 2¢...
Cheers,
--
Pierre
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
>> >
>> > Would anyone like to second this nomination?
>> >
>>
>
> Yes, me! +1 :)
>
>
If it's already seconded, I guess I will have to "third" then. :)
--
Pierre
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
of no
relevance to normal developers, but should definitely have its place
somewhere to further clarify the platform plugin development process.
Regards,
Pierre
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
tween users and
contributors of Qt. Maybe this is something to consider in order to
narrow it a little more.
Regards,
Pierre
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
go. Currently, I am using the one provided by the distributor, and I
only later realized that they must not have enabled it.
I wish you a good WE. (and sunny if it's like here)
Regards,
Pierre
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
e toolchain... that would need more
investigating on my part though, but if someone knows how to resolve
it, I would save some time. :)
Thank you for your time,
Pierre V.
___
Development mailing list
Development@qt-project.org
http://lists.q
On Tue, Jan 17, 2012 at 3:48 PM, Simon Hausmann wrote:
> Hi Pierre,
>
>
> I can see now how you'd be able to implement tracking with this, but I
> wonder
> how much more complex this makes your layout altogether, because hidden
> fragments are right now subject to the
Hello everybody,
As it is my first post in that list, a bit of presentation is due: my name
is Pierre Stirnweiss, and I am part of the Calligra (www.calligra.org)
team. I initially started coding in KOffice time, with the initial
implementation of the change tracking system.
We (as in the
29 matches
Mail list logo
