Il 21/09/2017 08:44, Lars Knoll ha scritto:
No, quite the opposite. +1 from my side to switching it over to 5.9.
This is now in place, latest build on Coverity Scan is 5.9 tip.
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB Group
Hi all,
Final downmerge from '5.9' to '5.9.2' is now done. So '5.9' is for Qt 5.9.3
from now on and all changes targeted to Qt 5.9.2 release needs to be done in
'5.9.2'
br,
Jani
> -Original Message-
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io@qt-
>
> The approaches available currently either
>
> 1) scale everything after rendering (eg with SetProcessDPIAware())
> 2) scale coordinates to screen metrics before rendering
> (QApplication::setAttribute(Qt::AA_EnableHighDpiScaling))
>
> The first approach gives a blurry result because of
On Friday, 15 September 2017 10:47:02 CEST Kevin Funk wrote:
> On Friday, 15 September 2017 06:42:34 CEST André Hartmann wrote:
> > Hi, since a while C++11 is allowed in Qt and there is ongoing effort
> > porting e.g. examples to the new possibilities.
>
> Slightly OT but I hope still useful: I'm
On 25.09.2017 10:29, iman ahmadvand wrote:
> Hi every one.
> I'm developing a set of specialized opensource widgets in c++ (called
> MaterialWidgets which is google material design implementation)
> Now i want to use private API for this library to prevent re
> implementing a bunch of logics
Hi every one.
I'm developing a set of specialized opensource widgets in c++ (called
MaterialWidgets which is google material design implementation)
Now i want to use private API for this library to prevent re implementing a
bunch of logics behind those widgets.
What is your suggestion ?
As this
