On Wednesday 04 February 2015 12:47:42 Matthew Woehlke wrote:
However, explicit defaulting is still interesting for the *default*
constructor. (See
https://msdn.microsoft.com/en-us/library/dn457344.aspx; apparently in
MSVC at least there are advantages to an explicitly defaulted default
On 2015-02-02 17:51, Thiago Macieira wrote:
On Monday 02 February 2015 14:29:21 Matthew Woehlke wrote:
* Q_DECL_EQ_DEFAULT - really discouraged
I can't think of any case where you could use this and let the code still
compile in C++98, so don't use it
I'd actually like to see this used
Two more ones:
https://codereview.qt-project.org/105427
https://codereview.qt-project.org/105428
Regards,
Konstantin
2015-02-03 3:35 GMT+04:00 Konstantin Ritt ritt...@gmail.com:
Some minor ones from me:
https://codereview.qt-project.org/105199
https://codereview.qt-project.org/105200
On Tuesday 03 February 2015 07:33:46 Knoll Lars wrote:
Hi,
I’d like to mark a few modules as deprecated with 5.5, and most likely
remove them from the binary packages with 5.6. These modules are:
* Qt WebKit
* Qt Declarative (Qt Quick 1)
* Qt Script
All of these modules are by now a
On 04/02/15 10:20, Olivier Goffart oliv...@woboq.com wrote:
On Tuesday 03 February 2015 07:33:46 Knoll Lars wrote:
Hi,
I’d like to mark a few modules as deprecated with 5.5, and most likely
remove them from the binary packages with 5.6. These modules are:
* Qt WebKit
* Qt Declarative (Qt
On 03/02/15 23:26, Thiago Macieira thiago.macie...@intel.com wrote:
On Tuesday 03 February 2015 20:14:42 Knoll Lars wrote:
Yes, making the Qt WebView module work on all desktop platforms could
be a
possible solution.
I think the consensus here is that we need some more work on Qt WebView /
On 04.02.2015 10:23, Knoll Lars wrote:
In principle I agree. The problem with 2008 is that this is currently the
only compiler supporting Windows Embedded 7, so we can’t easily get rid of
it. Dropping gcc 4.4 is afaik not a big problem.
QNX 6.5.0 has GCC 4.4.2. I don't know how important QNX
Then,
What is the latest Qt version that I can use to compile Qt3D?
Thanks.
--
fede
On Fri, Jan 23, 2015 at 9:34 AM, Sean Harmer sean.har...@kdab.com wrote:
On Friday 23 January 2015 11:06:23 Ben Beckwith wrote:
Is there a version of Qt3D that I can git that is compatible with Qt
5.4.0?
On Wednesday 04 February 2015 16:15:09 Federico J. Fernández wrote:
Then,
What is the latest Qt version that I can use to compile Qt3D?
5.5 (dev branch)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Den 04-02-2015 kl. 15:56 skrev Olivier Goffart:
On Wednesday 04 February 2015 09:23:12 Knoll Lars wrote:
On 04/02/15 10:20, Olivier Goffart oliv...@woboq.com wrote:
Also, is it not time to decide which platform are we going to stop
supporting in Qt 5.6?
For example, if we were to decide to
We are intending to have a Qt track at this conference, so anyone who would
like to come and present something in May should sign up at the URL below.
Begin forwarded message:
From: Per Henrik Oja p...@oja.no
Subject: Communities! Participate!
Date: 4 February 2015 11:49:44 GMT+1
To:
Hello,
The Qt Contributors' Summit 2015 will be held in Oslo, the home of Qt, in early
June.
This year the venue will be at The Qt Company offices, and we will have an
unofficial get-together on Friday before the Summit.
The event is the annual gathering of Qt contributors (code, tests,
I've found a very strange (and serious) miscompilation of QImage with g++
In qimage.cpp there is a simple line (3584 in Qt-5.3.2):
d-paintEngine = paintEngine ? paintEngine : new
QRasterPaintEngine(paintDevice);
which results in 0(!). The return value of this method QImage::paintEngine()
It's relatively simple to compile x264 with visual studio 2013+. I was just
reading about it.
On 4 Feb 2015 11:52 pm, Guido Seifert warg...@gmx.de wrote:
If you don't have a choice, you don't have a choice, but just saying:
In one of my projects I needed the x264 libs:
If you don't have a choice, you don't have a choice, but just saying:
In one of my projects I needed the x264 libs:
http://www.videolan.org/developers/x264.html
and the webkit. I was unable to compile x264 with MSVC. Dropping webkit
would leave me in the inconvenient situation that either I
Thanks,
As far as I can see the new certificate is now in place, i.e. I can
login on qt-project.org. But still no new installation of qt-libs via
ministro is possible...
Should I wait more?
Phlippe Lelong
Le 04-02-2015 12:41, Turunen Tuukka a écrit :
Hi,
Now we have finally received the
On Wednesday 04 February 2015 09:23:12 Knoll Lars wrote:
On 04/02/15 10:20, Olivier Goffart oliv...@woboq.com wrote:
Also, is it not time to decide which platform are we going to stop
supporting in Qt 5.6?
For example, if we were to decide to start using some of the C++11, we
should drop
04.02.2015, 13:12, Martin Koller kol...@aon.at:
I've found a very strange (and serious) miscompilation of QImage with g++
In qimage.cpp there is a simple line (3584 in Qt-5.3.2):
d-paintEngine = paintEngine ? paintEngine : new
QRasterPaintEngine(paintDevice);
which results in
+1 from my side.
Best Regards,
Tobias
--
Tobias Hunger, Senior Software Engineer | The Qt Company
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB
19 matches
Mail list logo
