Hi all,
Qt 5.9 beta2 is now available. You can update it at the top of your Qt 5.9 beta
online installation or do clean installation by using qt online installer.
Detailed instructions here:
https://wiki.qt.io/How_to_get_snapshot_via_online_installer
br,
Jani Heikkinen
Release Manager
Is there any plan to enhance the QModelIndex interface by adding support to
std::weak_ptr but being able to store a weak_ptr seems a little bit safer.
--
Filippo Cucchetto
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.o
Here is a solution using range-v3
https://github.com/cor3ntin/qt-iterate-over-associative-containers/blob/master/main.cpp
- there is of course room for improvement :)
2017-04-20 19:28 GMT+02:00 Matthew Woehlke :
> On 2017-04-20 13:18, Sergio Martins wrote:
> > On 2017-04-20 18:06, Matthew Woehlke
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 C++
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.
...or
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
https://github.com/Kitware/qtextensions
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.
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)!
Bernd
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 using
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 questio
Re: inconsistencies: I just checked video playback in Safari. HTML5 video uses
the "native" fullscreen but Flash videos go fullscreen without affecting other
screens. I've noticed the same in other browsers, but not in Google Chrome
which uses "single-screen fullscreen" regardless the type of vi
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 question, is this platform behaviour one should
Il 20/04/2017 10:43, Katja Marttila ha scritto:
> 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 wil
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:
https://github.co
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:
> https://codereview.qt-project.org/#/q/
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 submodul
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 sho
17 matches
Mail list logo
