Re: [Development] Pixelated UI elements in Windows HiDPI mode (5.6)

2015-11-10 Thread Friedemann Kleint
Hi, >I don't see tickets in Jira for any of these. Please do not create unrelated, single tickets for each issue. Previously, we had https://bugreports.qt.io/browse/QTBUG-40277 "Adapt styles to High DPI" (related to https://bugreports.qt.io/browse/QTBUG-46615 "Implement High DPI scaling v2 (

[Development] New Qt 5.6 Beta snapshot available

2015-11-10 Thread Heikkinen Jani
Hi all, New Qt5.6 Beta snapshot available in http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/ Windows: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/253/

[Development] Pixelated UI elements in Windows HiDPI mode (5.6)

2015-11-10 Thread Adam Light
I built Qt 5.6 (latest from the 5.6 git branch as of this morning) and tested our application with the build on Windows 10. I'm calling QApplication::setAttribute(Qt::AA_EnableHighDpiScaling); before the QApplication is created. I don't have an actual High DPI monitor so I've been testing by cli

Re: [Development] Qt LTS & C++11 plans

2015-11-10 Thread Marc Mutz
On Tuesday 10 November 2015 19:43:35 Olivier Goffart wrote: > Likewise, Marc is trying to use std::declval and type traits > in exception specification [https://codereview.qt-project.org/140132/] declval is in use for exception specifications since at least 5.5 (in QPair). As for type_traits, ple

Re: [Development] Qt LTS & C++11 plans

2015-11-10 Thread Thiago Macieira
On Tuesday 10 November 2015 12:10:17 Thiago Macieira wrote: > The problem is that the Standard Library in use is not always the one > provided with the compiler. See the cases of libstdc++ with Clang and > Dinkumware with QNX's GCC. > > If we're going to use certain Standard Library features that

Re: [Development] Qt LTS & C++11 plans

2015-11-10 Thread Knoll Lars
On 10/11/15 19:43, "Olivier Goffart" wrote: >On Tuesday 23. June 2015 10:17:40 Knoll Lars wrote: >[...] >> Qt 5.7: >> * New compiler baseline with gcc 4.7 and VC++ 2012 >> * Enable and use the C++11 features supported by these compilers >> unconditionally > >By "C++11 features", do you mean only

Re: [Development] Qt LTS & C++11 plans

2015-11-10 Thread Thiago Macieira
On Tuesday 10 November 2015 19:43:35 Olivier Goffart wrote: > Since all of these are C++11 features supported by these compiler, I would > assume that we can use them unconditionally. The problem is that the Standard Library in use is not always the one provided with the compiler. See the cases

Re: [Development] Qt LTS & C++11 plans

2015-11-10 Thread Knoll Lars
On 04/11/15 15:31, "Albert Astals Cid" wrote: >On Tue, Jun 23, 2015 at 12:17 PM, Knoll Lars > wrote: >> Qt 5.6: >> >> * We make 5.6 a long term supported release > >Any plan on how long will be that "long term"? 2 years? 5 years? 3 years was the current thinking. Cheers, Lars ___

Re: [Development] Qt LTS & C++11 plans

2015-11-10 Thread Olivier Goffart
On Tuesday 23. June 2015 10:17:40 Knoll Lars wrote: [...] > Qt 5.7: > * New compiler baseline with gcc 4.7 and VC++ 2012 > * Enable and use the C++11 features supported by these compilers > unconditionally By "C++11 features", do you mean only core language feature, or can we also use standard li

Re: [Development] Dropping support for Android 15 and below in Qt 5.7

2015-11-10 Thread Konstantin Ritt
My +1. Konstantin 2015-10-27 10:37 GMT+03:00 Eskil A. Blomfeldt via Development < development@qt-project.org>: > Hi, > > According to the data from Google Play, there are currently only 7.4% of > active devices on Android versions 15 and below (< 4.1). > > https://developer.android.com/abou

Re: [Development] Fwd: Change in qt/qtbase[dev]: QFileSystemWatcher: print out path in case of error.

2015-11-10 Thread Thiago Macieira
On Tuesday 10 November 2015 14:55:19 Marc Mutz wrote: > Hi, > > is anyone looking into this recurring CI problem? Yes, it's fixed by https://codereview.qt-project.org/140389 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center __

[Development] Fwd: Change in qt/qtbase[dev]: QFileSystemWatcher: print out path in case of error.

2015-11-10 Thread Marc Mutz
Hi, is anyone looking into this recurring CI problem? Thanks, Marc -- Marc Mutz | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - The Qt Experts --- Begin Message --- Qt CI Bot has posted comments on this change. Change subject: QFil

Re: [Development] Override toString() method for c++ QObject types in QML

2015-11-10 Thread Luke Parry
That's fine. I was curious if this was possible or not in the current state of QML2. I do not yet have critical need for it but it could also be useful for overriding the valueOf prototype. I will just use another method to provide debug information about a QObject type. Thanks for the quick answ