The build with the latest update from the release branch (commit
f3f634ae660e77effac660bc624b9a6f986cc398) is failing on OSX 10.9.
Projects/qt5/qtbase/mkspecs/features/mac/default_post.prf:22: cache(): invalid
flag stash.
Projects/qt5/qtbase/mkspecs/features/mac/default_post.prf:23: cache():
Rerunning configure solved this problem.
On 22 Nov 2013, at 22:02, Kurt Pattyn pattyn.k...@gmail.com wrote:
The build with the latest update from the release branch (commit
f3f634ae660e77effac660bc624b9a6f986cc398) is failing on OSX 10.9.
Projects/qt5/qtbase/mkspecs/features/mac
Hi,
does QTBUG-32655 still makes part of these?
/Kurt
On 22 Nov 2013, at 22:18, development-requ...@qt-project.org wrote:
From: Heikkinen Jani jani.heikki...@digia.com
Subject: [Development] FW: Finalizing qt5.2 RC1
Date: 22 Nov 2013 13:43:37 GMT+1
To: development@qt-project.org
What is the general rule to include files in a Qt add-on module, more specific,
when should include files be prefixed with the module name?
If I look at QTcpSocket.h I see:
#include QtNetwork/qabstractsocket.h
#include QtCore/qvariant.h
Includes prefixed with the module name.
In
Also a big thanks from my side, Shane. I wish you all the luck in the new job.
Richard and Peter, many thanks for taking this up.
On 04 Nov 2013, at 20:46, development-requ...@qt-project.org wrote:
From: development-bounces+kai.koehne=digia@qt-project.org
Hi Mikkel,
it would be great to have native support for JP2K.
Kurt
On 04 Nov 2013, at 22:51, Mikkel Krautz mik...@krautz.dk wrote:
Hello,
I'm process of attempting to integrate support for the ICNS (OS X icon
files) format into Qt as an icon engine.
Hi,
I would like to add secure sockets support to the QWebSocket class (see
QtWebSockets add-on at https://qt.gitorious.org/qtplayground/websockets).
Currently, a connection is made to a web socket server, as follows:
QWebSocket webSocket;
webSocket.open(QUrl(“ws://someserver”));
Hi,
currently the QWebSocket class (see
https://qt.gitorious.org/qtplayground/websockets), emits the signals
textFrameReceived() and binaryFrameReceived().
These signals are tightly connected with the way web sockets work. Too me, this
feels too ‘low level’.
Wouldn’t it be better to buffer
I can add to this that Google also disallows exceptions, as is stated in their
style guide:
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml?showone=Exceptions#Exceptions
So, Qt is not alone in this regard.
On 03 Oct 2013, at 12:00, development-requ...@qt-project.org wrote:
All XML validation in Qt is based on XML 1.0 (and not the newer 1.1 standard).
I found at least 3 places where validity is checked:
1. in qxmlstream.cpp:
Method resolveCharRef:
//checks for validity
ok = (s == 0x9 || s == 0xa || s == 0xd || (s = 0x20 s = 0xd7ff)
On 08 Sep 2013, at 20:01, development-requ...@qt-project.org wrote:
From: Konstantin Ritt ritt...@gmail.com
Subject: Re: [Development] [Question] Implementation of XML character
validation
Date: 8 Sep 2013 20:00:45 GMT+02:00
To: development@qt-project.org development@qt-project.org
On 08 Sep 2013, at 20:43, Thiago Macieira thiago.macie...@intel.com wrote:
On domingo, 8 de setembro de 2013 20:36:39, Kurt Pattyn wrote:
bool QXmlUtils::isChar(const QChar c)
{
return (c.unicode() = 0x0020 c.unicode() = 0xD7FF)
|| c.unicode() == 0x0009
|| c.unicode
On 08 Sep 2013, at 20:43, Thiago Macieira thiago.macie...@intel.com wrote:
On domingo, 8 de setembro de 2013 20:36:39, Kurt Pattyn wrote:
It's limited by the size of QChar. It cannot contain 0x1.
Isn't it supposed that a QChar contains a Unicode character (which is 32-bit in
size
was just wondering how QChar fits within the Unicode 6.2 standard?
Reading the docs doesn't clarify much.
Kurt
On 08 Sep 2013, at 22:43, Konstantin Ritt ritt...@gmail.com wrote:
Plz read the docs.
Regards,
Konstantin
2013/9/8 Kurt Pattyn pattyn.k...@gmail.com
On 08 Sep 2013, at 20:43
: Re: [Development] A bug or not a bug, that's the question
Date: 5 Sep 2013 17:35:49 GMT+02:00
To: development@qt-project.org
On quinta-feira, 5 de setembro de 2013 13:46:19, Kurt Pattyn wrote:
Is it OK then to remove the check in QUtf8Codec, or do we need a check on
the DBus version (which
From: Thiago Macieira thiago.macie...@intel.com
Subject: Re: [Development] A bug or not a bug, that's the question
Date: 26 Aug 2013 17:16:19 GMT+02:00
To: development@qt-project.org
On segunda-feira, 26 de agosto de 2013 13:53:38, Kurt Pattyn wrote:
We should remove the check
On 29 Aug 2013, at 00:21, development-requ...@qt-project.org wrote:
From: Richard Gerd Kuesters rich...@humantech.com.br
Subject: Re: [Development] [Feature Request] Websockets
Date: 28 Aug 2013 19:28:11 GMT+02:00
To: development@qt-project.org
A couple of things got me thinking about the
Hi,
when implementing web sockets, I encountered a problem with the QTextCodec
class.
This is a code snippet:
QTextCodec *codec = QTextCodec::codecForName(UTF-8)
codec-toUnicode(someUtf8StringContainingNonCharacters, …);
When toUnicode is called with a string containing Unicode non-character
On 26 Aug 2013, at 14:26, Christoph Feck christ...@maxiom.de wrote:
What do you mean with maintained as is? The document you cite does
not mention anything related to invalid UTF-8.
Unicode strictly requires no loss of information when going between the
different representations.
Currently
Hi,
I am about to move the QWebSockets project (see:
http://github.com/KurtPattyn/QWebSockets) to the playground.
Could you please review the API?
Notes:
The public API is QWebSocket and QWebSocketServer; all other classes are
internal.
The APIs of both classes were modelled after
of QTcpSocket and QTcpServer. I'll expand
the unit tests in the coming days. I suppose I cannot run Autobahn on the Qt
infrastructure?
Best regards,
Kurt
On 25 Aug 2013, at 22:29, Matt Broadstone mbroa...@gmail.com wrote:
On Sun, Aug 25, 2013 at 3:49 PM, Kurt Pattyn pattyn.k...@gmail.com wrote
wrote:
On 16/08/13 03:41, Matt Broadstone wrote:
On Wed, Aug 14, 2013 at 11:54 AM, Kurt Pattyn pattyn.k...@gmail.com
mailto:pattyn.k...@gmail.com wrote:
Hi,
I opensourced a Qt based module that implements the web socket
protocol. The repository can be found here
Yes, I know about the project. About a year ago, I started using that, but it
was not fit for purpose. I needed to transmit large quantities of CT and
mammography images, and it was too slow (the reason was that the implementation
does not send the data frame per frame, but captures all the
101 - 123 of 123 matches
Mail list logo
