Re: [Development] Multiple QML engines with different import paths, file selectors, etc

Hi, I don’t necessarily want to walk into the specifics of that feature of this change - more that I think compatibility is something that should be considered very valuable - to the point that prior to starting work on refactorings that break compatibility (in behavior in this case), there

Re: [Development] Multiple QML engines with different import paths, file selectors, etc

Hi, have you considered how you can keep compatibility, by making this change either opt-in or opt-out? Since it seems the refactoring is already done, it feels like you are making a bet that only has a negative outcome for those porting/trying to keep up.  Good for maintenance, bad for users?

Re: [Development] Future of java-style iterators?

How about QDir::iterator, QDir::cbegin, basically make QDir a container? Or make a new class that serves the same purpose… /me likes the QDir idea.. :-) Andreas Tir 5 des 2023 kl. 22:15 skrev Mathias Hasselmann via Development: > Hi, > > would QDirIterator[1] be part of this deprecation? Its

Re: [Development] qsizetype

On Wed, Sep 7, 2022, at 08:45, Kevin Kofler via Development wrote: > Alex Blasche wrote: > > 2.) An alternative might be to make this change in one go for Qt 7. We > > would keep Qt 6.x on the status quo but start adding compatible > > replacement APi with an absolute change at 7.0 (ifdefs or

Re: [Development] Requesting forward BC exception for QtWaylandCompositor in 6.2 and 5.15

On Tue, Feb 15, 2022, at 19:46, Thiago Macieira wrote: > On Tuesday, 15 February 2022 09:34:35 PST Marc Mutz wrote: > > 6.2 is an LTS release, is it not? > > Not from my point of view, it isn't. *cough* *cough* Can this be commented officially by the chief maintainer? Andreas

Re: [Development] Nominating Volker Hilsheimer as co-maintainer of Qt Widgets

+1  On Tue, Jan 25, 2022, at 10:30, Oliver Eftevaag wrote: > +1! > > > *From:* Development on behalf of Lars > Knoll > *Sent:* Tuesday, January 25, 2022 9:55 AM > *To:* Fabian Kosmale > *Cc:* Qt development mailing list > *Subject:* Re: [Development] Nominating Volker Hilsheimer as

Re: [Development] Erroneous Qt TouchBegin event to QGraphicsView ?

> 3. aug. 2017 kl. 04.54 skrev Patrick Stinson : > Hi there! > I am seeing a QEvent::TouchBegin being sent to the QGraphicsView viewport (on > Mac) when moving the mouse into or out of the view with no buttons pressed. I > noticed this because if a QLineEdit somewhere

Re: [Development] Widgets maintainers

xt related things > Andreas Aardal Hanssen for graphicsview Go widget team? ;-) Andreas ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Using semicolons in JS (QML)

2016-09-30 14:19 GMT+02:00 Kai Koehne : > To make a proposal: Let’s use semicolons in imperative JS parts of QML in > our examples and documentation. > > Apart from being on the safe side regarding some pathological cases, it > also makes the difference between declarative QML

Re: [Development] commas in ctor-init-lists

> Den 1. jun. 2016 kl. 15.06 skrev Mark Gaiser : > ... > Funny in the coding style you mention. For operators: "An operator at the end > of the line is easy to miss if the editor is too narrow." The exact same > could be said for commas at the end of the line. Silly point,

Re: [Development] New KDE Free Qt Foundation agreement and changes to Qt

2016-01-13 12:15 GMT+01:00 Knoll Lars : > Hi everybody, > The Qt Company has over the last days signed a new and updated agreement > with the KDE Free Foundation. With this new agreement come some adjustments > to the open source licensing of Qt. Basically LGPLv3 will

Re: [Development] Backwards compatibiltiy break in Qt 5.5

() or qUtf8Printable() on everyone who wants to keep human readable debug output sounds pretty evil, but having e.g. toHtmlEscaped() or a similar function doing the octa/hex thing could be better. -- Andreas Aardal Hanssen ___ Development mailing list

Re: [Development] Backwards compatibiltiy break in Qt 5.5

On 27 Jul 2015, at 21:14, Thiago Macieira thiago.macie...@intel.com wrote: On Monday 27 July 2015 21:50:15 NIkolai Marchenko wrote: Oh, but now you KNOW that it is a misspeled link to paypal. In real situation you won't have this forward knowlegde. The point is that I have all of the

Re: [Development] Container benchmark was HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

On 12 Jul 2015, at 16:58, Marc Mutz marc.m...@kdab.com wrote: That's because your benchmark runs entirely in L1. If you want to test containers of 10, 100, 1000 and 1 elements each, then make - one run over 1×N containers of 1 elements each, - one run over 10×N containers of 1000

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

On 10 Jul 2015, at 14:58, Marc Mutz marc.m...@kdab.com wrote: On Friday 10 July 2015 13:37:40 Andreas Aardal Hanssen wrote: QListQImage. You just proved my point. sizeof(QImage) sizeof(void*). If even you as a long-time Troll don't understand what QList actually does, there's a problem

Re: [Development] HEADS UP: Don't use QList, use Q_DECLARE_TYPEINFO

On 10 Jul 2015, at 14:24, Marc Mutz marc.m...@kdab.com wrote: That just goes to show how bad of an influence QList has. But it never hid its design, and, indeed, the default container in Qt 3 was QValueList, which actually *was* a doubly-linked list. Why Qt always nominates a list as the

Re: [Development] Fwd: QTextStream::readLine(0) is an ambiguous overload in 5.5

2015-05-18 14:56 GMT+02:00 Alejandro Exojo s...@badopi.org: El Monday 18 May 2015, Smith Martin escribió: You omitted that toInt(ok) is required to test ok for null, which is not required if ok is a reference. That's extra work in the implementation in order support a nicer API to the

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

2015-05-18 11:40 GMT+02:00 André Somers an...@familiesomers.nl: Andreas Aardal Hanssen schreef op 18-5-2015 om 11:35: Qt convention is to promote pointers for out parameters to make it immediately clear that your input can be modified. Out references, or non-const reference parameters

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

2015-05-18 11:10 GMT+02:00 Christian Kandeler christian.kande...@theqtcompany.com: On 05/17/2015 09:57 PM, Giuseppe D'Angelo wrote: On Sun, May 17, 2015 at 9:55 PM, Smith Martin martin.sm...@theqtcompany.com wrote: How do you get bitten by an out-reference? As usual, because at call

[Development] Fwd: QTextStream::readLine(0) is an ambiguous overload in 5.5

to what has always been the convention. Otherwise going through all Qt's api and changing it from pointers to references would be required. IMO. -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

2015-05-18 12:07 GMT+02:00 Julien Blanc julien.bl...@nmc-company.com: C++, you should resort to const-correctness to prevent mistakes. I like There is no const correctness in C++. #dontfeedthetroll #trymakingaconstcorrectlinkedlistinc++ -- Andreas Aardal Hanssen

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

++14? QString readLine(QString reuseThisStringsCapacity); The overload is unintuitive and the operation so complex that I would propose doing something different altogether. It's no longer a one-liner. It's not a good case for out parameters at all... -- Andreas Aardal Hanssen

Re: [Development] qtchooser (was: Re: Adding new third party component three.js to Qt?)

Sigh get a room (on irc fex) guys. Mailbox full already ;-). Andreas Aardal Hanssen Den 20. jan. 2015 kl. 17.08 skrev Thiago Macieira thiago.macie...@intel.com: On Tuesday 20 January 2015 11:28:10 Oswald Buddenhagen wrote: So no, don't tell us qtchooser is not meant to solve distros

Re: [Development] FTP in Qt5

On 08 Mar 2014, at 18:11, Thiago Macieira thiago.macie...@intel.com wrote: Em sáb 08 mar 2014, às 08:31:19, Tom Isaacson escreveu: There are no plans. FTP is really low-priority these days. Well we're still using it. Plus I said resume functionality for HTTP and FTP - I still think resume is

Re: [Development] Accepted flag of QGraphicsView::mouseMoveEvent is not updated

On 19 Jan 2014, at 16:34, Dmitrii Volosnykh dmitrii.volosn...@gmail.com wrote: Probably we may discuss it before make any unwanted bug reports... Basically, I have the same problems described in the referenced topic from URL. Specifically, I have a scene (tiles of geographic map) and an

Re: [Development] QWidget mouse events - different order

Why keep the breakage though. This fix would still require a note in porting docs and changes to code. Why fix what was never broken - just go back to Qt 4 behavior.. Sorry for the post format, crap mail client issue... ___ Development mailing list

Re: [Development] Howto know the Qt version in Qt source code

On 30 Dec 2013, at 09:31, Li Anthony anthony...@digia.com wrote: Hi, Maybe this is a silly question. But I always want to know the Qt version when I compile Qt from source code. Is there a version file or some easy way that I can find in source code? Thanks.

Re: [Development] [Request] Add Info to QDebug

On 23 Dec 2013, at 14:42, Thiago Macieira thiago.macie...@intel.com wrote: Fatal conditions affect not only the application, but also the surrounding system. The application and possibly the whole system should be shutdown immediately. A good example is loss of control of an X-ray beam in an

Re: [Development] [Request] Add Info to QDebug

On 23 Dec 2013, at 21:39, Kurt Pattyn pattyn.k...@gmail.com wrote: On 23 Dec 2013, at 17:38, development-requ...@qt-project.org wrote: From: Andreas Aardal Hanssen andr...@hanssen.name Subject: Re: [Development] [Request] Add Info to QDebug Date: 23 Dec 2013 15:17:06 GMT+1 To: development@qt

Re: [Development] QWidget mouse events - different order

On 20 Dec 2013, at 09:15, Martin Koller kol...@aon.at wrote: so it's just the extra mousePressEvent in Qt5 which is wrong. Good. I think it can and should just be removed, but it would be nice to know when it broke, in case there was thought behind it...

Re: [Development] QWidget mouse events - different order

On 19 Dec 2013, at 03:30, Nicolás Alvarez nicolas.alva...@gmail.com wrote: That would break many use cases, such as QSpinBox, which performs an action on every press (not release) and doesn't care about double click events. No it wouldn’t. The default implementation of mouseDoubleClickEvent()

Re: [Development] Qt's Leak-on-exit policy

On 19 Dec 2013, at 11:29, Tim Blechmann t...@klingt.org wrote: Should Qt clean-up dynamically allocated reachable pointers, or is this useless / pointless work? [snip] 2) static leak, which is when the pointer is overwritten at shutdown without being freed i wonder: what is the definition

Re: [Development] QWidget mouse events - different order

On 19 Dec 2013, at 18:36, Rick Stockton rickstock...@reno-computerhelp.com wrote: Perhaps we should perform as QT4 did (there wasn't a second ButtonPress, the DoubleClick ate it). Such use cases would then need to be fixed up (i,e, to accept EITHER event as a cause for executing that Action)?

Re: [Development] QWidget mouse events - different order

On 18 Dec 2013, at 22:07, Rayner Pupo Gómez rpgo...@uci.cu wrote: I've discovered that with Qt5 I get a different order of mouse events on a QWidget than with Qt4 (openSuse 13.1 Linux, X11): double clicking a widget results in Qt4 in: mousePressEvent mouseReleaseEvent

Re: [Development] Weird offseting in QDataStream

On 08 Nov 2013, at 10:15, Yves Bailly yves.bai...@sescoi.fr wrote: Le 08/11/2013 10:05, Giuseppe D'Angelo a écrit : See QDataStream::setFloatingPointPrecision. The default is double. That's pretty strange... what if I want to read a float then a double? do I have to switch between the two each

Re: [Development] Weird offseting in QDataStream

On 08 Nov 2013, at 11:32, André Somers an...@familiesomers.nl wrote: Eskil Abrahamsen Blomfeldt schreef op 8-11-2013 11:20 QDataStream supports reading and writing floats and doubles, but it might use more bytes than necessary to represent them in the stream. the main ... I don't see

Re: [Development] Weird offseting in QDataStream

On 08 Nov 2013, at 12:41, Yves Bailly yves.bai...@laposte.net wrote: ]I would recommend against using QDataStream for anything else than reading back what was written using QDataStream. This is what I called a step backward. It’s just stating a fact. QDataStream isn’t a generic

Re: [Development] QCommandLineParser

the translators got automatically loaded from standard paths, which means tr() can be used inside the qapp constructors. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Andreas Aardal

Re: [Development] Nominating Andreas Hanssen as Approver

/development -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Andreas Hanssen as Approver

to pay back some of the work you have all done to getting my stuff approved. Qt rocks! -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Help needed in 4.8 failing tests on Mac (QGraphicsProxyWidget and MacNativeEvents)

On Dec 29, 2012, at 3:10 PM, Thiago Macieira thiago.macie...@intel.com wrote: The following two tests have prevented 3 of the last 6 integration in 4.8, and that's 3 of 3 of the integrations that failed on Mac: These are consistent failures: they failed in 6 out of 6 runs: FAIL! :

Re: [Development] FW: how to improve GraphicsView performance

Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Partial screen updates with Scenegraph

is not that bad. The example of dragging an object around a screen without imposing full updates and complete redraws is logical. -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Partial screen updates with Scenegraph

2012/7/20 Uwe Rathmann uwe.rathm...@tigertal.de On 07/20/2012 12:32 PM, Andreas Aardal Hanssen wrote: Partial update support doesn't help for applications that don't _need_ it, rather. And high-end mobile phones where there's enough CPU and GPU power for the UI, which is the focus of QML 2

Re: [Development] Suggestion on QML portability

with QML 2 / SceneGraph; see pvr2d). -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Suggestion on QML portability

are 90% 2D. My point is simply that Qt 5 is best served with a painting backend for QML 2 that can support non-OpenGL technologies. -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman

Re: [Development] Suggestion on QML portability

for Qt 3, and this never caused any pain for anybody. Qt3Support was a well intended effort to either port classes that were dropped from Qt 3, or to wrap those around Qt 4 classes that provided the same functionality. Let's make use of the good experience this was in Qt 5 as well. -- Andreas Aardal

Re: [Development] Suggestion on QML portability

2012/7/16 Thiago Macieira thiago.macie...@intel.com On segunda-feira, 16 de julho de 2012 09.38.53, Andreas Aardal Hanssen wrote: In Qt 4 we added obsolete symbols for Qt 3, and this never caused any pain for anybody. Qt3Support was a well intended effort to either port classes

Re: [Development] QPixmap::fill( const QWidget *, ... )

some fancy blending code that feeds the widgets' own rendered output back into its painting code? -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] When to remove old platform plugins?

to debug GUI functionality on hardware that does not yet have display capabilites, and for remote debugging. It works, please don't remove it. -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org

Re: [Development] Changing qreal to a float

if this arrives twice to the list btw) -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Use make before you push and stage

While that it would be awesome to have a system which could compile test each uploaded patch set, and preferably have the results available before developers would review them, I think it something that will not scale; at least not without a system which can guarantee proper incremental

Re: [Development] Hacking guide for Qt's SSL Support

think the licensing looks very interesting. If OpenSSL does the job then why use GnuTLS? -- Andreas Aardal Hanssen ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development