[Development] Qt 5.9 Header diff (API review)

Hi all, It is time to do official Header diff for Qt 5.9 APIs (compared to Qt 5.8.0) >From here you can find the diffs: >https://codereview.qt-project.org/#/q/branch:5.9+topic:%22API+Review%22,n,z >(thanks to Eddy!) Please do the review now if not done yet. We should get '+2' for each

[Development] Please update your Qt Online Installer’s Maintenance Tool

Hi, We are about to change the domain used in Qt Online Installations. If you are using an old version of Maintenance Tool, now is a good time to update it to version 2.0.5-2. So please run ‘Update components’ and your Qt installation will continue working without errors. The MaintenanceTool

Re: [Development] Qt 5.9 Header diff (API review)

Some of the diffs don’t look like they are 100% up to date. Eddy? Lars > On 20 Apr 2017, at 11:43, Jani Heikkinen wrote: > > Hi all, > > It is time to do official Header diff for Qt 5.9 APIs (compared to Qt 5.8.0) > > From here you can find the diffs: >

Re: [Development] old-style, consistent fullscreen behaviour on Mac

I see the problem you are trying to solve, but I don't think it's worth it to maintain a separate code path for this legacy mode that conflicts with the platform behavior. tor arne On 20/04/2017 00:04, René J. V. Bertin wrote: Hi, I went ahead and tinkered with Qt4's code:

Re: [Development] Please update your Qt Online Installer’s Maintenance Tool

In in corporating the propr objection sand in addition to, 1. Why should I care? Or more specifically, why should you bother the users about this. It seems that a techincal implementation is the way to go. You have a vaiety of options: a. Use http 300 codes b. Use a proxy c. Use DNS aliases.

Re: [Development] old-style, consistent fullscreen behaviour on Mac

On Thursday April 20 2017 14:56:04 Tor Arne Vestbø wrote: > Yes. > > If you want non-platform behavior because you disagree with the > platform's choice, you are welcome to write one in user-code using > frameless window set to QScreen::geometry() e.g. That's a valid PoV for writing code

Re: [Development] Stepping down as the QNX maintainer / proposing James McDonnell

Hi, I'd like to add that James will act as the sole maintainer for QNX. I am still listed as co-maintainer along with Rafael at least on paper. Though, I have been dragged away from QNX even more unfortunately, so there is no point in keeping this role. @James: make Qt on QNX great (again)!

Re: [Development] old-style, consistent fullscreen behaviour on Mac

On 20/04/2017 13:42, René J.V. Bertin wrote: On Thursday April 20 2017 12:20:17 Tor Arne Vestbø wrote: I see the problem you are trying to solve, but I don't think it's worth it to maintain a separate code path for this legacy mode that conflicts with the platform behavior. That's the

Re: [Development] QHash iteration vs std::unordered_map

On 2017-04-16 10:44, Corentin wrote: > If you want the same behavior, you can create a proxy for your associative > container instance, with a custom iterator whose operator*() returns a std > pair ( or a QPair ) - quite a bit of boilterplate code. ...or use

Re: [Development] QHash iteration vs std::unordered_map

On 2017-04-20 18:06, Matthew Woehlke wrote: On 2017-04-16 10:44, Corentin wrote: If you want the same behavior, you can create a proxy for your associative container instance, with a custom iterator whose operator*() returns a std pair ( or a QPair ) - quite a bit of boilterplate code.

Re: [Development] QHash iteration vs std::unordered_map

On 2017-04-20 13:18, Sergio Martins wrote: > On 2017-04-20 18:06, Matthew Woehlke wrote: >> for (auto i : qtEnumerate(my_hash)) >> do_stuff(i.key(), i.value()); > > That doesn't work with temporaries, does it ? No. Neither does std::add_const / qAsConst. > Maybe something to fix in the