Em qua 30 abr 2014, às 18:49:25, John Layt escreveu:
This is a common pattern in Qt to indicate the last valid value, so is
OK afaik, it's just weird the same issue reports with different
severity.
For future reference: don't add those to the same enum.
--
Thiago Macieira - thiago.macieira
Oops you're right, it's there. Thanks :)
Simon
Opprinnelig melding
Fra: Alan Alpert
Sendt: 23:32 onsdag 30. april 2014
Til: Hausmann Simon
Kopi: Hartmann Thomas; development@qt-project.org
Emne: Re: [Development] Perceptions/Understandings of the QML language [was:
Question about Qt's
On 04/30/2014 11:42 AM, Peter Hartmann wrote:
Yeah, nice work! I think it would be a good thing to get this into qtbase
(should you be
willing to contribute this of course); providing only a subset of the QSsl*
functionality sounds perfectly fine to me...
I have created a qssl-ios branch in
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
QIODevice::read: device not open
SSL Echo Server listening
If your module has QML types, and you provide a qmltypes file, you
still need to update those manually each release.
Until we have an automated tool for this (I started work on one in
5.2, but it doesn't work anymore), a manual inspection of the qmltypes
file diffs can also help identify any QML
