>From a feature point of view it would fit best into Qt Network. But it's a
>sizeable piece of code added to Qt Network. Do you have any numbers on how
>this changes the size of Qt Network?
Peter and Rich, and comments from your side?
Cheers,
Lars
On 16/01/14 19:41, "Steve Gold"
mailto:steveg
On segunda-feira, 13 de janeiro de 2014 12:56:08, Thiago Macieira wrote:
> The following changes have been unreviewed for some time, even after my ping
> of 10 days ago:
>
> https://codereview.qt-project.org/73060 Centralize support for QBasicAtomic
> for ints and longs
> https://codereview.qt-pro
On Wednesday 15 January 2014 18:16:12 Rafael Roquetto wrote:
> Hello everyone,
>
> I noticed that one program that I run displays a lot of black squares when it
> shouldn't - I traced the problem down to the fact that, at least on this env
> - KDE4 + Qt5 dev branch HEAD - QPalette::mid() returns Q
I recommend that it be included in Qt 5.3 as part of the QtNetwork module.
Regards,
Steve
From: Kurt Pattyn
Sent: Thursday, January 16, 2014 6:51 AM
To: development@qt-project.org
Cc: Heikkinen Jani ; mailto:thiago.macie...@intel.com ; richmoor...@gmail.com ;
releas...@qt-project.org
Subject
On 1/16/14 19:02 , Thiago Macieira wrote:
> It's interesting that the static builds don't try to link. Should we enable
> building of examples in static builds? Hmm... we can't because examples don't
> necessarily work with static builds.
We'll enable some basic tests.
https://codereview.qt-pro
On quinta-feira, 16 de janeiro de 2014 08:29:40, Hausmann Simon wrote:
> A change in qtbase broke qtdeclarative integration due to build failure on
> iOS. It appears that the ios builds in the CI for qtbase don't actually
> every try to link a target binary, otherwise I suppose that error would've
On 13 January 2014 21:12, Alex Montgomery wrote:
> Hello,
>
> I understand that Widgets are considered "complete" in Qt5, and no new
> features are going to be added, but it's seeming more and more like the
> actual position of developers is that Widgets are fully deprecated.
I have no comment on
Hi, these are great news for me. Do you plan to use RHEL6's default
compiler (which is GCC 4.4, and therefore *very* limited C++11 support), or
the Red Hat Developer Toolset [1] which, as of the 2.0 version, comes with
GCC 4.8?
Also, the list contains "RedHat enterprise_6_x32". However, "x32" i
Hi all!
We'd like to open a discussion about the platforms used in the CI, packaging
(creates the installer binaries) and release test automation. Do note, that
this list isn't the "supported platform" -list. This is a subset of that trying
to achieve a broad coverage of different platforms and
I would like to propose the QtWebSockets module as a new feature for Qt 5.3
(see https://qt.gitorious.org/qtplayground/websockets/source/master)
There are a number of requests in Jira:
https://bugreports.qt-project.org/issues/?jql=labels%20%3D%20websockets asking
to include web socket functiona
On Wednesday 15 January 2014 13:42:01 Kuba Ober wrote:
> Currently, the metacall arguments are marshaled by copy-constructing them in
> their own heap blocks. The addresses to the copies are deposited in an
> array-of-void*, passed as the args argument to QObject::qt_metacall etc.
>
> So there are
It had been discussed on this list about 1-2 years ago (if memory
serves well), and the common consensus was to use com0com on Windows
and some VT alike option on Linux. I do not think the technology
changed much, so it is probably still the best option... In my opinion
though, the best and easiest
Hi all,
Antti Kokko is taking care of staging in release branch. Release team will help
him with this task as well. Antti (and release team) will monitor approved
changes and stage clear ones automatically. Unclear changes (p2 or lower +
changes without bug ID) will be handled case by case by c
Hi,
A change in qtbase broke qtdeclarative integration due to build failure on iOS.
It appears that the ios builds in the CI for qtbase don't actually every try to
link a target binary, otherwise I suppose that error would've been caught
earlier.
Does the error ring bells for anyone? Any ideas
Hi all,
I want to remind you all that Qt 5.3 feature freeze is coming pretty soon.
Feature freeze for Qt 5.3 is 14th Feb 2014 so there is only 4 weeks left for
implementing new features.
Qt 5.3 schedule can be found here: http://qt-project.org/wiki/Qt-5.3-release .
There is also link to the Qt
15 matches
Mail list logo
