Hi all,
Qt 5.7 beta is out & work towards final release continues. One step on the way
is String Freeze which is planned to happen 7th May 2016, see
https://wiki.qt.io/Qt-5.7-release. So it is time to start keeping the
translatable strings as it is and fix remaining important issues.
Br,
J
On Tue, 26 Apr 2016, Lisandro Damián Nicanor Pérez Meyer wrote:
Please correct me if I'm wrong: the feature which will break API was added in
5.6.0, and we can say that most of the people out there are not using it.
Ideally API/ABI should not be broken without a SONAME change. If I had some
Qt5
> > As a distribution packager, I think that's a good plan. :-) The people
> > on proprietary operating systems seem less happy about that, as
> > evidenced by this thread. But that's not MY problem… ;-)
>
> Indeed.
>
> If we want the binaries to include the builds, we could include the DLLs for
pebcak, by using cmath code should be using the std namespace.
Sorry for the noise.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
_
Suppose this simple code:
#include
#include
void Foo::bar() {
QPointF refPos, newPos;
/// They get some values.
if( abs(refPos.x()-newPos.x()) > abs(refPos.y()-newPos.y()) ) {
// Do something.
}
}
With gcc6 I will get:
error: call of overloaded ‘abs(qreal)’ is ambiguous
If we can simply update libmng and recompile against the new version then we
should do so immediately!
On Apr 26, 2016, at 4:47 PM, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On quarta-feira, 27 de abril de 2016 01:39:38 PDT Kevin Kofler wrote:
Thiago Macieira wrote:
Sorry, just
On terça-feira, 26 de abril de 2016 20:51:30 PDT Lisandro Damián Nicanor Pérez
Meyer wrote:
> Please correct me if I'm wrong: the feature which will break API was added
> in 5.6.0, and we can say that most of the people out there are not using
> it.
No ABI breakage happened. There's a change in b
Please correct me if I'm wrong: the feature which will break API was added in
5.6.0, and we can say that most of the people out there are not using it.
Ideally API/ABI should not be broken without a SONAME change. If I had some
Qt5 app using it already I would be forced to do a hack in our packa
On quarta-feira, 27 de abril de 2016 01:39:38 PDT Kevin Kofler wrote:
> Thiago Macieira wrote:
> > Sorry, just deleting. That makes downloading and maintaining such a
> > library SEP.
>
> As a distribution packager, I think that's a good plan. :-) The people on
> proprietary operating systems seem
Thiago Macieira wrote:
> Sorry, just deleting. That makes downloading and maintaining such a
> library SEP.
As a distribution packager, I think that's a good plan. :-) The people on
proprietary operating systems seem less happy about that, as evidenced by
this thread. But that's not MY problem…
On quarta-feira, 27 de abril de 2016 01:11:28 PDT Kevin Kofler wrote:
> Jake Petroules wrote:
> > The MNG and JPEG2000 plugins are no longer built by default on most
> > platforms because upstream development has stalled and there are known
> > security vulnerabilities. See
> > https://codereview.q
I wrote:
> For libmng, you bundle the ancient version 1.0.10 from 2009 (!).
Sorry, from 2007, even!
Kevin Kofler
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Jake Petroules wrote:
> The MNG and JPEG2000 plugins are no longer built by default on most
> platforms because upstream development has stalled and there are known
> security vulnerabilities. See
> https://codereview.qt-project.org/#/c/141429/
For libmng, you bundle the ancient version 1.0.10 fro
El Tuesday 26 April 2016, Shawn Rutledge escribió:
> Personally I think event compression should be a cross-platform feature if
> we’re going to have it. The event-pileup problem can happen also on
> Windows for example, but it seems that we never implemented event
> compression on any platform ot
On terça-feira, 26 de abril de 2016 10:02:46 PDT Matthew Woehlke wrote:
> Since when does SC mean that code written for version Y must compile
> against version X (X < Y)? Usually it's only the other way around... Or
> do I not understand what would break, here? (Is the problem just that
> code wri
On terça-feira, 26 de abril de 2016 11:54:15 PDT Oleg Shalnev wrote:
> And socket is connected!!!
>
> The problem is that socket connected and signal emmited.
>
> Only then after couple of seconds program received error "Remote host
> closed"
>
>
> On Linux and Android all ok.
>
>
> Qt 5.5 5.
On 2016-04-26 08:08, Shawn Rutledge wrote:
> If the application does not handle high-frequency events (mouse
> movements and window moves/resizes) quickly enough, some events will
> be dropped.
Do you really mean dropped? Or do you mean merged? There is a HUGE
difference...
Please don't EVER si
Hi,
The way you describe the problem sounds like it is specific to tablet events on
X-Windows. In my opinion a solution to the problem applied to the 5.6 branch of
Qt
should also be limited to tablet events on X-Windows. Wouldn't it therefore be
easiest to simply not do tablet event compression
On Tue, Apr 26, 2016 at 1:08 PM, Shawn Rutledge wrote:
>
>
> I was told to request this exception on the mailing list, because we usually
> try to maintain source compatibility between releases.
>
> So, any objections?
(Having been the one asking for bringing the matter up to the ML): an
excepti
> On 26 Apr 2016, at 14:08, Shawn Rutledge wrote:
>
> Personally I think event compression should be a cross-platform feature if
> we’re going to have it. The event-pileup problem can happen also on Windows
> for example, but it seems that we never implemented event compression on any
> plat
In 5.6.0, an event compression feature was added to the xcb platform plugin, to
fix QTBUG-40889 and QTBUG-47069. That is here:
https://codereview.qt-project.org/#/c/126136/ Qt 4 had a similar feature, and
then it was possible to turn it on or off, using widget attribute
WA_NoX11EventCompressi
Hi all!
I have no idea what's the (hell) is going on.
The simplest test...
SocketTest::SocketTest()
{
mSocket=new QTcpSocket(this);
QObject::connect(mSocket, SIGNAL(hostFound()), this, SLOT(onHostFound()));
QObject::connect(mSocket, SIGNAL(connected()), this, SLOT(onConnected()));
QO
Den 23.04.2016 13:11, skrev Simon Hausmann:
Hi,
Usually the CI system won't rebuild depending modules, but in this case no
builds exist of qtbase. That is because MinGW 5.3 was added to the CI system -
replacing MinGW 4.9 - maybe yesterday (I'm not sure exactly when) and qtbase
doesn't comp
On Tuesday 26 April 2016 07:15:47 Tony Sarajärvi wrote:
> Hi,
>
> We ran out of disk space on the CI master. Problem has been fixed now and
> things are being restarted.
Thanks. Don't worry about re-staging the Qt 3D changes though, I found a
problem with them after staging that I've since fixed
Hi,
We ran out of disk space on the CI master. Problem has been fixed now and
things are being restarted.
-Tony
> -Original Message-
> From: Development [mailto:development-
> bounces+tony.sarajarvi=qt...@qt-project.org] On Behalf Of Marc Mutz
> Sent: 26. huhtikuuta 2016 10:15
> To: de
On Monday 25 April 2016 21:03:24 Sean Harmer wrote:
> Hi All,
>
> is someone around who could kill the current Qt 3D CI integration please?
> It's been going since lunchtime today and appears to be stuck.
Same for QtBase integrations: running since 14:13 yesterday.
--
Marc Mutz | Senior Softwa
26 matches
Mail list logo