Re: [Development] Aliasing with QSGRectangleNode

> -Original Message- > From: Gunnar Sletta [mailto:gun...@sletta.org] > Sent: Wednesday, 16 December 2015 9:05 AM > To: Curtis Mitch > Cc: development@qt-project.org > Subject: Re: [Development] Aliasing with QSGRectangleNode > > It is curious that the

Re: [Development] Proposal: Deprecating platforms in Qt 5.6 that don't support lambda

On Friday 20 February 2015 02:26:25 Thiago Macieira wrote: > Do NOT do this. This will crash: > > for (auto const : std::cref(somefunction()) { ... } Sorry for warming up an old thread, but since there was talk about the QtC coding style recommending this... It's safe for lvalues.

Re: [Development] Proposal: Deprecating platforms in Qt 5.6 that don't support lambda

On Wednesday 16 December 2015 15:01:23 Marc Mutz wrote: > // assume the following are friends of QContainerWrapper, > resp.: template > QContainerWrapper qAsConst(const T ) // lvalue > Q_DECL_NOTHROW > { return {t}; } // stores reference > template >

Re: [Development] New Qt 5.6.0 Beta candidate packages available

Hi and thanks everyone for your hard work on this massive Qt release. I'd just like to add my 2 cents. I know Qt3D on Qt 5.6.0 will still be a tech preview, but recently 2 examples (deferred-rendering-cpp and deferred-rendering-qml) got broken due to some changes in the lighting area. Here's

[Development] New Qt 5.6.0 Beta candidate packages available

Hi all, Unfortunately we found new blocker (QTBUG-49886) from previous packages. Fixes for it is now in new packages: Windows: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/292/ Linux: http://download.qt.io/snapshots/qt/5.6/5.6.0-beta/295/ Mac:

Re: [Development] Nominating Pasi Petäjäjärvi for Approver status

Thank you all! :) Br, Pasi On Tue, 15 Dec 2015 at 15:20 Al-Khanji Louai < louai.al-kha...@theqtcompany.com> wrote: > Congrats! > > _ > From: Blasche Alexander > Sent: Tuesday, December 15, 2015 3:21 AM > Subject: Re: [Development]

Re: [Development] Aliasing with QSGRectangleNode

It is curious that the aliasing in the 1x image is not reproducible with the Rectangle {} element and only for some of the elements.. Some subtlety with the private api. One difference might be that you are giving your rectangle nodes an explicit x/y while the Rectangle element uses a transform

Re: [Development] High-DPI 5.6 beta update

> On 15 Dec 2015, at 22:16, Tim Blechmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Your thoughts on projects that use ONLY SVG image resources > and not PNG/JPEG? But the above: 1) already works >>> >>> kind of ... the

Re: [Development] High-DPI 5.6 beta update

> On 15 Dec 2015, at 20:25, rpzrpz...@gmail.com wrote: > > Instead of worrying about @2x and @3x and trying to generate artwork in all > of the sizes, would it not be advantageous > to only use SVG vector format and allow the svg plugin to generate and scale > at run-time a single svg file in