> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Lars Knoll
> Sent: keskiviikkona 22. kesäkuuta 2016 9.49
> To: Thiago Macieira ; development@qt-
> project.org
> Subject: Re: [Development] [Releasing] brown paper bag
On 22/06/16 08:37, "Development on behalf of Thiago Macieira"
wrote:
>On terça-feira, 21 de junho de 2016 16:42:14 PDT Thiago Macieira wrote:
>> I propose that we delete the bad tag, retag and rerelease with a better
>> name.
>
>Also: update MODULE_VERSION qtdeclarative/.qmake.conf. It MUST be
On terça-feira, 21 de junho de 2016 16:42:14 PDT Thiago Macieira wrote:
> I propose that we delete the bad tag, retag and rerelease with a better
> name.
Also: update MODULE_VERSION qtdeclarative/.qmake.conf. It MUST be different
from the original 5.6.1 version.
--
Thiago Macieira - thiago.maci
On quarta-feira, 22 de junho de 2016 05:29:35 PDT Simon Hausmann wrote:
> Approach 1: Roll 5.6.2 by branching 5.6 into 5.6.2. That will bring in a lot
> more changes into the release and certainly requires a broad testing
> effort. That is in contrary to the goal of getting a fix into the hands of
Hello QtIFW developers!It's my first change.Can anybody review and merge It:https://codereview.qt-project.org/#/c/163220/Regards,Konstantin Podsvirov
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/deve
Hi,
As an advocate of the -1 release I can elaborate on what I thought was a series
of convincing reasons.
The problem: The bug affects a surprisingly large number of Qt Quick
applications. People not using Qt Quick are not affected.
The objective: Get just that one fix for qtdeclarative in
Am Mittwoch, 22. Juni 2016, 05:03:28 schrieb Jani Heikkinen:
> Hi!
> But if there is really some reason why v5.6.1-1 don't work and v.5.6.1.1
> would work then it is really ok for me to change the tag. But let's don't
> change that just because of opinions...
The naming scheme for alpha, beta, rc'
Hi!
Actually https://bugreports.qt.io/browse/QTBUG-53761 is a blocker. Priority
isn't correct at the moment but in reality the bug is preventing any bigger and
a bit complex applications working correctly. Unfortunately bug isn't
describing that well enough :(
That's why we need to update th
On quinta-feira, 16 de junho de 2016 10:38:02 PDT Jani Heikkinen wrote:
> Unfortunately we noticed https://bugreports.qt.io/browse/QTBUG-53761 is
> actually a brown paper bag issue for Qt 5.6.1 release. That's why we need
> to update release packages with change
> https://codereview.qt-project.org/
There's no reason to invent new naming schemes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/l
On terça-feira, 21 de junho de 2016 18:02:05 PDT Morten Sorvig wrote:
> I think using screen names can be a good match for cases where you are
> sometimes connecting to external screens, provided that the string returned
> by name() is unique for each screen.
It's not. It's always "DP-1" (it repor
> On 17 Jun 2016, at 22:49, Thiago Macieira wrote:
>
>
> Creator is also a bad citizen (worst of all Qt 5 applications I've tested),
> but I did not test it again in the scenarios above. When I tested before, I
> had to find the right combination that would make both the QML and non-QML
> pa
2016-06-21 14:15 GMT+02:00 Shawn Rutledge :
>
>> On 20 Jun 2016, at 18:09, Thiago Macieira wrote:
>> 160x90 mm is a valid screen size, correspoding to a 7.2" monitor.
>
> Of course, it’s just suspicious (being a fallback value, apparently), but not
> impossible.
Unfortunately it's not a fallback
Hello,
The binary compatibility report for the Qt 5.7.0 is ready:
http://abi-laboratory.pro/tracker/timeline/qt/
Thank you.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
> 2) Handling fractional scale factors
>
> This is relevant for e.g. a Windows setting of 250%, corresponding to a scale
> factor of 2.5. Presenting a fractional scale factor to the app may cause
> graphics glitches, so we round it to the nearest integer, using qRound.
>
> However, mathematically
> On 20 Jun 2016, at 18:09, Thiago Macieira wrote:
>
> On segunda-feira, 20 de junho de 2016 14:30:19 PDT Shawn Rutledge wrote:
>> Don’t you think there should be a quirks database somewhere (outside of Qt)
>> which corrects these cases? The TV model can be identified, right?
>
>> X does it, b
On Tuesday 21 of June 2016 10:47:29 Jędrzej Nowacki wrote:
> On Thursday 16 of June 2016 16:22:15 Jędrzej Nowacki wrote:
> > There is datacenter hardware maintenance break on Tuesday 21st of June
> > (6am-8am UTC+3), Coin will be shutdown a bit earlier and hopefully restart
> > after.
> > Cheers,
>
On Tuesday June 21 2016 09:50:52 Eike Ziller wrote:
>I think this would be more a question to the Qt/macOS developers, to be asked
>on the development@ mailing list ;)
OK then :)
I've, erm, borrowed some code from Qt Creator to add a Dock icon progressbar to
KDevelop, adding a minimal API (onl
On Thursday 16 of June 2016 16:22:15 Jędrzej Nowacki wrote:
> There is datacenter hardware maintenance break on Tuesday 21st of June
> (6am-8am UTC+3), Coin will be shutdown a bit earlier and hopefully restart
> after.
> Cheers,
> Jędrek
Seems that something got completely broken, Coin is down. S
cdb integration: +1
text editors: +2 (he should have taken over maintainership from me ages ago...)
-- Erik.
From: Development on
behalf of Eike Ziller
Sent: 17 June 2016 13:52:49
To:
Cc: qt-creator
Subject: [Development] Proposing David Schulz as maintainer
20 matches
Mail list logo
