Re: [Development] Changelogs for 5.3.0

Hi, On 23 avr. 2014, at 01:09, Thiago Macieira wrote: > Here's some editing I've done. This serves as suggestions for other editors. > >> - QPA/Android: >> * [QTBUG-36025] Fixed a memory leak in the clipboard > > Moved to Android changes. Why was this in QtCore in the first place? QPA is a

Re: [Development] Qt 5.3 header diff: QtPositioning

> >Sent: Wednesday, April 23, 2014 01:35 >To: development@qt-project.org >Subject: Re: [Development] Qt 5.3 header diff: QtPositioning >Why do we need two sets of macros? Excellent question. https://codereview.qt-project.org/#change,83875 -- Alex ___

Re: [Development] Changelogs for 5.3.0

On 23-Apr-14 01:09, Thiago Macieira wrote: > [...] It's also in the > imperative -- why are you telling the user to rework the implementation? I reckon, it's because our commit policy (http://qt-project.org/wiki/Commit_Policy) suggests to use it for commit messages: "consider the generic Git co

Re: [Development] Changelogs for 5.3.0

qtconnectivity and qtlocation were taken care of by me. -- Alex From: development-bounces+alexander.blasche=digia@qt-project.org [development-bounces+alexander.blasche=digia@qt-project.org] on behalf of Thiago Macieira [thiago.macie...@intel.com]

Re: [Development] Qt 5.3 header diff: QtLocation

Em qua 23 abr 2014, às 10:28:51, Aaron McCarthy escreveu: > On Tue, 22 Apr 2014 14:12:46 Thiago Macieira wrote: > > http://macieira.org/~thiago/qt-5.3/QtLocation.diff > > This is fine. Qt Location is not part of the 5.3 release. Indeed. However, Ubuntu did ship it in previous releases. http://p

[Development] What am I not seeing in the QByteArray::capacity test failure?

FAIL! : tst_QByteArray::reserve() 'qba.constData() != data' returned FALSE. tst_qbytearray.cpp(1871) : failure location http://testresults.qt-project.org/ci/QtBase_stable_Integration/build_03694/win32-msvc2010_Windows_7/log.txt.gz Code around the location is: 1858 qba.resize(capacit

Re: [Development] Qt 5.3 header diff: QtLocation

On Tue, 22 Apr 2014 14:12:46 Thiago Macieira wrote: > http://macieira.org/~thiago/qt-5.3/QtLocation.diff This is fine. Qt Location is not part of the 5.3 release. Cheers, -- Aaron McCarthy ___ Development mailing list Development@qt-project.org http:/

Re: [Development] Qt 5.3 header diff: QtBluetooth

On Tue, 22 Apr 2014 14:12:46 Thiago Macieira wrote: > http://macieira.org/~thiago/qt-5.3/QtBluetooth.diff Looks fine. Cheers, -- Aaron McCarthy ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/develo

Re: [Development] Changelogs for 5.3.0

Em ter 22 abr 2014, às 16:09:07, Thiago Macieira escreveu: > > - QTextDocumentLayout: > >* [QTBUG-36743] Emit updateBlock signal in QTextDocumentLayout. > > "The updateBlock() signal is now emitted". > > This implies we had a signal that was never emitted before. If that's not > correct, pl

Re: [Development] Qt 5.3 header diff: QtCore

Em ter 22 abr 2014, às 16:34:09, Thiago Macieira escreveu: > > --- a/src/corelib/kernel/qobject.h > > +++ b/src/corelib/kernel/qobject.h > > @@ -549,6 +549,83 @@ template inline const char * > > qobject_interface_iid()> > > > > Q_CORE_EXPORT QDebug operator<<(QDebug, const QObject *); > > #endi

Re: [Development] Qt 5.3 header diff: QtWidgets

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > --- a/src/widgets/widgets/qplaintextedit.h > +++ b/src/widgets/widgets/qplaintextedit.h > @@ -141,6 +145,9 @@ public: > bool centerOnScroll() const; > > bool find(const QString &exp, QTextDocument::FindFlags options = 0); > +#

Re: [Development] Qt 5.3 header diff: QtTest

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > http://macieira.org/~thiago/qt-5.3/QtTest.diff Looks fine, not including the ugly exception verification macros. I didn't even read those. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Tec

Re: [Development] Qt 5.3 header diff: QtSql

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > http://macieira.org/~thiago/qt-5.3/QtSql.diff Looks fine, if scary. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Developm

Re: [Development] Qt 5.3 header diff: QtSensors

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > http://macieira.org/~thiago/qt-5.3/QtSensors.diff Looks fine. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development ma

Re: [Development] Qt 5.3 header diff: QtQuick

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > http://macieira.org/~thiago/qt-5.3/QtQuick.diff Looks fine from the C++ side. I have no clue what those Q_REVISION changes do to QML. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technolo

Re: [Development] Qt 5.3 header diff: QtQml

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > diff --git a/src/qml/qml/qqmlprivate.h b/src/qml/qml/qqmlprivate.h Why do we have a public header with "private" in the name? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center

Re: [Development] Qt 5.3 header diff: QtPositioning

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > --- a/src/positioning/qpositioningglobal.h > +++ b/src/positioning/qpositioningglobal.h > @@ -48,13 +48,17 @@ QT_BEGIN_NAMESPACE > #ifndef QT_STATIC > #if defined(QT_BUILD_POSITIONING_LIB) > # define Q_POSITIONING_EXPORT

Re: [Development] Qt 5.3 header diff: QtCore

No major issues. All cosmetic. Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > --- a/src/corelib/kernel/qmetatype.h > +++ b/src/corelib/kernel/qmetatype.h > @@ -771,9 +771,13 @@ struct VariantData >, flags(flags_) > { > } > +VariantData(const VariantData &other)

Re: [Development] Qt 5.3 header diff: QtDBus

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > http://macieira.org/~thiago/qt-5.3/QtDBus.diff Looks fine. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development maili

Re: [Development] Qt 5.3 header diff: QtGui

Em ter 22 abr 2014, às 14:12:46, Thiago Macieira escreveu: > diff --git a/src/gui/kernel/qopenglcontext.h > b/src/gui/kernel/qopenglcontext.h index ce34a2d..fce983f 100644 > --- a/src/gui/kernel/qopenglcontext.h > +++ b/src/gui/kernel/qopenglcontext.h > @@ -192,6 +192,17 @@ public: > QSet exte

Re: [Development] Changelogs for 5.3.0

Here's some editing I've done. This serves as suggestions for other editors. Everyone who has committed to qtbase please read through because I have editing questions for you. Em ter 22 abr 2014, às 15:13:41, Thiago Macieira escreveu: > GLES3 and desktop OpenGL are now fully supported with EGL

Re: [Development] Qt 5.3 header diff: QtLocation

I believe only Qt Positioning has been released. Qt Location hasn't. Regards, Sze-Howe On 23 April 2014 06:00, Sergio Ahumada wrote: > Qt Location is not officially part of Qt 5.3.0 .. is it? > > Sent from my BlackBerry 10 smartphone. > Original Message > From: Sune Vuorela > Sent: Dienstag,

[Development] Project structure for multi-platform mobile devices

Hi everyone Actually, I’m getting serious problems by setting up a Qt/QML project integrating also unit tests for a multi-platform mobile application. The idea is to set up a project skeleton for the development of applications, which will run on Android and iOS; and at the same time, the unit

[Development] Changelogs for 5.3.0

Please find attached the raw logs for each of the modules that had any [ChangeLog] in the v5.2.1..origin/release range. I'm taking responsibility of editing the one for qtbase. For all other modules, I'd like someone to reply to this email saying they'll be the editor. Otherwise, there will be

Re: [Development] Qt 5.3 header diff: QtWidgets

On 2014-04-22, Thiago Macieira wrote: > --- a/src/widgets/widgets/qlcdnumber.h > +++ b/src/widgets/widgets/qlcdnumber.h > @@ -43,7 +43,6 @@ > #define QLCDNUMBER_H > > #include > -#include > > QT_BEGIN_NAMESPACE > I guess this is theoretically a SiC change, but one that could also be ig

Re: [Development] Qt 5.3 header diff: QtSerialPort

On 2014-04-22, Thiago Macieira wrote: > --- a/src/serialport/qserialport.h > +++ b/src/serialport/qserialport.h > @@ -64,11 +64,11 @@ class Q_SERIALPORT_EXPORT QSerialPort : public QIODevice > Q_PROPERTY(FlowControl flowControl READ flowControl WRITE setFlowControl > NOTIFY flowControlChange

Re: [Development] Qt 5.3 header diff: QtLocation

Qt Location is not officially part of Qt 5.3.0 .. is it? Sent from my BlackBerry 10 smartphone. Original Message From: Sune Vuorela Sent: Dienstag, 22. April 2014 23:56 To: development@qt-project.org Subject: Re: [Development] Qt 5.3 header diff: QtLocation On 2014-04-22, Thiago Macieira wrot

Re: [Development] Qt 5.3 header diff: QtNetwork

On 2014-04-22, Thiago Macieira wrote: > --- a/src/network/ssl/qsslconfiguration.h > +++ b/src/network/ssl/qsslconfiguration.h > @@ -131,6 +132,21 @@ public: > +static const char NextProtocolSpdy3_0[]; > +static const char NextProtocolHttp1_1[]; These static const char[] kind of triggers m

Re: [Development] Qt 5.3 header diff: QtLocation

On 2014-04-22, Thiago Macieira wrote: > -QGeoCodingManagerEngine(const QMap ¶meters, > QObject *parent = 0); > +QGeoCodingManagerEngine(const QVariantMap ¶meters, QObject *parent = > 0); Given it is just changes to typedefs, it should be okay. There are quite many of those across this d

[Development] Qt 5.3 header diff: QtOpenGL

http://macieira.org/~thiago/qt-5.3/QtOpenGL.diff diff --git a/src/opengl/qglframebufferobject.h b/src/opengl/qglframebufferobject.h index 9312a23..affa47c 100644 --- a/src/opengl/qglframebufferobject.h +++ b/src/opengl/qglframebufferobject.h @@ -63,17 +63,11 @@ public: QGLFramebufferObject(c

[Development] Qt 5.3 header diff: QtTest

http://macieira.org/~thiago/qt-5.3/QtTest.diff diff --git a/src/testlib/qtest.h b/src/testlib/qtest.h index ac1d6cc..7c9a7b2 100644 --- a/src/testlib/qtest.h +++ b/src/testlib/qtest.h @@ -66,14 +66,14 @@ QT_BEGIN_NAMESPACE namespace QTest { -template<> inline char *toString(const QLatin1String

[Development] Qt 5.3 header diff: QtWidgets

http://macieira.org/~thiago/qt-5.3/QtWidgets.diff diff --git a/src/widgets/dialogs/qmessagebox.h b/src/widgets/dialogs/qmessagebox.h index c5598a8..5fae174 100644 --- a/src/widgets/dialogs/qmessagebox.h +++ b/src/widgets/dialogs/qmessagebox.h @@ -72,6 +72,7 @@ class Q_WIDGETS_EXPORT QMessageBox : p

[Development] Qt 5.3 header diff: QtQml

http://macieira.org/~thiago/qt-5.3/QtQml.diff diff --git a/src/qml/qml/qqml.h b/src/qml/qml/qqml.h index b6c6fe8..721f2cc 100644 --- a/src/qml/qml/qqml.h +++ b/src/qml/qml/qqml.h @@ -91,13 +91,13 @@ class QQmlPropertyValueInterceptor; const char *className = T::staticMetaObject.className(); \

[Development] Qt 5.3 header diff: QtSerialPort

http://macieira.org/~thiago/qt-5.3/QtSerialPort.diff diff --git a/src/serialport/qserialport.h b/src/serialport/qserialport.h index 6e16463..6ca5af4 100644 --- a/src/serialport/qserialport.h +++ b/src/serialport/qserialport.h @@ -64,11 +64,11 @@ class Q_SERIALPORT_EXPORT QSerialPort : public QIODev

[Development] Qt 5.3 header diff: QtSensors

http://macieira.org/~thiago/qt-5.3/QtSensors.diff diff --git a/src/sensors/qcompass.h b/src/sensors/qcompass.h index 75b6869..5351062 100644 --- a/src/sensors/qcompass.h +++ b/src/sensors/qcompass.h @@ -67,7 +67,7 @@ class Q_SENSORS_EXPORT QCompassFilter : public QSensorFilter public: virtual

[Development] Qt 5.3 header diff: QtQuick

http://macieira.org/~thiago/qt-5.3/QtQuick.diff diff --git a/src/quick/items/qquickitem.h b/src/quick/items/qquickitem.h index 2500a2d..2b08cc2 100644 --- a/src/quick/items/qquickitem.h +++ b/src/quick/items/qquickitem.h @@ -56,7 +56,7 @@ QT_BEGIN_NAMESPACE class QQuickItem; class QQuickTransfo

[Development] Qt 5.3 header diff: QtSql

http://macieira.org/~thiago/qt-5.3/QtSql.diff diff --git a/src/sql/kernel/qsqldriver.h b/src/sql/kernel/qsqldriver.h index 017ffd4..f93a030 100644 --- a/src/sql/kernel/qsqldriver.h +++ b/src/sql/kernel/qsqldriver.h @@ -62,6 +62,7 @@ class QVariant; class Q_SQL_EXPORT QSqlDriver : public QObject {

[Development] Qt 5.3 header diff: QtPrintSupport

http://macieira.org/~thiago/qt-5.3/QtPrintSupport.diff diff --git a/src/printsupport/dialogs/qprintdialog.h b/src/printsupport/dialogs/qprintdialog.h index c822aa0..886cd1e 100644 --- a/src/printsupport/dialogs/qprintdialog.h +++ b/src/printsupport/dialogs/qprintdialog.h @@ -106,7 +106,6 @@ Q_SIGNA

[Development] Qt 5.3 header diff: QtMultimedia

http://macieira.org/~thiago/qt-5.3/QtMultimedia.diff diff --git a/src/multimedia/camera/qcamera.h b/src/multimedia/camera/qcamera.h index 6a29b2c..9c413c3 100644 --- a/src/multimedia/camera/qcamera.h +++ b/src/multimedia/camera/qcamera.h @@ -64,6 +64,7 @@ QT_BEGIN_NAMESPACE class QAbstractVideoSur

[Development] Qt 5.3 header diff: QtNetwork

http://macieira.org/~thiago/qt-5.3/QtNetwork.diff diff --git a/src/network/access/qnetworkreply.h b/src/network/access/qnetworkreply.h index a7db2d1..f11a5e8 100644 --- a/src/network/access/qnetworkreply.h +++ b/src/network/access/qnetworkreply.h @@ -93,12 +93,20 @@ public: ContentNotFound

[Development] Qt 5.3 header diff: QtPositioning

http://macieira.org/~thiago/qt-5.3/QtPositioning.diff diff --git a/src/positioning/qgeorectangle.h b/src/positioning/qgeorectangle.h index cd91c1d..babbe62 100644 --- a/src/positioning/qgeorectangle.h +++ b/src/positioning/qgeorectangle.h @@ -55,6 +55,7 @@ public: QGeoRectangle(); QGeoRec

[Development] Qt 5.3 header diff: QtLocation

http://macieira.org/~thiago/qt-5.3/QtLocation.diff diff --git a/src/location/maps/qgeocodingmanagerengine.h b/src/location/maps/qgeocodingmanagerengine.h index aa2839a..11862db 100644 --- a/src/location/maps/qgeocodingmanagerengine.h +++ b/src/location/maps/qgeocodingmanagerengine.h @@ -56,7 +56,7

[Development] Qt 5.3 header diff: QtConcurrent

http://macieira.org/~thiago/qt-5.3/QtConcurrent.diff diff --git a/src/concurrent/qtconcurrentiteratekernel.h b/src/concurrent/qtconcurrentiteratekernel.h index b47c30a..0969029 100644 --- a/src/concurrent/qtconcurrentiteratekernel.h +++ b/src/concurrent/qtconcurrentiteratekernel.h @@ -86,6 +86,8 @@

[Development] Qt 5.3 header diff: QtBluetooth

http://macieira.org/~thiago/qt-5.3/QtBluetooth.diff diff --git a/src/bluetooth/qbluetoothdevicediscoveryagent.h b/src/bluetooth/qbluetoothdevicediscoveryagent.h index a311d14..4ac1685 100644 --- a/src/bluetooth/qbluetoothdevicediscoveryagent.h +++ b/src/bluetooth/qbluetoothdevicediscoveryagent.h @@

[Development] Qt 5.3 header diff: QtDBus

http://macieira.org/~thiago/qt-5.3/QtDBus.diff diff --git a/src/dbus/qdbusserver.h b/src/dbus/qdbusserver.h index d455f8e..7a7f54b 100644 --- a/src/dbus/qdbusserver.h +++ b/src/dbus/qdbusserver.h @@ -66,6 +66,9 @@ public: QDBusError lastError() const; QString address() const; +void

[Development] Debugging crashes in QML / QtDeclarative [was: Question about Qt's future]

Hi Christoph, > Christoph Feck wrote: Not speaking for Michael, but let me add that C++ is > much easier to > debug compared to QML, if you get a crash. We have nearly hundred > backtraces in the Plasma bug tracker that point back to crashes in > QtDeclarative, without a single clue where the

[Development] Qt 5.3 header diff

Results Modules with no public headers: Enginio QtAndroidExtras QtCompositor QtFtp QtHttp QtMacExtras QtOrganizer QtPlatformSupport QtPlatformSupport QtQmlDevTools QtQuickParticles QtVersit QtVer

Re: [Development] qt_add/removeObject hooks

Em ter 22 abr 2014, às 21:02:24, Milian Wolff escreveu: > BTW: Did you really compile this with Qt5? The operator T*() is gone from > QAtomicPointer, no? > https://qt-project.org/doc/qt-5/qatomicpointer-members.html It's back. https://qt.gitorious.org/qt/qtbase/commit/19c70982517e76d89bb3da931e13

Re: [Development] qt_add/removeObject hooks

On Thursday 17 April 2014 18:11:03 Kevin Funk wrote: > On Wednesday 16 April 2014 12:55:38 Matthew Woehlke wrote: > > On 2014-04-16 03:18, Volker Krause wrote: > > > On Tuesday 15 April 2014 08:02:56 Thiago Macieira wrote: > > >> In other words: use QBasicAtomicPointer. > > > > > > As mentioned on

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Em ter 22 abr 2014, às 11:13:00, Carlos Duclos escreveu: > PS1 Where could I take a look at your code? QtSerialPort is part of Qt since 5.2. https://qt.gitorious.org/qt/qtserialport http://code.woboq.org/qt5/qtserialport/ -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

> Hi Thiago, Kuba, > > >> It should support the same waitForBytesWritten() and waitForReadyRead() that >> QAbstractSocket and QProcess have. Those are blocking. >Yes, QSerialPort does it (at least tries to do). :) >>Let's make sure we distinguish blocking from buffered. It's quite ok for >>QSeri

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Em ter 22 abr 2014, às 19:34:48, Denis Shienkov escreveu: > 1. or keep it as is, but then bytesWritten() will be "tell lies" It's not lying. It's telling the user that the bytes were written from the QIODevice to the underlying device. That's the best we can do, since now those bytes are no long

Re: [Development] QScreen API

On Sat, Apr 19, 2014 at 12:00 AM, Alan Alpert <4163654...@gmail.com> wrote: > On Thu, Apr 17, 2014 at 7:54 AM, Aleix Pol wrote: > > Hi, > > Yesterday I was trying to figure out a problem I've been having on some > code > > that keeps track of screen management changes on my system. After some > >

Re: [Development] Qt-Designer sources ?

On Tuesday 22 April 2014 17:20:44 Martin Koller wrote: > Where do I find the sources for Qt Designer ? > Or is there no longer a stand-alone designer application in Qt5 as was in > Qt4 ? Thanks. In the qttools repository. qttools/src/designer -- Olivier Woboq - Qt services and support - http:

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Hi Thiago, > That's simply not workable. > If the buffer never empties, bytesWritten() would never fire. Imagine the user > is always writing data at the same speed as the device is transmitting (or > faster). Hmm.. Yes. But this scenario it is possible in case of continuous flushing (or, maybe

Re: [Development] Qt-Designer sources ?

On 22 April 2014 16:20, Martin Koller wrote: > Where do I find the sources for Qt Designer ? > Or is there no longer a stand-alone designer application in Qt5 as was in > Qt4 ? > https://qt.gitorious.org/qt/qttools/source/e7b791c8bb5e64a4c786bf370b10366815af704f:src/designer Cheers Rich. _

[Development] Qt-Designer sources ?

Where do I find the sources for Qt Designer ? Or is there no longer a stand-alone designer application in Qt5 as was in Qt4 ? Thanks. -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Em ter 22 abr 2014, às 12:28:39, Denis Shienkov escreveu: > If to be honest, I don't agree with implementation with emission of the > bytesWritten() signal in QAbstractSocket. IMHO, this signal has to be > emitted when data were really transferred, i.e. after completion of > transfer, when fired th

Re: [Development] utf-8 BOM and parsers

Em ter 22 abr 2014, às 12:35:33, Knoll Lars escreveu: > Hi, > > Just came back from vacation today. > > Unfortunately BOM’s at the beginning of files seem to still be used quite > a bit esp. in the Windows world. So I would actually vote for option 1 and > rather keep compatibility. Reason is tha

Re: [Development] utf-8 BOM and parsers

Hi, Just came back from vacation today. Unfortunately BOM’s at the beginning of files seem to still be used quite a bit esp. in the Windows world. So I would actually vote for option 1 and rather keep compatibility. Reason is that stripping the BOM will not break anything, but leaving it in will.

Re: [Development] Question about Qt's future

Olivier Goffart schreef op 22-4-2014 13:01: > On Tuesday 22 April 2014 12:20:58 Oswald Buddenhagen wrote: >> On Mon, Apr 21, 2014 at 02:52:25PM +0200, Roland Winklmeier wrote: >>> If I want to access this methods from QML I would have to derive them >>> from QObject and register it in the QML conte

Re: [Development] Question about Qt's future

On Tuesday 22 April 2014 12:20:58 Oswald Buddenhagen wrote: > On Mon, Apr 21, 2014 at 02:52:25PM +0200, Roland Winklmeier wrote: > > If I want to access this methods from QML I would have to derive them > > from QObject and register it in the QML context. > > try playing with Q_GADGET instead of Q

Re: [Development] Documenting JavaScript with QDoc

> Hello! > > I'm trying to add documentation to the JavaScript API of QWebChannel. It is a > fundamental part of this module and as such, I think proper documentation is > crucial. > > So far, I have not found a way to get qdoc to generate a page for my .js file > for me. Can it? Or do I have to

Re: [Development] Question about Qt's future

> > > > > If I want to access this methods from QML I would have to derive them > > > > > > > from QObject and register it in the QML context. > > > > > > Not necessarily, depends on what you want to do. > > > However, it is true that it would be nice to have something similar to > > > QtScript's b

Re: [Development] Question about Qt's future

On Monday 21. April 2014 15.13.08 Robert Knight wrote: > > The design direction is because QML is easier to develop with, more > > modern, > > and based on OpenGL. Widgets don't have that and will never be as > > efficient.> > > Therefore, the effort is directed towards the technology that has th

Re: [Development] qt_add/removeObject hooks

On Wednesday 16 April 2014 12:55:38 Matthew Woehlke wrote: > On 2014-04-16 03:18, Volker Krause wrote: > > On Tuesday 15 April 2014 08:02:56 Thiago Macieira wrote: > >> In other words: use QBasicAtomicPointer. > > > > As mentioned on https://codereview.qt-project.org/#change,83272 Kevin Funk > > m

Re: [Development] qt_add/removeObject hooks

On Wednesday 16 April 2014 14:46:56 Branislav Katreniak wrote: > > As mentioned on https://codereview.qt-project.org/#change,83272 Kevin Funk > > measured the difference between the current approach and using atomics > > using Olivier's initial benchmark, it's about 4-5x slower for checking if > >

Re: [Development] Question about Qt's future

On Mon, Apr 21, 2014 at 02:52:25PM +0200, Roland Winklmeier wrote: > If I want to access this methods from QML I would have to derive them > from QObject and register it in the QML context. > try playing with Q_GADGET instead of QObject/Q_OBJECT - that's much less heavyweight. if it doesn't work wi

Re: [Development] Spurious downloadProgress signal with incorrect bytesTotal when loading from cache

> On 04/11/2014 11:08 AM, Mandeep Sandhu wrote: >> >> Shouldn't these be having valid size values or is this expected >> behaviour for cached content? >> >> I guess the 1st signal (with incorrect size) being emitted is still a bug. > > > I think if the response comes from the cache the response alw

Re: [Development] Question about Qt's future

On Monday, 2014-04-21, 11:28:24, charleyb123 . wrote: > ...In this case, none of "class Cytometer" nor "class Laser" nor "class > Wavelength" derive from QObject, but we want them exposed to QML. > Including their nested properties. Wrapping-or-deriving-from-QObject is > now required. The "Wave

Re: [Development] Qt5.3 change files

On Thu, Apr 17, 2014 at 02:23:09PM +0200, Peter Hartmann wrote: > On 04/17/2014 01:38 PM, Heikkinen Jani wrote: > > All maintainers: If your component doesn’t have 5.3 changes file yet, > > please add it as soon as possible! > > I was under the impression that the changes file is generated from th

Re: [Development] Question about Qt's future

> Unfortunately that means there are now 4 completely separate UI stacks > to maintain in Qt - widgets, > QGraphicsView, the web and QtQuick v2. I wonder if they could be > harmonized at all? > > We can use QML to describe UIs in all four. True - but I'm thinking more about the implementation. If

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Hi Thiago, Kuba, > It should support the same waitForBytesWritten() and waitForReadyRead() that > QAbstractSocket and QProcess have. Those are blocking. Yes, QSerialPort does it (at least tries to do). :) >Let's make sure we distinguish blocking from buffered. It's quite ok for >QSerialPort to

Re: [Development] Nominating Giulio Camuffo (giucam) as an Approver

Thank you everyone, it's been a pleasure working with you guys so far and I'm sure it will continue to be so. Looking forward to the day I'll be nominated Chief Mantainer. :-P Giulio 2014-04-22 10:17 GMT+03:00 Blasche Alexander : > Congratulations, > > Approver rights have been set in Gerrit and

Re: [Development] [QIODevice]How to correctly treat/understand of the documentation?

Hi Kuba, > The `QSerialPort` API must be nonblocking, It is truth, currently it is non-blocking. > The writes should be executed right away if they won’t block. The semantics would be: There are some problems, please see below: > 1. Check how many bytes can be written to the OS device buffers

Re: [Development] Nominating Giulio Camuffo (giucam) as an Approver

Congratulations, Approver rights have been set in Gerrit and Jira. -- Alex From: development-bounces+alexander.blasche=digia@qt-project.org [development-bounces+alexander.blasche=digia@qt-project.org] on behalf of Nichols Andy [andy.nich...@digi