I've been thinking about it some more, and I think it would be a good idea
to add another optional bool to the opt-in custom interface constructor.
So it now would be:
QFileSystemWatcher(IQFileSystemWatcherSpecialCoarseToFineGrainedNotificationsFigureOuter
*userCustomSnapshotComparisonCode, bool
Hi Konstantin,
I'm seeing a unittest failure in KDE Frameworks (sonnet framework) due to
changes in QTextBoundaryFinder. This isn't my domain of expertise, so can I
ask you to take a look at the information below, to find out if it's an
intentional change or a bug, and/or if maybe the sonnet
2012/7/28 David Faure fa...@kde.org:
I'm seeing a unittest failure in KDE Frameworks (sonnet framework) due to
changes in QTextBoundaryFinder. This isn't my domain of expertise, so can I
ask you to take a look at the information below, to find out if it's an
intentional change or a bug, and/or
Op 28-7-2012 11:04, d3fault schreef:
I've been thinking about it some more, and I think it would be a good
idea to add another optional bool to the opt-in custom interface
constructor.
Having (series of) bools in API's is usually a bad idea. See for
instance this blog posting:
Hi,
On Jul 23, 2012, at 7:15 PM, ext Laszlo Papp lp...@kde.org wrote:
The QtSerialPort project was established a little over than half a
year ago [1] in Playground. The project had already been useful (at
least to me) at the time, but it has gone through a lot of bug fixes.
Furthermore,
