Re: [Development] Request for early MOC support for C++20 Modules

On 2023-12-15, Elias Steurer via Development wrote: > No, I still need all the get/set/notify functions to change/get the > variables from the outside. There is currently no way to do that, or am > I missing something? Something like this >

Re: [Development] API style guide: scoped enum or not?

On 2023-05-04, Marc Mutz via Development wrote: > So, enum-backed APIs taking int will have to be ported to take the enum > instead. On the plus side, you get type-richer and safer APIs. How would you do the extensions (e.g. user roles or user events) if you convert to enums ? /Sune --

Re: [Development] API style guide: scoped enum or not?

On 2023-05-04, Marc Mutz via Development wrote: > that keeps unported code running. The main issue isn't the scoping, the > main issue will be the missing implicit conversion to underlying_type. In few cases the implicit conversion to underlying_type is kind of important. Especially in the

Re: [Development] Raising the minimum to C++20

On 2023-05-03, Thiago Macieira wrote: > 13, while Ubuntu 22.04 and Debian 11 (current stable) have GCC 11. Debian > will > probably release its next stable before Qt 6.7, though whether it'll still > upgrade from GCC 12 to 13 I don't know. When we released Qt 6.0, our minimum Debian 12

Re: [Development] Qt 6 co-installability with Qt 5

On 2020-11-17, Kai Köhne wrote: > Why should the packages in the online installer change? They are hardly ever > installed into some general directory. To have documentation be "Run this command `foo`". not "If you are running linux or mac and have gotten your Qt the normal way thru your

Re: [Development] Qt 6 co-installability with Qt 5

On 2020-11-02, Lars Knoll wrote: > I honestly don't think renaming all our binaries is an option, certainly not > that late in the process. We’ve had Qt 4 and Qt 5 co-installed for a long > time as well and while that might not be perfect it was working. > > And qtchooser has been working

Re: [Development] QList for Qt 6

On 2019-05-23, Lars Knoll wrote: I'm a bit late to this game, but ... > I don’t see why you’d want to remove the switch for Qt 6. > It would be a porting help for application developers. Application developers will not build their own Qt, but rely on the QList with the switch their Qt and

Re: [Development] Proposal: New branch model

On 2019-01-25, Lars Knoll wrote: > * I think it makes the life of casual/new contributors easier. Simply always > develop and push against the development branch. The more experienced > reviewer can then easily decide that the fix should be cherry-picked into a > stable branch. I'm mostly a

Re: [Development] QUIP 12: Code of Conduct

On 2018-10-28, Thiago Macieira wrote: > But if it isn't spam, what gives the list moderator the right to intervene in > something that he/she believes is abusive behaviour? Same thing about IRC: we > do have one annoying person who does come along every now and then, but most > of his messages

Re: [Development] Orphan modules

On 2018-09-12, Gatis Paeglis wrote: > +1 for deprecating qtx11extras as well and moving the code closer to actual > plugin. It is frustrating to have all that boilerplate code for 1 header file > - qx11info_x11.h I think it makes sense to have qtx11extras. A stable api and abi that X11 users

Re: [Development] Stepping down as maintainer

On 2018-03-19, Denis Shienkov wrote: > As I can see recently, is is not a good tendence in Qt... Many peoples > leaves from Qt.. What happens? Or I'm mistake? :) Let's do some math. There is around 160 maintainer positions in Qt (a quick count of on the maintainers

Re: [Development] syncqt.pl in C++

On 2017-03-08, Jake Petroules wrote: > I'm working on the qbs bootstrapping. The requirements will be: a C++11 com= > piler. End of requirements. Seriously. Not even bash, if you don't mind typ= > ing a couple commands manually. I don't mind a bat script, a bash script or

Re: [Development] syncqt.pl in C++

On 2017-03-07, Lars Knoll wrote: > This also makes qbs a natural choice to also use for Qt itself, and I belie= > ve all the people that have worked and maintained Qt's build system over th= > e last few years are supporting this. Of course this requires that we can s= > how

Re: [Development] Calendar Systems proposal

On 2016-12-17, Soroush Rabiei wrote: > it's wrong to add such implementation to QDate. My view of QDate is this: > QDate represents a day in time. So it only needs to know what day it is > (how many days are to the day 0). And it is exactly things like that that would

Re: [Development] Calendar Systems proposal

On 2016-12-15, Soroush Rabiei wrote: > 2.History > Hi I would welcome more calendar systems. Personally I hope for french revolutionary calendar. Because it is funny. I think you need to touch quite some of the 'inner bits' of date / time, and while you are there,

Re: [Development] Should QVariant be doing fuzzy comparisons on doubles?

On 2016-09-23, André Pönitz wrote: > That gives already "surprising" behaviour if fed with QChar('a') and > QString("a") in a row. > > And it is "surprising" to a degree that I'd call it buggy. Then try feeding it boolean's and strings. QQmlPropertyMap map;

Re: [Development] Qt 5.8 API review (vs 5.7.0)

On 2016-09-09, Edward Welbourne wrote: > https://codereview.qt-project.org/170634 -- qtbase Added some comments. Though didn't detailed read all template magic. One enum have reordered some members. This is likely an issue. > https://codereview.qt-project.org/170635 --

Re: [Development] Notes on QtCore session @ QCS2016

On 2016-09-05, Giuseppe D'Angelo wrote: >> * C++ ABI >> * libstdc++ still breaking compatibility in std::function >> * not now, revisit in a year or two > > There hasn't been time to discuss this at QtCon, but I'd say we should > not spend another year before

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

On 2016-09-05, Andrew Knight wrote: > tl;dr: Lots of discussion on the merits of which build system (CMake, > Qbs) should replace qmake in building Qt; lots of supporters of CMake > but no volunteers to do the work, many reasons to use Qbs as well. Some I do think

Re: [Development] Would it make sense to make QObject moveable in Qt 6?

On 2016-08-24, Thiago Macieira wrote: > And its address is copyable, so if we replaced the pointer with something, > we'd have to use something copyable and non-owning. class QObjectHandle { public: QObjectHandle(QObject* obj) : m_obj(obj) { }

Re: [Development] New repository for QtOAuth

On 2016-08-12, Fredrik de Vibe wrote: > We have recently been working on an implementation of OAuth (1+2), and > this is now approaching a state in which it can be distributed as a tech > preview. For this we'll need a new public repository. there is a handful of external

Re: [Development] leak in QMetaObject?

On 2016-07-14, Thomas Senyk wrote: I see neither one nor the other. I see continues 100% consume with no memory consumption drop what so ever. > should "fix" it? .. but I still see 100% cpu and same memory consumption? I debugged some time ago a case of a

Re: [Development] QImage::transformed returns shallow copy for QTransform::TxNone matrix type.

On 2016-07-11, Allan Sandfeld Jensen wrote: > On Monday 11 July 2016, Benjamin TERRIER wrote: >> QImage::detach() is not public API. >> However QPixmap::detach() is, so why QImage::detach() couldn't be made >> public too? >> > It probably should be. It is a lot more sensible

Re: [Development] Use of Standard Library containers in Qt source code

On 2016-07-01, Thiago Macieira wrote: > confusing because the next line has "isEmpty". When I read this code, I had > to > wonder if that "empty" was a verb in the imperative, meaning the author was > trying to remove all elements from the container. Hah. I found

Re: [Development] Can we use std::unique_ptr in Qt base/modules sources since Qt5.7 ?

On 2016-06-14, Konstantin Tokarev wrote: > QScopedPointer lacks custom deleters which make it unusable for the purpose > of managing Windows HANDLEs (see original post). You can pass your own classes as handlers, provided that they have a public static function void cleanup(T

Re: [Development] QTBUG-52360: is ARMv5 still supported?

On 2016-04-05, Thiago Macieira wrote: > If it is, can someone try a regular toolchain for that platform with Qt 5.6 > and report whether QtCore links? I'd like a second opinion with a different > toolchain than the reporter. looks like 5.6 is built in

Re: [Development] gerrit : pointers to use it cleverly/efficiently?

On 2016-03-29, René J.V Bertin wrote: > Can someone point me in the right direction, maybe to a tutorial of sorts > that outlines how to do several code reviews from a single working copy? > > I'm not exactly familiar with using branches; I just tried to create one, >

Re: [Development] debug symbols for official Qt releases

On 2016-03-01, Milian Wolff wrote: > b) Apparently there are never any debug symbols shipped for the release build > fo Qt. Having debug symbols even for a release build is crucial for a good > profiling experience. Could we maybe get release builds in the future with - >

Re: [Development] API/ABI changes report

On 2016-02-11, Thiago Macieira wrote: >> There are several remaining issues in the report. So I have some questions: >> >> - Is class QPlatformScreen private and all related changes should be removed >> from the report? >>

Re: [Development] A simple analysis of apps using qtbase's private headers

On 2016-02-02, Liang Qi wrote: > Above three are not applications, they must be input context plugin of Qt, > just like ibus in > https://github.com/qtproject/qtbase/tree/5.5/src/plugins/platforminputconte= > xts/ibus > . Normally every input method software could/should

Re: [Development] Fwd: A simple analysis of apps using qtbase's private headers

On 2016-01-22, Lisandro Damián Nicanor Pérez Meyer wrote: > On Friday 22 January 2016 18:09:55 NIkolai Marchenko wrote: >> Speaking of workarounds : >> I have to use this ugly hack that depends on otherwise inaccessible c= > ode to >> update QPrintPreviewDialog >>=20 >>

Re: [Development] Qt 5.6.0 header diff: QtCore.diff

On 2015-09-17, Frederik Gladhorn wrote: > --- a/src/corelib/tools/qbytearray.h > +++ b/src/corelib/tools/qbytearray.h > @@ -43,6 +43,7 @@ > #include >=20 > #include > +#include >=20 > #ifdef truncate > #error qbytearray.h must be included before any

Re: [Development] Request to delete libibusplatforminputcontextplugin.so from qtbase

On 2015-07-17, Takao Fujiwara tfuji...@redhat.com wrote: Right. ibus-qt already has the ibus module for qt4 so this request is for qt5. I'd think it's easy to move libibusplatforminputcontextplugin.so from qtbase to ibus-qt. Part of me would like to have as many things that uses QPA headers

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

On 2015-07-12, Andre Somers an...@familiesomers.nl wrote: become easier to make the transition in user code? Then, if Qt itself changes its API in Qt 6 to use QVector instead of QList, the users' code will just work :-) In Qt6, QList can be fixed. The issue is what to do until then. /Sune

Re: [Development] The dark side of QtMultimedia - strikes back

On 2015-07-05, Massimo Callegari massimocalleg...@yahoo.it wrote: Update #2 (sorry for spamming) I patched qgstreamervideowindow.cpp and qgstreamervideowidget.cpp to support the linuxfb platform. It kinda works !! Screenshot here: http://pasteboard.co/1JlYRT9l.jpg Videos can be played

Re: [Development] Qt LTS C++11 plans

On 2015-06-26, Olivier Goffart oliv...@woboq.com wrote: Can we have function that takes or return std::function, std::tuple, std::unique_ptr, std::vector? While I can see the advantage of std::function, I'm not sure why we would use the remaining ones in API ? Thiago already mentioned that he

Re: [Development] Item View Maintainer

On 2015-03-01, Samuel Gaist samuel.ga...@edeltech.ch wrote: Hi, Since Stephen Kelly ended his work at KDAB, he also got out of gerrit/jira so it seems that there's no official maintainer for the Item View module, unless he's there with a new account I missed ? I spotted him some time ago

Re: [Development] license question, bds 4 clause license text in qtbase\src\corelib\tools\qdatetime.cpp qt5.4.1 found

On 2015-02-28, Gunnar Roth gunnar.r...@gmx.de wrote: UC writes BSD Unix files not about general source code. I don't think that UC has published anything else but BSD Unix. And why does gnu,org not update their website,but till insists on incompatibility with the GNU GPL? In the general

Re: [Development] qt-4.8.x gcc5 version/detection issues

On 2015-02-16, Rex Dieter rdie...@math.unl.edu wrote: * QT_BUILD_KEY handling Similar to webkit above, the configure bits about QT_BUILD_KEY only handles up to gcc-4.x. For fedora 22, our gcc5 builds are done in a way that is (supposedly) ABI compatible to gcc4, so I'm currently using:

Re: [Development] qt-4.8.x gcc5 version/detection issues

On 2015-02-16, Rex Dieter rdie...@math.unl.edu wrote: From my reading of http://developerblog.redhat.com/2015/02/10/gcc-5-in-fedora/ It may depend on the value of _GLIBCXX_USE_CXX11_ABI macro, but I admittedly don't yet fully grasp the implications of it being set either way. Yes. it does

[Development] Reproducible Qt ; the purpose of QLibraryInfo::buildDate

Hi After a couple of patches [1], most submitted to gerrit, my current qtbase dev build on linux is bitwise reproducible. This is the first step to let end users check that the binaries they recieve actually matches the sources they recieve. The first simple steps is 1) ensure __DATE__, __TIME__

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

On 2015-01-19, Oswald Buddenhagen oswald.buddenha...@theqtcompany.com wrote: your problem is a self-made one: the attempt to co-install major versions of everything. this is a linux distro specific problem, and demanding x-platform upstreams to accept trade-offs to adjust to it is

Re: [Development] changing Q_GADGET

On 2014-11-28, Simon Hausmann simon.hausm...@theqtcompany.com wrote: I feel that Q_GADGET has its primary use with structures and the default access level for those is public. I find it awkward that you currently have to write: I have a lot of code in the wild using classes and Q_GADGET.

Re: [Development] Contribution proposal: Dispatcher class

On 2014-09-24, Yam Marcovic ymar...@gmail.com wrote: However, I will say I don't want to force people to give their sources away if they use it. So a license along the lines of 'this license is here for formal purposes; but feel free to do anything you want with this,' is good enough as far

Re: [Development] QtMultimedia and Musepack

On 2014-08-26, Allan Sandfeld Jensen k...@carewolf.com wrote: Well. That would the safe way, and we should keep that in mind for Qt6, but I believe with symbol versioning it can be done without breaking ABI, assuming it works as advertised. The libraries would export all symbols as both their

Re: [Development] Multimedia support.

On 2014-08-20, Thorvaldur Jochumsson jochums...@gmail.com wrote: Hi I am currently designing multimedia support for my application. I am wondering which approach to take. Should I make use of the phonon library or make use of the multimedia support provided in the Qt multimedia library? We are

Re: [Development] Private Qt helper libraries?

On 2014-07-03, Milian Wolff milian.wo...@kdab.com wrote: I imagine, it could work by create just a normal library but not install and public headers, only private ones. That should be OK then, or what do you think? We have too many private headers already. We should work on getting rid of

Re: [Development] Proposal: All Qt modules must use the same version number

On 2014-06-30, Olivier Goffart oliv...@woboq.com wrote: Totally off topic: I think using private header should be tried to be avoided. In the past, we used private header inside Qt because Qt was not split that much. But one of the goal of modularisation was to allow independent release

Re: [Development] Proposal: All Qt modules must use the same version number

On 2014-06-30, Olivier Goffart oliv...@woboq.com wrote: We need also to identify private APIs that could be polished and made public. The first step here is, from your friendly packagers POV, the QPA API's. One thing is that we need to be very careful with combining the components released by

Re: [Development] Adding support for version number comparisons

On 2014-05-09, Keith Gardner kreios4...@gmail.com wrote: 2. What semantics should be used for version comparisons? Numerical segments are more clearly defined but when introducing a non-null suffix, many different methods are being proposed. 3. Are there any other versioning

Re: [Development] Adding support for version number comparisons

On 2014-05-10, Thiago Macieira thiago.macie...@intel.com wrote: How do you make 5.3.0-rc1 compare less than 5.3.0? we call them 5.3.0~rc1. /Sune ___ Development mailing list Development@qt-project.org

Re: [Development] Qt 5.3 header diff

On 2014-04-23, Andrey Ponomarenko aponomare...@rosalab.ru wrote: I've created the ABI compatibility report between 5.2.1 and 5.3.0-beta versions: http://upstream-tracker.org/compat_reports/qt/5.2.1_to_5.3.0-beta/abi_compat_report.html Hope it may be helpful to analyse changes in headers.

Re: [Development] Qt 5.3 header diff: QtLocation

On 2014-04-22, Thiago Macieira thiago.macie...@intel.com wrote: -QGeoCodingManagerEngine(const QMapQString, QVariant parameters, QObject *parent = 0); +QGeoCodingManagerEngine(const QVariantMap parameters, QObject *parent = 0); Given it is just changes to typedefs, it should be

Re: [Development] Qt 5.3 header diff: QtNetwork

On 2014-04-22, Thiago Macieira thiago.macie...@intel.com 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

Re: [Development] Qt 5.3 header diff: QtSerialPort

On 2014-04-22, Thiago Macieira thiago.macie...@intel.com 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

Re: [Development] Qt 5.3 header diff: QtWidgets

On 2014-04-22, Thiago Macieira thiago.macie...@intel.com wrote: --- a/src/widgets/widgets/qlcdnumber.h +++ b/src/widgets/widgets/qlcdnumber.h @@ -43,7 +43,6 @@ #define QLCDNUMBER_H #include QtWidgets/qframe.h -#include QtCore/qbitarray.h QT_BEGIN_NAMESPACE I guess this is

Re: [Development] How to write a ChangeLog entry

On 2014-01-20, Thiago Macieira thiago.macie...@intel.com wrote: Windows --- [QTBUG-35500] Fix printing on Windows. QPrinter now reports proper page sizes for system printers. (I would like another sentence about the actual implications. For me, it was that my custom printing code went from

Re: [Development] How to write a ChangeLog entry

On 2014-01-20, Thiago Macieira thiago.macie...@intel.com wrote: On segunda-feira, 20 de janeiro de 2014 21:30:37, Sune Vuorela wrote: On 2014-01-20, Thiago Macieira thiago.macie...@intel.com wrote: Windows --- [QTBUG-35500] Fix printing on Windows. QPrinter now reports proper page

Re: [Development] moving some SystemInfo stuff into qtbase (was Re: QtDriveInfo module in Playground)

On 2014-01-13, David Faure david.fa...@kdab.com wrote: Mounting can still be done with `mount`, no? Only in rare cases. Normally on linux from a user app you would call out to udisks, who would connect to polkit and have polkit maybe query you and other magic. Notifications mean listening to

Re: [Development] The Software shall be used for Good, not Evil statement in Qt sources

On 2013-12-18, Ziller Eike eike.zil...@digia.com wrote: On Dec 18, 2013, at 5:35 PM, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: Hi! I would like to now if it's acceptable for the project to have 3rd party code with the following statement in 3rd party sources: The

Re: [Development] Removing libudev dependency from binary packages?

On 2013-10-21, Thiago Macieira thiago.macie...@intel.com wrote: Anyway, my suggestion thus: - QtSerialPort: statically link to libudev btw, does anyone know how close the libudev version should match the udev-daemon version? are there any library/daemon protocol stability guarantees? What

Re: [Development] Removing libudev dependency from binary packages?

On 2013-10-21, Thiago Macieira thiago.macie...@intel.com wrote: But what distributions are those that don't have libudev.so.0? Most modern ones I think. http://git.kernel.org/cgit/linux/hotplug/udev.git/tree/Makefile.am Note that udev in general is built from systemd source tree, even for

Re: [Development] A QtCore class for event-driven jobs

On 2013-09-09, Giuseppe D'Angelo dange...@gmail.com wrote: Indeed, but how about starting with an addon and then moving the classes inside QtCore? We can freely break API/ABI in addons -- when things get stabilized, we start including them in QTCore/QtNetwork... I'm not sure what a addon

Re: [Development] Cleaner code base patches

On 2013-01-28, Knoll Lars lars.kn...@digia.com wrote: 1) always with -developer-build 2) on by default on -developer-build, but the CI disables it 3) completely optional, CI enables it 4) completely optional, not enabled by the CI I'd favor (2) for now, and move over to (1) once we gained a

Re: [Development] Cleaner code base patches

On 2013-01-28, Thiago Macieira thiago.macie...@intel.com wrote: I'd rather skip that step and simply go to -Werror. Lars proposed that we experiment with it a little and see how far it goes before turning it on. The good thing about -Werror is that the failure comes fast. The bad thing about

Re: [Development] QtMultimedia BIC / header cleanliness issue

On 2013-01-22, Thiago Macieira thiago.macie...@intel.com wrote: Sune, especially for you: will you try and patch Qt to change the sonam= e if we=20 don't do it? Sorry for answering a bit late. Given that we haven't yet formally published Qt5, no. if we had, then it would be a definately

Re: [Development] RFC: What constitutes a non-destabilising bug-fix?

On 2012-12-09, Sune Vuorela nos...@vuorela.dk wrote: On 2012-12-09, Marc Mutz marc.m...@kdab.com wrote: 3. new features and bug-fixes that require new strings or BiC changes should be submitted to 'dev' directly. binary incompatible changes should not be submitted anywhere except for Qt6

Re: [Development] Qt5/Qt Quick 2 with C#

On 2012-11-28, Labs, Torsten torsten.l...@siemens.com wrote: Hello, does anybody know something about a possiblity to use C# for programming Qt= 5 and Qt Quick? I know this sounds funny :-) I would expect the people behind Qyoto (Qt4 mono bindings) will move on to Qt 5 sometime in the

Re: [Development] Is QtConcurrent's code generator still in use?

On 2012-11-14, Christian Kandeler christian.kande...@digia.com wrote: On 11/14/2012 12:17 PM, Sorvig Morten wrote: QtConcurrent is done. The implementation is not good enough to be used as a base for further development. Can you be a bit more specific? What are the general problems and why

Re: [Development] Pending decisions on co-installation

On 2012-10-30, Thiago Macieira thiago.macie...@intel.com wrote: 1) QML environment variables The variable for import paths has been versioned from QML_IMPORT_PATH to QML2_IMPORT_PATH. But I have not changed any of the other variables. We need a decision from the team familiar with the

Re: [Development] Pending decisions on co-installation

On 2012-10-31, Poenitz Andre andre.poen...@digia.com wrote: This is not about overriding someone. This is about ranking the user experience of the majority of users higher than the convenience of a handful of Linux distribution packagers - half which will do their own renaming anyway, no

Re: [Development] Summary of renaming changes

On 2012-10-19, Alberto Mardegan ma...@users.sourceforge.net wrote: 3) Provide a script to switch, per user and maybe even per $PWD, what version of Qt /usr/bin/qmake should generate the makefiles for. I have, as a distributor, frequently gotten 'hate' in #qt for providing switchable qmakes.

Re: [Development] Summary of renaming changes

On 2012-10-19, Poenitz Andre andre.poen...@digia.com wrote: User support could then be: write qmake5 to build Qt 5 things no. it would be if you compiled Qt yourself or if you downloaded the built editions from digia, write qmake to build things. if you gotten from your linux distribution

Re: [Development] Summary of renaming changes

On 2012-10-19, André Pönitz andre.poen...@mathematik.tu-chemnitz.de wrote: Really. I really want, both as a Qt contributor and a Qt packager to ship a pristine Qt. Please help me make it happen. Demanding to be relieved from that burden is one thing. Demanding to use an approach that will

Re: [Development] Summary of renaming changes

On 2012-10-18, Giuseppe D'Angelo dange...@gmail.com wrote: The following are user applications and they have not and will not be renamed: qdbus qdbusviewer assistant designer linguist creator pixeltool I would remove creator from