Hi Edward,
Am 10.11.2016 17:18 schrieb "Edward Welbourne" :
>
> A review puzzled several of us today by (apparently) starting at patch
> set 6. Jesus had discovered a gerrit feature we hadn't heard of:
> drafts. If you push to refs/drafts/blah instead of refs/for/blah,
On 10.11.2016 17:20, Konstantin Tokarev wrote:
10.11.2016, 19:18, "Edward Welbourne" :
A review puzzled several of us today by (apparently) starting at patch
set 6. Jesus had discovered a gerrit feature we hadn't heard of:
drafts.
FYI, it was around for ages, since
10.11.2016, 17:08, "Marco Martin" :
> On Thursday 10 November 2016 11:11:35 Olivier Goffart wrote:
>> Writing and polishing styles to pixel perfection is indeed lot of work. And
>> QStyle has the advantage hat it already exists. However one can copy-paste
>> the code to
> On Nov 10, 2016, at 6:08 AM, Marco Martin wrote:
>
> On Thursday 10 November 2016 11:11:35 Olivier Goffart wrote:
>> Writing and polishing styles to pixel perfection is indeed lot of work. And
>> QStyle has the advantage hat it already exists. However one can copy-paste
>>
10.11.2016, 19:18, "Edward Welbourne" :
> A review puzzled several of us today by (apparently) starting at patch
> set 6. Jesus had discovered a gerrit feature we hadn't heard of:
> drafts.
FYI, it was around for ages, since 2.3 release
> If you push to refs/drafts/blah
A review puzzled several of us today by (apparently) starting at patch
set 6. Jesus had discovered a gerrit feature we hadn't heard of:
drafts. If you push to refs/drafts/blah instead of refs/for/blah, you
get a review on gerrit with much of the effect we normally achieve using
WIP but without
On Thu, Nov 10, 2016 at 12:38:41PM +, Jani Heikkinen wrote:
> Lately it has been quite hard to get change files done for the releases.
>
oh, it's that time of the year again. :D
> 1) Let's enable [ChangeLog] -tag by default in commit template. After
> that you must remove/comment out it by
On Thursday 10 November 2016 11:11:35 Olivier Goffart wrote:
> Writing and polishing styles to pixel perfection is indeed lot of work. And
> QStyle has the advantage hat it already exists. However one can copy-paste
> the code to turn existing styles into QCC2 style. (You will have two style
> to
FYI, using a shorter folder name solved the problem.
Thanks for your help.
Harald
2016-11-10 10:58 GMT+01:00 Edward Welbourne :
> > I've started a new build in a folder with a shorter name
>
> Good luck,
>
> Eddy.
>
On torsdag 10. november 2016 12.29.12 CET Oswald Buddenhagen wrote:
> the easiest would be going with the normal approval rights, but limit
> the submit button to a "QUIP owners" group which would consist of lars
> (and possibly a _few_ deputies).
Considering expected traffic there it could be
Hi all,
Lately it has been quite hard to get change files done for the releases. It
should be maintainers responsibility to make sure those will be done for every
release and those are containing proper data. We have tried to help maintainers
by doing initial ones for them (running script to
On torsdag 10. november 2016 11.39.14 CET Arnaud Vrac wrote:
> Hi,
>
> I'm trying to run MaintenanceTool on my Qt commercial install and it fails,
> apparently because the SSL certificate to cdn.qt.digia.com has expired.
> This also prevents using the online installer.
>
> Can this please be
Hi,
I'm trying to run MaintenanceTool on my Qt commercial install and it fails,
apparently because the SSL certificate to cdn.qt.digia.com has expired.
This also prevents using the online installer.
Can this please be fixed ?
Thanks,
-Arnaud
___
On Wed, Nov 09, 2016 at 06:49:08PM +, Edward Welbourne wrote:
> > Agree with meta/quips
>
> +1,
>
the repository has been created.
next point: permissions.
i don't think the regular ones are appropriate - they are way too
anarchic for a process that is supposed to reflect *actual* community
On Donnerstag, 10. November 2016 09:55:00 CET Frederik Gladhorn wrote:
> Hello all,
> let's take a step back and get back into a productive discussion :)
>
> I'm sorry that Jake uses so harsh words and I hope everyone understands he
> expresses his personal opinion since he's not even directly
> On 8 Nov 2016, at 15:57, Niccolò Belli wrote:
>
> Hi,
> My laptop's monitor is a 13" with a 16:9 aspect ratio and a 3200x1800
> resolution. As you can see[1] the EDID[2] is perfectly correct.
> QT computes the scaling factor using a formula like this:
>
> On 9 Nov 2016, at 23:25, Allan Sandfeld Jensen wrote:
>
>
> Since most of the common configuration of HiDPI screens are following Mac
> standards, they have been designed to work at 2x scaling with 72DPI. We can
> not ignore all the Apple style screens out there like 4k
> On 9 Nov 2016, at 19:44, Niccolò Belli wrote:
>
>> On martedì 8 novembre 2016 23:34:48 CET, Allan Sandfeld Jensen wrote:
>>> We have a two factor scaling system. We also scale by DPI. 144/2 == 72 for
>>> instance, which happens to be the standard on Macs. Therefore
Thanks for the input.
Creating a file named webcore_generated.HTMLImageElementOrHTMLVideoEle
mentOrHTMLCanvasElementOrBlobOrImageDataOrImageBitmap.obj.rsp in a shallow
folder was no problem.
However, if I try to create it in the folder where it should be generated:
Hello all,
let's take a step back and get back into a productive discussion :)
I'm sorry that Jake uses so harsh words and I hope everyone understands he
expresses his personal opinion since he's not even directly involved in the Qt
Quick Controls (1/2) project.
Yesterday we had some debate
> On 4 Nov 2016, at 13:00, Robert Iakobashvili wrote:
>
> Right. Most users of dictation are people with learning or motoric
> disabilities.
>
> When these users are used to a certain pattern of platform-specific habits
> working for them, any other options to do the same
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Egor Pugin
> Sent: Wednesday, November 09, 2016 10:55 PM
> To: Harald Vistnes
> Cc: development@qt-project.org
> Subject: Re: [Development]
22 matches
Mail list logo