> From: Dmitry Volosnykh
> Sent: lundi 18 juin 2018 13:40
>
> FYI, there's QTBUG-29095 and QTBUG-25723 that feel like somewhat related to
> the problem under discussion.
I guess QTBUG-25723 is the kind of problem that Thiago solved for QCborValue
For the use case described in QTBUG-29095, I thi
FYI, there's QTBUG-29095 and QTBUG-25723 that feel like somewhat related to
the problem under discussion.
On Mon, Jun 18, 2018 at 2:33 PM Jason H wrote:
> +1 this.
>
> I'd prefer Arne's over the bind below. I do want value updates to be
> emitted so that we only have to change the data to keep d
+1 this.
I'd prefer Arne's over the bind below. I do want value updates to be emitted so
that we only have to change the data to keep dependent structures updated. I've
suggested having some kind of xpath watcher facility...
Having done some web UIs powered by a Ajax, (and qt will undoubtedly
This implementation has started. Please be aware of changing component names.
--
Alex
From: Development
on behalf of Alex Blasche
Sent: Thursday, 31 May 2018 2:42:51 PM
To: development@qt-project.org; inter...@qt-project.org Interest
Subject: Re: [Devel
Hi,
I have come up with a PoC fix for the rendering glitch regression that was
introduced by the fix for QTBUG-16252.
In fact, it seems this fix forgot that the size(hint) for a dock area should be
(0,0) when none of the widgets attached to that area are visible; failing to
take that into accou
On Mon, 18 Jun 2018 at 11:23, Kari Oikarinen wrote:
> On 18.06.2018 12:04, Frederik Gladhorn wrote:
>
>
> Other parts sound good, so I'll just touch on the big question.
>
> > And then there is the big question when we run it once over the entire
> > codebase.
>
> I'd hesitate to ever run it o
On 18.06.2018 12:04, Frederik Gladhorn wrote:
Other parts sound good, so I'll just touch on the big question.
> And then there is the big question when we run it once over the entire
> codebase.
I'd hesitate to ever run it over the entire codebase.
* It will ruin plain git blame, since so
Hi all,
as part of the closing ceremony of this year's Qt Contributors' Summit we
agreed to start using clang-format, to have fewer discussions around coding
style and rather focus on the actual code.
I have not yet thought about all angles, how to best implement this, here are
some notes:
We
The proposed changes have been enacted.
--
Alex
From: Development
on behalf of Eike Ziller
Sent: Monday, 28 May 2018 12:33:44 PM
To: Karsten Heimrich
Cc: development@qt-project.org
Subject: Re: [Development] Changing maintainer-ship for Qt Assistant, Q
