(The TLDR for this is https://bugreports.qt.io/browse/QTBUG-94168)
When working on pointer handlers a few years ago, I was mainly thinking of the
primary use cases where the target property points to an Item to be
manipulated, and when the handler is active, it changes the appropriate
propertie
Hi all,
On 20.05.21 08:26, Alex Blasche wrote:
Congratulations to Andreas. Approver rights have been granted.
thanks a lot for your trust. During the last days, I approved my first
few patches. It is great to be part of the Qt Project.
cheers,
Andreas
___
Hi,
Having the controls within declarative and also using the controls more in all
the relevant examples would be beneficial for the users. So I think this might
be one dependency we could add, not only for testing.
Yours,
Tuukka
Lähettäjä: Development käytt
> On 4 Jun 2021, at 16:10, Mitch Curtis wrote:
>
>> -Original Message-
>> From: Volker Hilsheimer
>> Sent: Friday, 4 June 2021 2:45 PM
>> To: Mitch Curtis
>> Cc: development@qt-project.org
>> Subject: Re: [Development] Solutions for ensuring that changes in upstream
>> modules are teste
> -Original Message-
> From: Volker Hilsheimer
> Sent: Friday, 4 June 2021 2:45 PM
> To: Mitch Curtis
> Cc: development@qt-project.org
> Subject: Re: [Development] Solutions for ensuring that changes in upstream
> modules are tested with downstream modules before merging
>
> > On 4 Jun 2
> On 4 Jun 2021, at 13:56, Mitch Curtis wrote:
>
> Hi.
>
> A common problem I see is that a change in say qtbase or qtdeclarative can
> cause test failures in modules that depend on them after that change is
> merged. As a result, dependency updates for the downstream modules can be
> blocke
Hi.
A common problem I see is that a change in say qtbase or qtdeclarative can
cause test failures in modules that depend on them after that change is merged.
As a result, dependency updates for the downstream modules can be blocked,
requiring the module maintainer to look into the failure, onl
