On 01/17/2014 08:49 PM, Kurt Pattyn wrote:
> So, based on the feedback, can everybody agree on QtWebSockets being an
> add-on?
> It keeps the core as is, and provides an opt-in for applications that need it.
+1, this sounds like the best solution to me...
Peter
>
> Cheers,
>
> Kurt
>
>> On 17 J
Hello again,
it's been a few weeks already, I think this means he passed the trial.
Congratulations Michael!
Thank you for the support everybody.
I've created a JIRA task for the permission request:
https://bugreports.qt-project.org/browse/QTJIRA-249
Cheers,
Jocelyn
On Fri, Dec 13, 2013 at 12
On 19 Jan 2014, at 16:34, Dmitrii Volosnykh wrote:
> Probably we may discuss it before make any unwanted bug reports...
> Basically, I have the same problems described in the referenced topic from
> URL. Specifically, I have a scene (tiles of geographic map) and an overlay
> consisting of a poly
Hello everyone,
Thanks for the nomination and all the approvals.
I will do my best and always use the newly gained +2 and -2 buttons in Gerrit
wisely :)
Best regards,
Michael
Von: development-bounces+michael.bruning=digia@qt-project.org
[developmen
Hello,
the attached example will run fine when started standalone, but will
fail with an assertion
ASSERT: "QThread::currentThread() ==
QCoreApplication::instance()->thread()" in file
/home/ulf/dev/qt5-src/qtdeclarative/src/qml/debugger/qqmldebugserver.cpp, line
551
when trying to debu
Hi,
The majority seems to agree that this should NOT go into the QtNetwork module,
but should be an add-on.
Votes so far:
Peter Hartmann: +1 - add-on
Richard Moore: +1 - add-on
Konstantin Ritt: +1 - add-on
Frederik Gladhorn: +1 - add-on
Lars Knoll: +1 - QtNetwork
Simon Hausmann has questions re
Ok, let’s keep it as an add-on for now. I’m happy with that solution as well.
When it comes to the QML API, I do agree with Simon that having compatibility
with the standard JS web sockets API is important so people can re-use code.
But that doesn’t have to exclude a more declarative QML API.
C
Mandag 20. januar 2014 13.15.46 skrev Kurt Pattyn:
> Hi,
>
> The majority seems to agree that this should NOT go into the QtNetwork
> module, but should be an add-on. Votes so far:
>
> Peter Hartmann: +1 - add-on
> Richard Moore: +1 - add-on
> Konstantin Ritt: +1 - add-on
> Frederik Gladhorn: +1
On Friday 17 January 2014 08:43:57 Rafael Roquetto wrote:
> Hello Martin,
>
> Good to hear that. I am looking forward to seeing this upstream. Do you have
> the bug report number so I can also follow it?
see https://codereview.qt-project.org/#change,76044
--
Best regards/Schöne Grüße
Martin
A:
Thanks,
Would you have the bug (task) number as well? It is missing on the commit
message.
Regards,
Rafael
On Mon, Jan 20, 2014 at 03:14:54PM +0100, Martin Koller wrote:
> On Friday 17 January 2014 08:43:57 Rafael Roquetto wrote:
> > Hello Martin,
> >
> > Good to hear that. I am looking forward
The CI system is still building for OSX 10.6.
Given the fact that OSX is at version 10.9 now, shouldn’t the build for 10.6 be
removed, and ideally replaced with a build for OSX 10.9?
Cheers,
Kurt
___
Development mailing list
Development@qt-project.org
On Monday 20 January 2014 14:18:42 Rafael Roquetto wrote:
> Thanks,
>
> Would you have the bug (task) number as well? It is missing on the commit
> message.
I did not create a bug report, I contacted digia support.
I don't know if they created a bug report, sorry
> Regards,
> Rafael
>
> On Mon
On 20 Jan 2014, at 17:36, Kurt Pattyn wrote:
> The CI system is still building for OSX 10.6.
> Given the fact that OSX is at version 10.9 now, shouldn’t the build for 10.6
> be removed, and ideally replaced with a build for OSX 10.9?
I’d prefer the CI to build for the oldest OS X version to be
Hi Guys,
I was looking through a lot of the open tickets, some of them are reported
against qt-mobility, or qt-components, projects that have since been merged
into Qt5.
Instead of being able to add comments to these tickets, I am unable to do
anything at all with them.
There is an "agile board"
Hi,
> Op 20 jan. 2014 om 17:36 heeft Kurt Pattyn het
> volgende geschreven:
>
> The CI system is still building for OSX 10.6.
> Given the fact that OSX is at version 10.9 now, shouldn’t the build for 10.6
> be removed, and ideally replaced with a build for OSX 10.9?
Why should it be one to the
On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
> The CI system is still building for OSX 10.6.
> Given the fact that OSX is at version 10.9 now, shouldn’t the build for 10.6
> be removed, and ideally replaced with a build for OSX 10.9?
Only if we decide to stop supporting 10.
I say: definitely not, and Mac devs aren't the people to ask, the market share
is.
Snow Leopard is being called "Apple's XP" for a good reason, and many (most?)
popular apps continue to support 10.6 at this point.
It will die eventually but it is not yet time. How about we reevaluate a few
mon
On 20 Jan 2014, at 18:52, André Somers wrote:
> Hi,
>
>> Op 20 jan. 2014 om 17:36 heeft Kurt Pattyn het
>> volgende geschreven:
>>
>> The CI system is still building for OSX 10.6.
>> Given the fact that OSX is at version 10.9 now, shouldn’t the build for 10.6
>> be removed, and ideally repl
On segunda-feira, 20 de janeiro de 2014 13:01:22, Jake Petroules wrote:
> I say: definitely not, and Mac devs aren't the people to ask, the market
> share is.
I'm asking the Mac devs because I expect that they know the pulse of the Mac
community.
> Snow Leopard is being called "Apple's XP" for a
Well, as I said, it's very much "Apple's XP" -- we'd like to get rid of it, and
it's slowly on it's way out but still very much relevant to keep around as a
deployment target for the time being (just as XP is).
Firefox and Chrome dropped support for 10.5 only relatively recently (late
2012?), I
Mandag 20. januar 2014 09.44.37 skrev Alan Ezust:
> Hi Guys,
>
> I was looking through a lot of the open tickets, some of them are reported
> against qt-mobility, or qt-components, projects that have since been merged
> into Qt5.
>
> Instead of being able to add comments to these tickets, I am un
I was looking at this one in particular:
https://bugreports.qt-project.org/browse/QTCOMPONENTS-930
On Mon, Jan 20, 2014 at 10:46 AM, Frederik Gladhorn <
frederik.gladh...@digia.com> wrote:
> Mandag 20. januar 2014 09.44.37 skrev Alan Ezust:
> > Hi Guys,
> >
> > I was looking through a lot of the
On Monday 20 January 2014, Thiago Macieira wrote:
> On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
> > The CI system is still building for OSX 10.6.
> > Given the fact that OSX is at version 10.9 now, shouldn’t the build for
> > 10.6 be removed, and ideally replaced with a bui
On Mon, 2014-01-20 at 13:21 -0500, Jake Petroules wrote:
> Well, as I said, it's very much "Apple's XP" -- we'd like to get rid
> of it, and it's slowly on it's way out but still very much relevant to
> keep around as a deployment target for the time being (just as XP is).
http://www.netmarketshar
On Monday 20 January 2014 19:55:05 Allan Sandfeld Jensen wrote:
> On Monday 20 January 2014, Thiago Macieira wrote:
> > On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
> > > The CI system is still building for OSX 10.6.
> > > Given the fact that OSX is at version 10.9 now, shou
Hello everyone
I've attached the raw output of the Qt 5.2.1 changelog, as created by the
create_changelog.pl tool. As you can see, it has several mistakes. This email
is meant to explain how to properly write a changelog entry in your commit
message.
The basic format is:
[ChangeLog][Major are
On segunda-feira, 20 de janeiro de 2014 20:45:50, Olivier Goffart wrote:
> It is true that building on OSX 10.6 still require GCC 4.2 which is a bit
> old. If it is possible to build with clang and target OSX 10.6 that would
> be great.
>
> We could revisit the supported compiler.
> Personally, th
> Le 21 Jan 2014 à 6:45 am, Olivier Goffart a écrit :
>
>> On Monday 20 January 2014 19:55:05 Allan Sandfeld Jensen wrote:
>>> On Monday 20 January 2014, Thiago Macieira wrote:
On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
The CI system is still building for OSX
On Jan 20, 2014, at 7:55 PM, Allan Sandfeld Jensen wrote:
> On Monday 20 January 2014, Thiago Macieira wrote:
>> On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
>>> The CI system is still building for OSX 10.6.
>>> Given the fact that OSX is at version 10.9 now, shouldn’t the
On segunda-feira, 20 de janeiro de 2014 12:08:37, Thiago Macieira wrote:
> Hello everyone
>
[snip]
Here's the edited changelog. Please re-read it. You can also find it here:
https://codereview.qt-project.org/76094
If you have updates, please reply to this email or leave a comment in the
On Jan 20, 2014, at 7:52 PM, Alan Ezust
mailto:alan.ez...@gmail.com>> wrote:
I was looking at this one in particular:
https://bugreports.qt-project.org/browse/QTCOMPONENTS-930
Hi Alan,
As the header says on that page, QTCOMPONENTS is deprecated. Those tickets
relate to an old set of componen
Requesting comments below.
On segunda-feira, 20 de janeiro de 2014 12:39:04, Thiago Macieira wrote:
> Accessibility
> -
>
> - On Linux action names were returned as empty strings in AT-SPI
>getActions, now returns the proper names.
Should I move this to QtGui? Or to QtWidgets? O
On 20 janv. 2014, at 21:59, Thiago Macieira wrote:
>
>> QtCore
>> --
>>
>> - [QTBUG-35069] Fixed a bug that caused negative number input using '-' to
>> be rejected because the current locale uses e.g. 0x2212. QIntValidator
>> and QDoubleValidator now accepts both signs as well as the l
On 2014-01-20, Thiago Macieira wrote:
> Windows
> ---
[QTBUG-35500] Fix printing on Windows. QPrinter now reports proper page
sizes for system printers.
(I would like another sentence about the actual implications. For me, it
was that my custom printing code went from 'completely broken' to
Following is an overview of the officially supported platforms for Qt (see
http://qt.digia.com/Product/Qt-Core-Features-Functions/Supported-Platforms/).
I also added an indication whether the platform is currently built on the CI
infrastructure (see
http://testresults.qt-project.org/ci/Qt5_relea
On segunda-feira, 20 de janeiro de 2014 21:30:37, Sune Vuorela wrote:
> On 2014-01-20, Thiago Macieira wrote:
> > Windows
> > ---
>
> [QTBUG-35500] Fix printing on Windows. QPrinter now reports proper page
> sizes for system printers.
Sounds like I should merge with the OS X fix:
- [QTBUG-
On segunda-feira, 20 de janeiro de 2014 22:21:54, Samuel Gaist wrote:
> On 20 janv. 2014, at 21:59, Thiago Macieira
wrote:
> >> QtCore
> >> --
> >>
> >> - [QTBUG-35069] Fixed a bug that caused negative number input using '-'
> >> to
> >>
> >> be rejected because the current locale uses e.
On 2014-01-20, Thiago Macieira wrote:
> On segunda-feira, 20 de janeiro de 2014 21:30:37, Sune Vuorela wrote:
>> On 2014-01-20, Thiago Macieira wrote:
>> > Windows
>> > ---
>>
>> [QTBUG-35500] Fix printing on Windows. QPrinter now reports proper page
>> sizes for system printers.
>
> Sounds
On 20 janv. 2014, at 22:40, Thiago Macieira wrote:
> On segunda-feira, 20 de janeiro de 2014 22:21:54, Samuel Gaist wrote:
>> On 20 janv. 2014, at 21:59, Thiago Macieira
> wrote:
QtCore
--
- [QTBUG-35069] Fixed a bug that caused negative number input using '-'
to
In the case of https://bugreports.qt-project.org/browse/QTCOMPONENTS-930
Qt-Components has a gallery example, as does Qt Quick Controls.
I had just reported a related ticket against the gallery example of qt
quick controls,
so i was going to add a comment "see related ticket:"
Meego is still a "sup
On segunda-feira, 20 de janeiro de 2014 22:59:09, Samuel Gaist wrote:
> Yes it does, with that, QLocale supports the various possible negative signs
Can you verify if the change also affects QString::toInt, toDouble, etc.?
5.1.1 doesn't support U+2212.
--
Thiago Macieira - thiago.macieira (AT)
On 20 janv. 2014, at 23:44, Thiago Macieira wrote:
> On segunda-feira, 20 de janeiro de 2014 22:59:09, Samuel Gaist wrote:
>> Yes it does, with that, QLocale supports the various possible negative signs
>
> Can you verify if the change also affects QString::toInt, toDouble, etc.?
>
> 5.1.1 doe
On segunda-feira, 20 de janeiro de 2014 23:58:21, Samuel Gaist wrote:
> On 20 janv. 2014, at 23:44, Thiago Macieira
wrote:
> > On segunda-feira, 20 de janeiro de 2014 22:59:09, Samuel Gaist wrote:
> >> Yes it does, with that, QLocale supports the various possible negative
> >> signs>
> > Can you
I was writing a test today and QtTest told me:
Actual (s) : ?12???
Expected (s2): ?12???
So I went, "duh, ok, it looks the same to me but what's behind those question
marks".
After a bit of changes [https://codereview.qt-project.org/76100], it now
prints:
Actual (s) : \u221212\u2
On segunda-feira, 20 de janeiro de 2014 21:46:22, Sune Vuorela wrote:
> On 2014-01-20, Thiago Macieira wrote:
> > On segunda-feira, 20 de janeiro de 2014 21:30:37, Sune Vuorela wrote:
> >> On 2014-01-20, Thiago Macieira wrote:
> >> > Windows
> >> > ---
> >>
> >> [QTBUG-35500] Fix printing on
Hi Alan,
On Mon, Jan 20, 2014 at 11:33 PM, Alan Ezust wrote:
> Meego is still a "supported" platform, with Jolla and all, right?
While we use a number of components that were part of or have their
roots in MeeGo, Sailfish is a rather different beast, particularly on
the UI level. Think of it as
Hi,
The example to use the new property "Drag.dragType: Drag.Automatic" crashes:
/opt/Qt5.2.0/5.2.0/gcc_64/bin/qmlscene
qt5/qtdeclarative/examples/quick/externaldraganddrop/externaldraganddrop.qml
Program received signal SIGSEGV, Segmentation fault.
0x7645bd34 in QDrag::mimeData() const
On terça-feira, 21 de janeiro de 2014 01:22:18, Fabien Castan wrote:
> #0 0x7645bd34 in QDrag::mimeData() const () from
> /opt/Qt5.2.0/5.2.0/gcc_64/bin/../lib/libQt5Gui.so.5
> #1 0x7fffef8df357 in ?? () from
> /opt/Qt5.2.0/5.2.0/gcc_64/plugins/platforms/libqxcb.so
> #2 0x7fffef8d
Tested on ubuntu 13.10 64 bits.
Valgrind result:
==22064== Memcheck, a memory error detector
==22064== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==22064== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==22064== Command: /opt/Qt5.2.0/5.2.0/gcc_64/bin/qmlsc
Please run valgrind with debug-mode Qt too. Valgrinding release-mode Qt is not
helpful. We need to know what these question marks mean:
On terça-feira, 21 de janeiro de 2014 01:36:36, Fabien Castan wrote:
> ==22064== Invalid read of size 8
> ==22064==at 0x6306D30: QDrag::mimeData() const (in
From: development-bounces+simo.falt=digia@qt-project.org
[mailto:development-bounces+simo.falt=digia@qt-project.org] On Behalf Of
Kurt Pattyn
Sent: 20. tammikuuta 2014 23:39
To: development@qt-project.org
Subject: [Development] Missing builds on the CI server?
Following is an overview
Andreas,
I have analyzed what you said and have adjusted my understanding on how it
works. Now I agree with you that current behaviour is correct. As part of
this change in my mind was ability to find a way to distinguish user
actions (map translation versus vertex dragging) in mousePressEvent()
h
>
> On Jan 20, 2014, at 7:55 PM, Allan Sandfeld Jensen
> wrote:
>
> > On Monday 20 January 2014, Thiago Macieira wrote:
> >> On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
> >>> The CI system is still building for OSX 10.6.
> >>> Given the fact that OSX is at version 10.9 n
> -Original Message-
> From: development-bounces+andrew.knight=digia@qt-project.org
> [mailto:development-bounces+andrew.knight=digia@qt-project.org]
> On Behalf Of Sarajärvi Tony
> Sent: 21 January 2014 09:02
> To: deDietrich Gabriel; development@qt-project.org
> Subject: Re: [Deve
> 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
> > >
> > > On Jan 20, 2014, at 7:55 PM, Allan Sandfeld Jensen
> > > wrote:
> > >
> > > > On Monday 20 January 2014, Thiago Macieira wrote:
> > > >> On segunda-feira, 20 de janeiro de 2014 17:36:26, Kurt Pattyn wrote:
> > > >>> The CI system is still building for OSX 10.6.
> > > >>> Given the fact
56 matches
Mail list logo
