Re: [Development] New approach to hi-dpi and coordinate system for layouts in Qt 6

> making it impossible to specify 'a one/two pixel border' Correct me if I am wrong, but isn't this what QPen::setCosmetic is used for ? Best, Jean-Michaël --- Jean-Michaël Celerier http://www.jcelerier.name On Thu, Sep 21, 2017 at 11:37 AM, Stephen Kelly via Development < developm

Re: [Development] Seeking advise using git and code review

set of changes > How could I find reviewers for my changes to QTextDocumentWriter? https://wiki.qt.io/Maintainers you can also come and ask on IRC Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Wed, Oct 4, 2017 at 8:55 AM, Daniel Savi <daniel.s...@gaess.ch> wro

Re: [Development] QtCS 2017 QtCore sessions

> (4x difference measured). wow, good to know. --- Jean-Michaël Celerier http://www.jcelerier.name On Tue, Oct 10, 2017 at 3:33 PM, Thiago Macieira <thiago.macie...@intel.com> wrote: > On Tuesday, 10 October 2017 15:04:29 CEST Jean-Michaël Celerier wrote: > >

Re: [Development] QtCS 2017 QtCore sessions

where people don't want to bring large stuff like whole QtCore but where a few headers are OK imho; offering facades to std:: types with easy, readable Qt-like APIs would also be quite nice (ideally with a set of standard-compliant typedefs, eg qt::hash_map... one can dream :p). Best, --- Jean-M

Re: [Development] Future of QBS

> nobody is going to port Qt to CMake (if you disagree start a new thread) https://plus.google.com/+AaronSeigo/posts/fWAM9cJggc8 > a complete CMake build for Qt was already contributed upstream (quite some time ago) .. and rejected .. --- Jean-Michaël Celerier http://www.jcelerie

Re: [Development] Qt and IoT infographic

, expositions, etc. which generate revenue all the same, for the artists, museums, etc. and need programmers to get the stuff running and banging sound. --- Jean-Michaël Celerier http://www.jcelerier.name On Tue, Aug 29, 2017 at 9:05 PM, Thiago Macieira <thiago.macie...@intel.com> wrote

Re: [Development] [fix]: Assistant (and others) burning CPU because of #f27d1ccbb24ec2fd4098f2976503478831006cc8 ?

tps://stackoverflow.com/questions/24142450/qtimersingleshot-and-qmetamethodinvoke Best Jean-Michaël --- Jean-Michaël Celerier http://www.jcelerier.name On Wed, Aug 30, 2017 at 11:31 AM, Giuseppe D'Angelo < giuseppe.dang...@kdab.com> wrote: > Il 30/08/2017 11:28, Morten Sørvig ha scritto: > &

Re: [Development] Pointer Handlers will be Tech Preview in 5.10

Why not just Drag, Tap, Pinch ? (for Drag it'd have to be in a different namespace than the actual QtQuick.Drag though) Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Wed, Sep 27, 2017 at 7:56 PM, J-P Nurmi <jpnu...@qt.io> wrote: > On 27 Sep 2017, at 17:35, Shawn

Re: [Development] Qt and IoT infographic

ike QIODevice. Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Thu, Aug 24, 2017 at 11:00 PM, Thiago Macieira <thiago.macie...@intel.com > wrote: > Re the inforgraphic at > https://info.qt.io/whitepaper-building-the-internet-of-things > (not the paper because it's as

Re: [Development] Qt and IoT infographic

cially supported so it can be used for UI in browsers*, and, +1 * 1 or merge the webassembly patches ( https://codereview.qt-project.org/#/c/178543/), whatever, but it would be so good to run Qt apps in client side web browser Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Mo

Re: [Development] Qt and IoT infographic

QML without QtQuick. * apparently QQuickWindow has some ties to the QML engine but in my experience you can just create new QQuickItem from c++ and add them as child of the rootItem and it works. --- Jean-Michaël Celerier http://www.jcelerier.name On Mon, Aug 28, 2017 at 9:26 PM, Jason H

Re: [Development] Qt and IoT infographic

tps://www.postscapes.com/javascript-and-the-internet-of-things/ which are now more and more used. Hell, sometimes people use python of all languages on constrained CPUs. It's a niche that Qt *could* fill, and fill better than the alternatives. --- Jean-Michaël Celerier http://www.jcelerier.n

Re: [Development] QtCS 2017 QtCore sessions

99% compatible to what's in std. --- Jean-Michaël Celerier http://www.jcelerier.name On Sun, Dec 3, 2017 at 5:41 PM, Alejandro Exojo via Development < development@qt-project.org> wrote: > On Saturday 02 December 2017 19:11:23 Boudewijn Rempt wrote: > > > > And, c'

Re: [Development] QtCS 2017 QtCore sessions

> (just look at how we have to build Linux binaries with GCC 4.8). Isn't it possible to use a newer GCC but to tell it to use GCC 4.8's ABI ? eg to target GCC 4.8, by using -fabi-version=2 -D_GLIBCXX_USE_CXX11_ABI=0 Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Fri, De

Re: [Development] Repository request: MaterialWidgets

dgets" and be happy forever after. For instance here are some already existing styles that you can find on the internet for widgets: https://github.com/diversys/QtHaikuStyle https://github.com/suratovvlad/libqdark Best, Jean-Michaël --- Jean-Michaël Celerier http://www.jcelerier.name On Mon, Oc

Re: [Development] Repository request: MaterialWidgets

of the Material set implemented in QML : https://github.com/papyros/qml-material . Maybe you could reuse some algorithms / painting code used there ? Best, Jean-Michaël Celerier http://www.jcelerier.name On Mon, Oct 30, 2017 at 10:44 AM, iman ahmadvand <iman72...@gmail.com> wrote: > Hi Jea

Re: [Development] QTBUG-43096 - QML instantiation performance decadence

tty QQC2 ones :p Even the latest innovation, QML Shapes, is beaten in performance by existing solutions : http://kgronholm.blogspot.fr/2017/12/qt-510-rendering-benchmarks.html that in addition also provide a C++ API. --- Jean-Michaël Celerier http://www.jcelerier.name On Fri, May 25, 2018 at 9

Re: [Development] QTBUG-43096 - QML instantiation performance decadence

> Jędrzej had a beautiful proof of concept at some point for QObject to combine the object and d-pointer allocation into one. If only there was a way to be able to use Qt without all the PIMPLing and just have QObjectPrivate be a "normal" QObject member ! --- Jean-Michaël

Re: [Development] RFC: unified data model API in QtCore

-- Jean-Michaël Celerier http://www.jcelerier.name On Thu, Jun 14, 2018 at 3:13 PM, Thiago Macieira wrote: > On Wednesday, 13 June 2018 23:46:54 PDT Lars Knoll wrote: > > I’d leave XML out of this. It is difficult to integrate, as it has so > many > > special features (entitie

Re: [Development] QTBUG-43096 - QML instantiation performance decadence

you want, like QStringLiteral :p --- Jean-Michaël Celerier http://www.jcelerier.name On Sat, May 26, 2018 at 3:17 PM, Thiago Macieira <thiago.macie...@intel.com> wrote: > On Saturday, 26 May 2018 09:12:25 -03 Jean-Michaël Celerier wrote: > > If only there was a way to

Re: [Development] clang-format

> I never seen anything QtCreator had trouble with. really ? paste this in a .cpp and indent it : #define WHATEVER struct foo { WHATEVER public: explicit foo(); }; struct bar { public: explicit bar(); }; --- Jean-Michaël Celerier http://www.jcelerier.name On Wed, Jun

Re: [Development] about the Cocoa/Freetype fontengine

are running) Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Sat, Dec 30, 2017 at 1:45 PM, René J. V. Bertin <rjvber...@gmail.com> wrote: > Nikolaus Waxweiler wrote: > > > I think you have to carefully match the rendering of CoreText (and its' > > dar

Re: [Development] Undeprecating QString::null

> The "just change" introduces a binary incompatibility - right ? I don't think it does: the QString is constructed on the caller's side anyways and your function is always passed a QString object; if you had an app that linked to qwt and didn't recompile it will just keep calling QString::null()

Re: [Development] Deprecation of Qt Quick Controls 1

properties, that is, properties that would apply to whole subtrees of QML components easily. Ableton has graciously provided some code for this : https://github.com/Ableton/aqt-stylesheets but it would be nice to have a syntaxic solution part of Qt proper... Best, --- Jean-Michaël Cel

Re: [Development] about the Cocoa/Freetype fontengine

:+1: for being able to use fontconfig everywhere. It's painful to have to make pixel adjustments on each platform because they don't render fonts exactly the same everywhere. Besides, fontconfig with infinality patches honestly gives a beautiful rendering, crispier and yet fuller than everything

Re: [Development] Qt 6 buildsystem support requirements

> I would say the only two options in the running are qbs and CMake. About this, I don't know if C++ community acceptance is a criterion, but : https://github.com/search?q=cmake https://github.com/search?q=qbs On Tue, Jul 31, 2018 at 4:41 PM, Thiago Macieira wrote: > On Monday, 30 July

Re: [Development] Apparently dead code: GPU_BLACKLIST and friends

p=1=QTEST_ADD_GPU_BLACKLIST_SUPPORT_DEFS=Code --- Jean-Michaël Celerier http://www.jcelerier.name On Wed, Aug 8, 2018 at 1:23 PM Edward Welbourne wrote: > Hi all, > > I notice that QTest includes support, in [0], alongside its BLACKLIST > files for problematic tests, for a GPU_BLACKLIST file; there

Re: [Development] Qt 6 buildsystem support requirements

> How much custom c++ code does it contains for just qt? which build system which supports automatic calling of moc doesn't have specific code for qt ? --- Jean-Michaël Celerier http://www.jcelerier.name On Sat, Jul 21, 2018 at 3:48 PM, Ray Donnelly wrote: > As someone who

Re: [Development] Qt 6 buildsystem support requirements

? If anything, CMake's automoc is in my experience much faster to process the whole repo. Richard: so what's this then ? https://github.com/qbs/qbs/blob/2d1de8cc84b258174b2dc0a8080f549cd9b59b32/src/lib/corelib/buildgraph/qtmocscanner.cpp --- Jean-Michaël Celerier http://www.jcelerier.name

Re: [Development] Qt 6 buildsystem support requirements

: http://mesonbuild.com/Qt5-module.html or https://scons.org/doc/2.0.1/HTML/scons-user/a8524.html --- Jean-Michaël Celerier http://www.jcelerier.name On Sat, Jul 21, 2018 at 7:07 PM, Ray Donnelly wrote: > On Sat, Jul 21, 2018 at 4:42 PM, Jean-Michaël Celerier > wrote: > > That's f

Re: [Development] Qt 6 buildsystem support requirements

oject(foo CXX)\nset(CMAKE_CXX_STANDARD 17)\nadd_executable(foo main.cpp)' > CMakeLists.txt results for me in correct completion of std::string_view in qtc. --- Jean-Michaël Celerier http://www.jcelerier.name On Sun, Jul 22, 2018 at 12:57 PM, Иван Комиссаров wrote: > > 21 июля 20

Re: [Development] Qt 6 buildsystem support requirements

ld be so much to gain with a better relationship between Qt and CMake. Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Sat, Jul 21, 2018 at 2:42 PM, Kevin Kofler wrote: > Bogdan Vatra via Development wrote: > > Anyway IMHO is more important to have a clean, nice an

Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration

For this kind of work I'd recoment QNanoPainter, it's another Qt paint engine built on top of modern openGL, very efficient for what you want (polylines) : https://github.com/QUItCoding/qnanopainter Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Sun, Sep 2, 2018 at 2:45 PM Uwe

Re: [Development] Dark mode, palettes, styles etc.

wse/cat/123/) ; it would be nice to have it integrated to Qt directly maybe ? And then use a GPU-based SVG renderer to only have to do the GPU work once (how far is QtQuick.Shapes from rendering full-fledged SVG ?). Best, Jean-Michaël --- Jean-Michaël Celerier http://www.jcelerier.name On

Re: [Development] #pragma once

, Clang, GCC, ccache, distcc and Icecream... --- Jean-Michaël Celerier http://www.jcelerier.name On Wed, Jan 24, 2018 at 11:34 AM, Mitch Curtis <mitch.cur...@qt.io> wrote: > > > > -Original Message- > > From: Ville Voutilainen [mailto:ville.voutilai...@gmail.

Re: [Development] GSoC 2018 Idea: a widget for 2D/3D image display

tml/classQVTKWidget.html --- Jean-Michaël Celerier http://www.jcelerier.name On Tue, Mar 13, 2018 at 2:39 PM, 孫夏 <hsia@gmail.com> wrote: > Hello all, > > I am a student interested in participating in Google Summer of Code 2018 > with Qt. > > As a Qt user before, I used Qt as

Re: [Development] Stepping down as maintainer

discourage newcomers. Best, Jean-Michaël --- Jean-Michaël Celerier http://www.jcelerier.name On Tue, Mar 20, 2018 at 10:35 AM, Denis Shienkov <denis.shien...@gmail.com> wrote: > Hi. > > Maybe, you can to consider some "yum-yum" for attraction of community

Re: [Development] Rendering only items that are visible in Qt Quick

> Far superior alternatives? Maybe not "far" superior, but AFAIK QGraphicsScene / QGraphicsView handles this. --- Jean-Michaël Celerier http://www.jcelerier.name On Fri, Mar 23, 2018 at 2:44 PM, Mitch Curtis <mitch.cur...@qt.io> wrote: > I'd like to get some d

Re: [Development] Improving CMake support for static builds

pkg-config files are generated by a perl script, maybe the same could be used for static builds ? --- Jean-Michaël Celerier http://www.jcelerier.name On Fri, Oct 12, 2018 at 9:12 PM Kyle Edwards wrote: > Hello everyone, > > New Qt developer here. I'm trying to improve Qt's suppor

Re: [Development] Build system for Qt 6

Especially considering that the person proposing the change is working at google which is where GN comes from. There's some conflict of interest here. On 01/11/2018 12:13, André Pönitz wrote: On Thu, Nov 01, 2018 at 08:34:34AM +, Simon Hausmann wrote: >From the same email perhaps it's

Re: [Development] Build system for Qt 6

https://github.com/openframeworks/openFrameworks/tree/patch-release/libs/openFrameworksCompiled/project 30 окт. 2018 г., в 22:14, Jean-Michaël Celerier <mailto:jeanmichael.celer...@gmail.com>> написал(а): OpenFrameworks, a fairly used creative coding framework has been using QBS for a

Re: [Development] Build system for Qt 6

://forum.openframeworks.cc/t/qtcreator-v4-3-1-qbs-problem/27214), so multiple people I know have ended up porting OF to use CMake instead : https://github.com/ofnode/of which frankly worked better and with less breakage. As always, mileage may vary. --- Jean-Michaël Celerier http://www.jcelerier.name

Re: [Development] Build system for Qt 6

ub.com/hioa-cs/IncludeOS). iOS is curerntly best supported (imho) through https://github.com/ruslo/polly which is a set of toolchains not unlike qmake's mkspecs. --- Jean-Michaël Celerier http://www.jcelerier.name On Tue, Oct 30, 2018 at 12:24 PM Christian Gagneraud wrote: > > >

Re: [Development] Build system for Qt 6

why not just go and propose the declarative QBS syntax as a front-end for CMake ? This would make the world a better place. The CMake people *want* a better language, and for these use cases, QML is certainly much closer to the solution than others. --- Jean-Michaël Celerier http://www.jcelerier.n

Re: [Development] Build system for Qt 6

> Does pkg-config and cmake works on Qnx and Windows? Can you cross > compile for iOS, tvOS, ... using CMake? > Has it been ever tried once? Seriously, it's a google search away: https://github.com/leetal/ios-cmake > CMake doesn't support (very well) cross-compilation for android on > Windows

Re: [Development] Missing documentation in Qt 5.12

I've also noticed the same for QCoreApplication and QApplication : http://doc.qt.io/qt-5/qapplication-members.html http://doc.qt.io/qt-5/qcoreapplication-members.html --- Jean-Michaël Celerier http://www.jcelerier.name On Mon, Dec 17, 2018 at 3:29 PM Martin Smith wrote: > Are the miss

Re: [Development] Orphan modules

There are quite a bunch of people using it out there : https://github.com/search?l=C%2B%2B=QX11Info+NOT+tst_QX11Info+NOT+QT_END_LICENSE=Code --- Jean-Michaël Celerier http://www.jcelerier.name On Thu, Sep 13, 2018 at 1:41 AM Thiago Macieira wrote: > On Wednesday, 12 September 2018 10

Re: [Development] Missing documentation in Qt 5.12

I think that option 3 (split by class) would be really nice and more readable than the current "all members" list Best, Jean-Michaël Celerier On Wed, Dec 19, 2018 at 1:47 PM Martin Smith wrote: > I found the problem. > > There are a few ways I can fix it. Which is prefe

Re: [Development] CMake Workshop Summary

Although it seems to have been fixed for ninja : https://gitlab.kitware.com/cmake/cmake/merge_requests/430 On Mon, Feb 25, 2019 at 10:02 AM Jean-Michaël Celerier < jeanmichael.celer...@gmail.com> wrote: > > It is not bad, but it is not great either :-). For example one needs to >

Re: [Development] CMake Workshop Summary

> It is not bad, but it is not great either :-). For example one needs to _link_ QtCore before compilation on other things can be started, it is quite visible on an under-powered machines, where linking takes time. I think that this would still generally be the case with CMake, there are

Re: [Development] Qt 5 types under consideration for deprecation / removal in Qt 6

> We probably need to keep QRWL around a while longer, since C++ added shared_mutex only in C++17. Wasn't it said at the world summit that Qt 6 would base itself on c++17 ? https://blog.qt.io/blog/2018/06/13/qt-contributors-summit-2018-wrap/ Best, Jean-Michaël On Wed, May 29, 2019 at 12:55 PM

Re: [Development] Qt 5 types under consideration for deprecation / removal in Qt 6

t;,", " -replace "`n","" -replace ".{2}$"; $res = "unsigned char foobar[] = { " + $content + " }; + `r`nunsigned int foobar_len = " + $size + ";`r`n"; echo $res Feel free to use as you see fit Best, Jean-Michaël Celerier http://www

Re: [Development] Qt 5 types under consideration for deprecation / removal in Qt 6

To bypass the MSVC limitation I think that you need to use array notation instead of string literals, with the help of a tool such as xxd. Apparently powershell has a command to more-or-less do it (format-hex), with some PS magic it could maybe work without too much dependencies added on

Re: [Development] Proposing CMake as build tool for Qt 6

> Looking at the CMake documentation – it looks like a maze. I would recommend starting at the cmake-buildsystem doc page which gives a general overview of the concepts of CMake : https://cmake.org/cmake/help/v3.15/manual/cmake-buildsystem.7.html It is also available as a man page for unix users

Re: [Development] Deprecation/removal model going into Qt 6

> If existing package of application cannot be rebuilt from source with updated Qt version, it's a sure no-go for distibution. Either Qt update will be blocked, or application will be thrown away (or application will be somehow patched by other people, without you even knowing about that) -

Re: [Development] Proposing CMake as build tool for Qt 6

Even if modules were available (and stable) in at least mainline versions of {clang, gcc, msvc} in a year (which I don't think they will), Qt would have to get modularized to actually be able to reap the benefits of modules (given the strong feelings in the "deprecations" thread, we can expect

Re: [Development] Proposing CMake as build tool for Qt 6

Hello :) > What makes you think that you can build Qt for any platform with cmake found in Ubuntu 16.04 (or any later version) ? You can download a CMake static binary (https://cmake.org/download/) that runs fine on Ubuntu 16.04 (or 12.04 or CentOS 6 for that matters) - and it wouldn't be hard

Re: [Development] Proposing CMake as build tool for Qt 6

ian Gagneraud > wrote: > > > > On Mon, 17 Jun 2019 at 23:06, Jean-Michaël Celerier > > wrote: > > > > > > > The world is not spinning around Qt, sorry for the bad news. > > > > > > On that we agree : https://www.jetbrains.com/lp/devecosystem-

Re: [Development] Proposing CMake as build tool for Qt 6

, 17 Jun 2019, 18:11 Jedrzej Nowacki, >> wrote: >> >> >> >> On Saturday, June 15, 2019 6:37:24 PM CEST Thiago Macieira wrote: >> >> > On Saturday, 15 June 2019 02:18:28 PDT Jean-Michaël Celerier wrote: >> >> > > You can download a CMa

Re: [Development] Proposing CMake as build tool for Qt 6

All the best, Jean-Michaël On Mon, Jun 17, 2019 at 2:27 PM Christian Gagneraud wrote: > On Mon, 17 Jun 2019 at 23:06, Jean-Michaël Celerier > wrote: > > > > > The world is not spinning around Qt, sorry for the bad news. > > > > On that we agree : https://www.j

Re: [Development] Proposing CMake as build tool for Qt 6

Here's a basic one, with which I managed to compile & link simple stuff - disclaimer : based on the ideas found in a google search for "keil" "cmake". I only tested on linux with wine. God is that compiler invocation ugly :) Example project I used (with dummy foo.c/bar.c/"space out" subfolder not

Re: [Development] Assistant WebKit/WebEngine support

> Feel free to correct/critique my assessment and to add more options if you see any. Otherwise: chose your poison. There's also Zeal which is a nice Qt-based documentation browser which covers much more than the current .qch offering: https://zealdocs.org/ & https://github.com/zealdocs/zeal I

Re: [Development] QList for Qt 6

> QList is just a linked list you're in for a rude awakening :-) https://doc.qt.io/qt-5/qlist.html On Mon, May 20, 2019 at 5:03 PM Jason H wrote: > > > Ok, QList as an alias for QVector takes care of the technical issues I > > have with using inheritance. It doesn't address my concerns

Re: [Development] CSS styling, XML, HTML etc. (was Re: Assistant WebKit/WebEngine support)

> (of all Qt applications, only a minority use either QSS or CSS) Are there sources for that ? From what I can see it has plenty of usage. https://github.com/search?l=C%2B%2B=setStyleSheet=Code Best, --- Jean-Michaël Celerier http://www.jcelerier.name On Tue, May 21, 2019 at 4:07 PM Sh

Re: [Development] HEADS-UP: QStringLiteral

> Try *any* other compiler and you'll see there's no mutex. Don't __cxa_guard_acquire / release use at least futexes ? I'd wager that in a non-zero amount of applications, having *any* kind of syscalls or locks sprinkled here and there depending on whether you use "static" or not is not kosher

Re: [Development] thread_local: replacing GCC with Clang for MinGW

I'm using this toolchain to build qtbase, declarative, svg, websockets, serialport and a few other : https://github.com/mstorsjo/llvm-mingw I think that it has also been used for webengine. Jean-Michaël On Fri, Aug 23, 2019 at 8:16 PM Thiago Macieira wrote: > Restarting the thread since it

Re: [Development] Migrate QStateMachine from Qt Core

What has lead to considering that they could eventually be removed ? Couldn't they be split off in a separate library put in the marketplace or github for instance if they're a thorn ? No reason to throw away code that works, is there ? On Thu, Feb 13, 2020 at 10:58 AM Karsten Heimrich wrote:

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> I don't think semantics matter here. It is all about annotation and readability. With the same arguments we design APIs. While Kai's survey is inconclusive about the actual solution, it is conclusive in one aspect. There is a clear majority to have sth in place for annotation/readability

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> I may need to write that patch myself. Would you consider instead a patch introducing a builtin that allows a library to declare attributes they "support" ? eg something in the taste of __builtin_declare_valid_attribute("qt::emit"); A far cry from attribute creation abilities of languages such

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

A good inspiration for that feature would be the Just My Code feature of recent visual studio : https://docs.microsoft.com/en-us/visualstudio/debugger/just-my-code?view=vs-2019 Best, Jean-Michaël On Mon, Feb 24, 2020 at 8:51 AM Shawn Rutledge wrote: > > > On 22 Feb 2020, at 12:57, Ville

Re: [Development] GitHub Pull requests

> otherwise we may end up accepting contributions from Twitter :) what is the problem if they improve the code ? On Tue, Mar 10, 2020 at 3:49 PM Konstantin Tokarev wrote: > > > 10.03.2020, 17:42, "Cristian Adam" : > > Hi, > > > > With the “GitHub issues” E-Mail thread we made sure the Issues

Re: [Development] How bad QList really is

> As starters, there are 85 occurences of QList::takeFirst() in Qt Creator source code. Replacing these with QVector replaces a O(1) operation with an O(n) operation. Apologies if I'm wrong, but isn't QList::erase (and anything derivative) always O(N) ? With a lower cost than std::vector for

Re: [Development] Proposal: Deprecate QVector in Qt 6

> I however want some generic indexable/iterable type, where it doesn't care if the final storage is QList or QVector... When I am working as an API, I don't want to choose for my users what that type is and make them pay for conversion. Which I think QList was historically the right choice.

Re: [Development] Views in APIs

> To have type-erased containers, we need to go back to something like java.lang.Collection. C++20 offers coroutines which allows the same things without java-like type hierarchies though (and with much more flexibility as you don't even need to have an actual container existing somewhere - your

Re: [Development] QProperty and library coding guide

It does work "in practice", but from the answer I got on SO, it's still technically UB. If anyone wants to add another, more positive answer sourced from the standard though it'd be very welcome :)

Re: [Development] Switch the main "Qt Build System"

Opening the root qt5/CMakeLists.txt has worked fine for me to work on e.g. qt3d through QtCreator - did not really notice any performance penalty from opening the whole project (except the initial "configure" step). Kind regards, Jean-Michaël On Tue, Jun 9, 2020 at

Re: [Development] Switch the main "Qt Build System"

To simplify this step, is there / could there be maybe a -DQT_BUILD_TOOLS_ONLY that would just generate... well, moc, uic, rcc and a couple other friends required for a cross-build ? Best, Jean-Michaël On Tue, Jun 9, 2020 at 10:14 AM Alexandru Croitor wrote: > > > > On 9. Jun 2020, at 07:22,

Re: [Development] QProperty and library coding guide

> We are not casting these structs to or from anything though, do we? ... >const auto *thisPtr = reinterpret_cast(reinterpret_cast(this) - propertyMemberOffset); sounds pretty much like the structs are indeed being casted to / from anything <_< On Fri, Jul 17, 2020 at 2:13 PM Ulf Hermann

Re: [Development] QThread::create mandatory in Qt 6?

> The big problem I see on Windows is unfortunately not the C++ standard library, but the C standard library. MinGW defaults to crtdll, the one from MSVC 6, which is not C99-compliant (MSVC 6 is from 1998 after all). A better alternative exists in the form of the Universal CRT, but that only comes

Re: [Development] QThread::create mandatory in Qt 6?

(It also has the very nice feature of using lld on windows, which links mch faster than bfd / gold, which could be useful for reducing CI times) <http://www.jcelerier.name> On Fri, Nov 20, 2020 at 9:27 PM Jean-Michaël Celerier < jeanmichael.celer...@gmail.com> wrote: > >

Re: [Development] Updating x86 SIMD support in Qt

eers, ------ Jean-Michaël Celerier *cto* ossia.io | *consulting inquiries* celtera.dev | *personal* jcelerier.name t: +336 81 31 53 08 On Wed, Jan 19, 2022 at 4:30 PM Thiago Macieira wrote: > On Tuesday, 18 January 2022 20:56:10 PST Lorn Potter wrote: > > wasm is a special case, as we turn it o

Re: [Development] Using '#pragma once' instead of include guards?

>The only way you’d have a strong case with this is if it has some other significant benefit, like compilation speedup. The main benefit to me is that it entirely removes possibilities for conflict due to headers having the same name. At least Qt takes great care of avoiding this but still,

Re: [Development] Playground Request: ClapInterface

As someone involved in the audio ecosystem, the Clap plug-in API is quickly becoming an industry standard, is now supported by multiple digital audio workstation software (Reaper, Bitwig, qtractor) and a recurrent topic in audio conferences and circles. It has its own wikipedia page:

Re: [Development] Should QObject::event() be protected or public?

There's nothing more frustrating that instantiating a C++ type on the stack like MyType foo; and having to call a function with: static_cast(foo).someVirtualMethod(); because "The base class is the interface" and all the overriding methods are marked private. This is just adding