r a long time now, but
> most
> people still write str.mid(n).toInt() instead of str.midRef().toInt().
> QStringView won't change that: A function taking QStringView accepts a
> QString, too (either by implicit conversion, or where it makes sence, by
> QString over
Marc,
It is clear that your main concern is performance (needless conversions) and
convenience (being able to work efficiently with 3rd party libraries).
Regarding performance, I think it would be good if we could come up with some
numbers. How 'bad' is the current implementation compared to an
Hi,
I have resolved a DoS vulnerability in the Qt WebSockets module (see
https://bugreports.qt.io/browse/QTBUG-48123).
Which branch should I commit this patch to: 5.3, 5.4, 5.5, 5.6 or dev?
This issue is present from the very first version (since Qt 5.3).
Cheers,
Kurt
__
Well,
you can also think of “on” + , like in: onWindowClosed, onMouseClicked,
onBytesReceived, …
In the same analogy, you could have onErrorOccurred.
Seems very intuitive to me.
It depends if you want to react to a state or to the event causing that state.
Cheers,
Kurt
> On 11 Jun 2015, at 2
I wonder if you also need hot-plug detection?
> On 29 May 2015, at 11:43, Viironen Kalle
> wrote:
>
>
>
> On 28/05/15 09:22, "Knoll Lars" wrote:
>
>> On 26/05/15 20:14, "Thiago Macieira" wrote:
>>
>>> On Tuesday 26 May 2015 17:40:05 Viironen Kalle wrote:
On 26/05/15 19:42, "Thiago Ma
Hi,
we compiled a project using Qt 5.4.1 (Windows 7 64-bit MSVS 2013) and then
tried to run it on a computer with Qt 5.3.2 installed.
We received the following popup:
Is there any chance that this is still a binary compatibility problem?
Of so, I will enter it into the bugreports.
Cheers,
Ku
> On 11 Dec 2014, at 08:30, Thiago Macieira wrote:
>
>> On Wednesday 10 December 2014 17:42:06 Thiago Macieira wrote:
>> Explanation:
>> * runtime: dynamically open libdbus-1 at runtime
>> * linked: link to libdbus-1
>> * configure1: check at configure time if libdbus-1 is present in the
>> s
> On 17 Oct 2014, at 19:26, Mathias Hasselmann wrote:
>
>
>
>> Am 17.10.2014 um 18:31 schrieb Thiago Macieira:
>>> On Friday 17 October 2014 13:06:39 Milian Wolff wrote:
>>> enum Foo {
>>> Bar = 1, Baz = 2
>>> };
>>>
>>> Foo foo = static_cast(3);
>>>
>>> Now what do you do without a defau
Christian,
the problem is often when your software has to be integrated into other
software and systems, which is almost always the case in life-critical systems.
If your software is controlling a critical component like an X-ray beamer for
instance, you’d better be prepared for all kinds of rub
> On 17 Oct 2014, at 12:54, Sean Harmer wrote:
>
> On 17/10/2014 11:44, Bo Thorsen wrote:
>> Den 17-10-2014 12:22, Julien Blanc skrev:
>>> On 17/10/2014 10:15, Christian Kandeler wrote:
>>>> On 10/17/2014 08:48 AM, Kurt Pattyn wrote:
>>>>> As
> On 17 Oct 2014, at 10:15, Christian Kandeler
> wrote:
>
>> On 10/17/2014 08:48 AM, Kurt Pattyn wrote:
>> As we are developing for aerospace, avionics, defence and healthcare, we are
>> confronted on a daily basis with a lot of very stringent rules that
On 17 Oct 2014, at 09:18, Knoll Lars wrote:
> It has always been our goal to keep the public headers as clean as
> possible. So removing a few more cases where they can cause warnings is in
> principle a good goal. The main place to be careful is (as Thiago said),
> if the changes make the heade
to have warnings of the public API be
reduced to a minimum.
Nothing more, nothing less.
I want to contribute patches, but if people find it nitpicking and not worth
the effort, then it is useless to spend my precious time on it.
Cheers,
Kurt
> On 16 Oct 2014, at 21:04, Kevin Kofler wro
On 15 Oct 2014, at 09:48, Poenitz Andre wrote:
> Kurt Pattyn wrote:
>>> On 14 Oct 2014, at 10:21, Bo Thorsen wrote:
>>>
>>> Den 14-10-2014 08:59, Kurt Pattyn skrev:
>>>> how do these applications comply with MISRA?
>>>
>>> MIS
Hi Bo,
> On 14 Oct 2014, at 10:21, Bo Thorsen wrote:
>
> Den 14-10-2014 08:59, Kurt Pattyn skrev:
>> how do these applications comply with MISRA?
>
> MISRA is impossible to comply with for a framework. For example, consider the
> required rule 0-1-11: "There
Hi,
supplying a QVariant property containing a custom type towards QML does not
work (even if it is registered as a metatype).
Currently I am explicitly converting the custom type to something QML
understands, like:
if (variant.canConvert()) {
MyCustomType1 t = variant.value();
//strea
Hi,
This has already been brought up before: when compiling an application/library
using Qt and setting compiler warnings to comply with e.g. the Misra C++ rules,
Qt generates a lot of warnings.
I already did some work on eliminating some of the warnings, but there are
still quite a lot left.
A
Hi,
After a long time, I finally found time again to help Qt forward (at least that
is what I hope :-) ).
I have a few questions regarding the 'new' branching scheme:
1. Is this somewhere documented?
2. Where do bug fixes go? I talked to Peppe regarding this, and according to
him, bugs should be
Hi Stefan,
I would appreciate if you could give a small explanation of what your research
is about. People get bothered with surveys much too often.
Cheers,
Kurt
> On 22 Aug 2014, at 23:54, "Stefan Kullack" wrote:
>
> Dear all,
>
> for a university research project at the Technical Univer
> On 06 Jun 2014, at 12:23, Oswald Buddenhagen
> wrote:
>
>> On Fri, Jun 06, 2014 at 11:38:34AM +0200, Kurt Pattyn wrote:
>> Just for clarity:
>> * Is the release branch gone for developers?
> it's gone for everyone. it has been deleted.
> the next rele
Just for clarity:
* Is the release branch gone for developers?
* And is there only one dev branch? Suppose 5.4 is in the make and meanwhile a
5.3.x patch release is being worked upon,
where will the dev branch end up? Or should we just push our patches to the
5.3.x in that case?
Cheers,
Kurt
O
> On 13 May 2014, at 08:01, Knoll Lars wrote:
>
>> On 12/05/14 22:40, "Thiago Macieira" wrote:
>>
>>> Em seg 12 maio 2014, às 19:35:24, Oswald Buddenhagen escreveu:
On Mon, May 12, 2014 at 08:39:37AM -0700, Thiago Macieira wrote:
> Em seg 12 maio 2014, às 11:48:21, Ulf Hermann escrev
rmal warning got
> suppressed because it occurred in the
> Qt template class header even though the error was actually in
> relation to my code.
>
> Regards,
> Rob.
>
>
>> On 7 May 2014 10:09, Mikołaj Siedlarek wrote:
>>> On 07 May 2014, at 10:59, Kurt Pattyn
On 06 May 2014, at 11:40, Mikołaj Siedlarek wrote:
> Hi,
>
> I’m on a quest to enable hack-free all-warnings-enabled building of my
> project using, among others,
> Qt and CMake. This requires that compiler treat Qt headers included in my
> code as “system headers”
> and not warn me about co
Hi,
I would like to know if there are any guidelines about using qDebug and friends
in Qt source code?
Recently I had to remove qWarning statements from a submit (for very plausible
reasons), but a quick search through qtbase revealed a lot of qWarning
statements.
So are there any rules of thu
Could this be a solution: https://github.com/x2on/OpenSSL-for-iPhone ?
This project provides a script to make a static build of OpenSSL to be used on
iOS 4.3 - iOS 7.1.
Cheers,
Kurt
On 02 May 2014, at 10:16, Jeremy Lainé wrote:
> On 05/01/2014 03:51 PM, Jeremy Lainé wrote:
>> One problem I am
> On 01 May 2014, at 22:31, "Steve Gold" wrote:
>
> I just tried to run the echo client and server examples using
> qt-opensource-windows-x86-android-5.3.0-RC_2014-04-29_22-03-28-79.exe and
> MinGW on Windows 8 64 bit from Qt Creator. The server displays
> QIODevice::read: device not open
> Q
Nice work!
I suppose you just want to replace the private implementation of QSSLSocket
leaving the QSSLSocket header intact?
QWebSockets depends further on the OpenSSL macro (can't remember the exact name
now) to decide whether SSL sockets are supported. I think we also need another
macro that
Maybe writing an OpenSSL compatibility layer over Apple's API is also an option?
Does anyone has an idea where OpenSSL is used in Qt? Definitely for SSL
sockets, but maybe also for generating ciphers, hashes, aso?
Cheers,
Kurt
> On 29 Apr 2014, at 14:21, Jeremy Lainé wrote:
>
>> On 04/29/2014
> On 29 Apr 2014, at 13:31, Richard Moore wrote:
>
>
>
>
>> On 29 April 2014 12:13, Sorvig Morten wrote:
>> >> What would the best course of action be to add support for secure
>> >> websockets
>> >> on iOS?
>> >
>> > Probably to add a new QSslSocket backend that uses the Apple API.
>>
>>
> On 29 Apr 2014, at 00:16, Jeremy Lainé wrote:
>
>> On 04/28/2014 11:44 AM, Nichols Andy wrote:
>> It is possible still in the packaged versions of Qt for iOS to make
>> connections using SSL via QNetworkAccessManager as there is a backend that
>> uses Apples crypto API, but without OpenSSL
> On 28 Apr 2014, at 07:53, Peter Kümmel wrote:
>
>> On 27.04.2014 22:40, Thiago Macieira wrote:
>>> Em dom 27 abr 2014, às 13:09:50, Peter Kümmel escreveu:
On 26.04.2014 17:39, André Pönitz wrote:
You could have made the point "declarative structures are good for GUI
description
> On 15 Apr 2014, at 21:25, Jake Petroules wrote:
>
>> On 2014-04-15, at 01:13 PM, Thiago Macieira
>> wrote:
>>
>> Hello
>>
>> I'd like to nominate Jake Petroules as approver. He's been very active in
>> the
>> Mac port in the recent months, helping out with issues like adding support
>>
Go Sze-Howe, go!
> On 11 Apr 2014, at 16:36, Blasche Alexander
> wrote:
>
> Approver rights have been set in Jira and Gerrit. Congratulations to Sze-Howe.
>
> --
> Alex
>
>
> From: development-bounces+alexander.blasche=digia@qt-project.org
> [deve
+1
> On 23 Mar 2014, at 00:50, Thiago Macieira wrote:
>
> Hello
>
> I'd like to nominate Sze Howe Koh as approver. You must have seen the number
> of contributions already done in the mailing list discussions, but you may
> not
> have seen the contributions done to Qt documentation.
>
> Her
When compiling applications on OSX 10.9 with clang,
I encounter quite a lot of deprecated warnings like this:
qbytearray.h:496:22: warning: definition of implicit
copy constructor for 'QByteRef' is deprecated because it has a
user-declared copy assignment operator [-Wdeprecated]
inline
Installer on Mac OSX with Retina display shows low resolution application icon.
When tabbing through the open applications an ugly looking icon is shown.
Should I file a bug report for this?
Cheers,
Kurt
On 22 Mar 2014, at 11:24, Heikkinen Jani wrote:
> Hi,
> New snapshot available in
> http
Hi,
when compiling an application, I get a lot of these warnings:
Qt5.3.0/5.3/clang_64/lib/QtGui.framework/Headers/qquaternion.h:145:12: warning:
'qIsNull' was marked unused but
was used [-Wused-but-marked-unused]
return qIsNull(xp) && qIsNull(yp) && qIsNull(zp) && qIsNull(wp);
Qt5.3.
Hi,
is there any reason why math3d is in the QtGUI module on not in the QtCore
module?
Cheers,
Kurt
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
t-project.org] On
>> Behalf Of Kurt Pattyn
>> Sent: Wednesday, March 19, 2014 4:33 PM
>> To: development@qt-project.org
>> Subject: [Development] 5.3 beta: QtWebSockets examples missing
>>
>> Hi,
>>
>> I noticed that in the beta release of Qt 5.3 for Ma
Hi,
I noticed that in the beta release of Qt 5.3 for Mac OSX Clang from March 19th,
the examples are missing for the Qt WebSockets module.
I assume I missed something in the configuration of the documentation.
How can the examples of that module be included in the examples section that is
visibl
Hi,
Recently I came across Effective C++ again and saw a chapter regarding inline
methods.
In short, Scott Meyer argued against it, because of potential binary
compatibility problems, code bloat, and so on.
My question is: is there any convention within Qt about inline methods?
Cheers,
Kurt
_
nge,80620
>
> Morten
>
>
> On 11 Mar 2014, at 12:12, Kurt Pattyn wrote:
>
>> Some more information.
>>
>> I work on OSX.
>> When digging into the platform specific implementation, I detected that in
>> the method qcgl_createNSOpenGLPixelFormat()
file a bug report for that.
Cheers,
Kurt
On 11 Mar 2014, at 11:28, Kurt Pattyn wrote:
> Hi,
>
> as I understand correctly the ‘old’ QGLxxx classes will be replaced by new
> QOpenGLxxx classes.
> I tried the following code below, and found out that QGLContext is correctly
>
Hi,
as I understand correctly the ‘old’ QGLxxx classes will be replaced by new
QOpenGLxxx classes.
I tried the following code below, and found out that QGLContext is correctly
setting the color depth,
while QOpenGLContext always defaults to 8.
QSurfaceFormat ogfrmt;
ogfrmt.setRedBufferS
> On 10 Mar 2014, at 08:37, "Giuseppe D'Angelo" wrote:
>
>> On 10 March 2014 07:43, Kurt Pattyn wrote:
>> Is the documentation on the signal sslErrors() still correct then: "Note:
>> You cannot use Qt::QueuedConnection when connecting to this signa
> On 09 Mar 2014, at 22:46, Richard Moore wrote:
>
>> >
>> > IIRC SSL sockets had the same "issue" when SSL errors are raised. Has
>> > it been solved there? How?
>> AFAIK, it has not been solved. The problem is the same.
>
> It has been partially solved, in recent versions you can set the soc
On 09 Mar 2014, at 21:02, Giuseppe D'Angelo wrote:
> On 9 March 2014 15:10, Kurt Pattyn wrote:
>> Also, the connection between the authenticationRequired signal and the slot
>> must be a direct connection.
>
> IIRC SSL sockets had the same "issue" when
On 09 Mar 2014, at 19:32, Olivier Goffart wrote:
> On Sunday 09 March 2014 15:10:02 Kurt Pattyn wrote:
>> Currently, QNAM stalls when authentication is required (also see:
>> https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection
>> between the authenti
On 09 Mar 2014, at 17:50, Kevin Krammer wrote:
> On Sunday, 2014-03-09, 15:10:02, Kurt Pattyn wrote:
>> Currently, QNAM stalls when authentication is required (also see:
>> https://bugreports.qt-project.org/browse/QTBUG-16251). Also, the connection
>> between the authenti
On 09 Mar 2014, at 17:16, Konstantin Ritt wrote:
>
> 2014-03-09 16:10 GMT+02:00 Kurt Pattyn :
> Currently, QNAM stalls when authentication is required (also see:
> https://bugreports.qt-project.org/browse/QTBUG-16251).
> Also, the connection between the authenticationRequired
Currently, QNAM stalls when authentication is required (also see:
https://bugreports.qt-project.org/browse/QTBUG-16251).
Also, the connection between the authenticationRequired signal and the slot
must be a direct connection.
This is problematic when an application wants to show a login dialogbox
Thanks for the reply.
On 25 Feb 2014, at 23:22, Gunnar Sletta wrote:
> On 26 Feb 2014, at 00:42, Kurt Pattyn wrote:
>
>> We are currently looking into a way to render a 10-bit image in QML.
>
> I'm going to assume we're talking about Qt Quick 2.0.
Yes, indeed.
&g
We are currently looking into a way to render a 10-bit image in QML.
Our first idea is to create an OpenGL context in C++ and use that in QML.
QML must be able to overlay text on this 10-bit OpenGL context.
What is the best approach for this? Is it possible at all?
Can we expose a QGLWidget, or so
On 20 Feb 2014, at 08:32, Thiago Macieira wrote:
> ... and removing them in Qt 6
>
> Please raise your hand if you knew we had that feature.
Never heard of this.
>
> Please raise your hand if you've ever used them in your own code.
So, never ever used it, and never had a need for such function
Hi Martin,
> On 17 Feb 2014, at 19:39, Martin Koller wrote:
>
> Hi,
>
> had a quick look into the implementation as I wanted to use it in my existing
> webserver.
> However, the API does not provide a way to use it for an _existing_ tcp
> communication channel.
Do you mean a QTcpSocket?
>
> W
On 17 Feb 2014, at 08:18, Kojo Tero wrote:
> Hi Thiago (and all),
>
> Yes, we have a date for the Contributor Summit. June 10-11, and the location
> this time will be Berlin.
> I'll post more information as soon as we have more details to share.
>
> Tero Kojo
> Qt Online Community Manager - D
On 15 Feb 2014, at 20:38, Laszlo Papp wrote:
> I have not read this thread through, but it is long for me now, but I
> would like to note one suggestion from my side:
>
> Make 1-2 unstable releases or a new add-on module. Unfortunately, we
> have not done that, and we are now stuck with a coupl
Hi,
since QtWebSockets moved from the playground, the unit tests are not run
anymore.
Any idea where I can file this problem (which project in Jira)?
Cheers,
Kurt
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mail
On 11 Feb 2014, at 19:21, "Giuseppe D'Angelo" wrote:
> On 11 February 2014 19:14, Thiago Macieira wrote:
>>
>> Anyone up for creating a nice function for Qt 5.4?
>
> I *cough* volunteered some time ago, but I'm going to miss the 5.3 deadline.
I can help you with you that if you want.
Cheers,
On 11 Feb 2014, at 19:14, Thiago Macieira wrote:
> Em ter 11 fev 2014, às 16:26:44, Tony Van Eerd escreveu:
>> http://channel9.msdn.com/Events/GoingNative/2013/rand-Considered-Harmful
>
> No doubt. And we should have a more secure generator, at least until we can
> rely on std::random.
We can a
On 11 Feb 2014, at 17:15, Thiago Macieira wrote:
> Em ter 11 fev 2014, às 09:04:39, Konrad Rosenbaum escreveu:
>> Please don't go there. AFAIK qrand() is a function meant to be equivalent to
>> the ANSI-C rand() function. I.e. it is supposed to be used by simple
>> simulations, be fast and produc
On 10 Feb 2014, at 20:17, Thiago Macieira wrote:
> Em seg 10 fev 2014, às 19:54:18, Kurt Pattyn escreveu:
>> Well, this is what I propose: use a delegate class that handles the creation
>> of a random 32-bit number. This would avoid having to subclass QWebSocket
>>
e
> seeding, but I'll have to study the API first to make sure.
>
> On Sunday, Sunday 09 February 2014 at 22:40, Kurt Pattyn wrote:
>> If the above implementation suffices, then a virtual method would not be
>> needed anymore.
>
> Please use the virtual method
On 09 Feb 2014, at 23:57, Olivier Goffart wrote:
> On Sunday 09 February 2014 22:40:22 Kurt Pattyn wrote:
>
> I think you are making it more complicated than it need to be.
> It turns out 32 bit entropy is enough because that's the size of your mask,
> so
> just
On 29 Jan 2014, at 09:45, Konrad Rosenbaum wrote:
>
> 1) create a fresh TCP connection for each Websocket, this way it is not
> possible to combine a previous HTTP request and a socket in an attack;
> consequently: if the handshake fails: terminate the TCP connection!
This is already happenin
On 26 Jan 2014, at 19:12, Konrad Rosenbaum wrote:
> Hi,
>
> [wow, I had a good laugh!]
>
>
> On Sunday 26 January 2014, Kurt Pattyn wrote:
> > On 26 Jan 2014, at 11:31, Konrad Rosenbaum wrote:
> > > Depends. What is it used for? Is it just obfuscation o
On 21 Jan 2014, at 01:05, Thiago Macieira wrote:
> 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.q
On 26 Jan 2014, at 11:31, Konrad Rosenbaum wrote:
> Depends. What is it used for? Is it just obfuscation or is it supposed to be
> real security?
Well, there are 2 places where random numbers are used:
1. During the handshake phase
Client sends a handshake request containing a 128-bit random n
On 17 Jan 2014, at 19:46, Frederik Gladhorn wrote:
> Just another remark which I'm not sure about:
> In section 5.2 of rfc 6455 randomness is mentioned. I didn't read up on the
> background but currently there is only a call to initialize qsrand with
> QDateTime::currentMSecsSinceEpoch() which
> When websockets becomes part of a Qt module you can consider using
> QObjectPrivate which makes the d pointer implementation slightly cleaner and
> removes the need for duplicate d pointers (one from qobject one for the
> class's own implementation.
I tried to use QObjectPrivate, but then I c
> On 23 Jan 2014, at 21:16, Jan Farø wrote:
>
> I don’t think anybody has mentioned the lack of ability to upgrade hardware -
> mostly because of financial issues, I suppose. 10.6 is as far as I know the
> last Mac OS to support 32 bit systems. Previous versions of my own software
> supported
Great, thanks for the effort.
/Kurt
On 22 Jan 2014, at 11:13, Oswald Buddenhagen
wrote:
> On Mon, Jan 20, 2014 at 01:15:46PM +0100, Kurt Pattyn wrote:
>> The majority seems to agree that this should NOT go into the QtNetwork
>> module, but should be an add-on.
>>
>
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 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
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
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
On 19 Jan 2014, at 14:18, iMath <2281570...@qq.com> wrote:
> when the widget is Activated or Deactivated ,QEvent::WindowActivate and
> QEvent::WindowDeactivate are not triggered
Please create a bug report at https://bugreports.qt-project.org.
> .
>
> On 17 Jan 2014, at 21:01, Matt Broadstone wrote:
>
> I'm inclined to agree with Rich, opting for keeping this as an addon.. for
> now. It's a 7k loc codebase that was mostly written in the past 1-3 months.
The code is actually older than the 3 months it is on the playground.
> How much has it
> On 17 Jan 2014, at 12:13, Blasche Alexander
> wrote:
>
>
>
> --
> Alex
>
>> On Fri, Jan 17, 2014 at 10:49 AM, Pau Garcia i Quiles
>> wrote:
>>
>>
>>Hello,
>>
>>If it's currently a separate module, which compiles by itself and can be
>> used by itself, why not adding it as an
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.
Cheers,
Kurt
> On 17 Jan 2014, at 12:25, Richard Moore wrote:
>
>> On 17 January 2014 07:54, Knoll Lars wrote:
>>
>> From a feature p
On 17 Jan 2014, at 17:56, Kurt Pattyn wrote:
>
> On 17 Jan 2014, at 14:10, Gladhorn Frederik
> wrote:
>
>> Hi Kurt,
>>
>> I'm quite impressed with the state of the websockets module.
> Thanks!
>> I tried reviewing the code, but I have to admit t
To me an add-on is fine and the name is fine as well as it covers exactly what
it does.
+1 for the add-on.
On 17 Jan 2014, at 14:21, Frederik Gladhorn wrote:
> Hi,
>
> I recently worked on a few small classes that wrap native TTS frameworks (for
> now SAPI5 on Windows, the Cocoa API on Mac,
st is sorted in descending order, and the server picks the latest
protocol version that it supports. That seems fine to me, but I’ll double-check
the RFC.
Cheers,
Kurt
>
> Greetings,
> Frederik
>
> From: development-bounces+frederik.gladhorn=digia@qt-project.org
>
On 17 Jan 2014, at 10:30, Simon Hausmann wrote:
>
> (removing releasing and other dev subscribed folks from CC)
>
> On Thursday 16. January 2014 12.51.28 Kurt Pattyn wrote:
>> I would like to propose the QtWebSockets module as a new feature for Qt 5.3
>> (see
On 17 Jan 2014, at 10:01, Peter Hartmann wrote:
> On 01/17/2014 08:54 AM, Knoll Lars wrote:
>> 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?
>>
>> P
gt;
> On 16/01/14 19:41, "Steve Gold" wrote:
>
> 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-pro
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
I had some changes but unit tests are failing with
FAIL! : tst_QTcpServer::linkLocal(WithoutProxy)
'socket->waitForConnected(5000)' returned FALSE. ()
Loc: [../tst_qtcpserver.cpp(929)]
Is there a problem with the test servers?
see: https://codereview.qt-project.org/#change,73476 and
https:
On 08 Jan 2014, at 10:12, Koehne Kai wrote:
>
> You can then use it like that:
>
> If (qtCoreIo().isDebugEnabled()) {
>QString x = expensive();
>qCDebug(qtCoreIo) << "Expensive: " << x;
> }
>
> Anyhow, note that qCDebug(qtCoreIo) expands to
>
> for (bool enabled = qtCoreIo().isDeb
On 19 Dec 2013, at 02:31, Thiago Macieira wrote:
>
> I especially like memcpy_s, which takes an extra argument which is most often
> the exact same value you were already passing anyway[1]. Too bad they didn't
> make memcmp_s, that would have been funny, returning EDOOFUS if you passed
> the
Best wishes for 2014 and a good health for you, your family and Qt of course!
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi,
I noticed that the oldest open item in Gerrit dates back to 7 October 2011.
There are around 2000 items still open. I suppose a lot of them are not
relevant anymore.
Wouldn’t it a good idea that the maintainers of the different modules in Qt go
through them and either discard them or merge
QString, QByteArray, QList, aso often use sign integers to store sizes,
indexing, aso.
This often leads to signed/unsigned mismatches and is not really according
standard practice.
Also, this restricts the indexes, sizes, aso to 32-bit.
One solution to resolve the signed/unsigned mismatch is to c
On 23 Dec 2013, at 17:38, development-requ...@qt-project.org wrote:
> From: Andreas Aardal Hanssen
> Subject: Re: [Development] [Request] Add Info to QDebug
> Date: 23 Dec 2013 15:17:06 GMT+1
> To: development@qt-project.org
>
> FTR, I’m completely -1 for touching QDebug and friends, and +1 for
On 23 Dec 2013, at 12:00, development-requ...@qt-project.org wrote:
> From: Alejandro Exojo
> Subject: Re: [Development] [Request] Add Info to QDebug
> Date: 22 Dec 2013 19:01:51 GMT+1
> To: development@qt-project.org
>
>
> El Saturday 21 December 2013, Kurt Pattyn escr
On 22 Dec 2013, at 05:51, development-requ...@qt-project.org wrote:
> From: Thiago Macieira
> Subject: Re: [Development] [Request] Add Info to QDebug
> Date: 21 Dec 2013 17:15:20 GMT+1
> To: development@qt-project.org
>
>
> On sábado, 21 de dezembro de 2013 14:23:10, Kur
Qt currently supports the following ‘severity’ levels for logging: Debug,
Warning, Critical, Fatal and System.
I propose to add the following levels: Info and Error, with associated methods
qInfo() and qError().
Particularly, the Info severity can be interesting to have applications output
log
Hi,
I propose to move QtWebSockets from the playground
(https://qt.gitorious.org/qtplayground/websockets/) to the official Qt
repository as an add-on.
As there is a need for a websockets implementation in Qt (see
https://bugreports.qt-project.org/browse/QTBUG-26300 and
https://bugreports.qt-pr
> On 19 Dec 2013, at 02:05, Nicolás Alvarez wrote:
>
> 2013/12/18 Kurt Pattyn :
>> For a lot of the standard C functions, Microsoft has implemented "safe"
>> versions.
>> Functions like sprintf, scanf, strcpy, aso have "safe" counterparts with an
1 - 100 of 142 matches
Mail list logo
