On Monday 6 May 2024 17:21:14 CEST Thiago Macieira wrote:
> On Monday 6 May 2024 03:31:46 GMT-7 Allan Sandfeld Jensen wrote:
> > Is there any problem in moving the class all the way if we preserve the
> > headers under both QtGui and QtCore?
>
> Yes. The last time we did
On Monday 6 May 2024 10:02:43 CEST Tor Arne Vestbø via Development wrote:
> There’s some overlap here with the more modern features of intents,
> activities, etc, which we are hoping to add proper APIs for at some point,
> so I suggest not doing any public API changes as part of this.
> We can
On Friday 26 April 2024 21:52:48 CEST Christian Ehrlicher via Development
wrote:
> Hello,
>
> I'm currently trying to investigate a painting problem within the
> windowsvista / common style:
>
> QImage img(7, 7, QImage::Format_ARGB32_Premultiplied);
> QPolygon poly{ QPoint(1, 1), {5,
On Friday, 9 February 2024 10:59:07 CET Vladimir Minenko via Development
wrote:
> Hi,
>
> I also think we should first get the 2022 compiler packages available for
> installation in parallel to the 2019 ones. This should be available for
> users for a while so that they have a transition period.
On Tuesday, 6 February 2024 06:57:34 CET Jani Heikkinen via Development wrote:
> > How about instead we drop at an LTS+2 release? The next one is actually
> > 6.7.
> We can't switch this in 6.7 at this point anymore; we don't have packages
> for MSVC2022 at the moment and doing this (adding new
On Saturday, 3 February 2024 18:08:25 CET Thiago Macieira wrote:
> The compiler is pretty buggy and has several, unfixed conformance issues
> with C++.
>
> One year ago I asked on the interest mailing list about using a non-latest
> MSVC:
>
Hi Hsu,
You probably have more than one Python 3 installed, and the one WebEngine finds
doesnt have html5lib. Btw your log is incomplete, you need to delete
CMakeCache.txt and rerun configure to get a proper configure log.
Best regards
Allan
On Samstag, 28. Oktober 2023 18:09:38 CET Haowei
On Samstag, 15. Juli 2023 17:23:30 EEST Fabian Kosmale wrote:
> Hi,
>
> https://codereview.qt-project.org/c/qt/qtbase/+/466471 should have fixed the
> issue, and should be in 6.5.2 and later. 6.5.1 and .0 should have a revert
> of the commit that caused the regression, so all versions of Qt 6.5
On Montag, 13. März 2023 17:38:54 EEST Thiago Macieira wrote:
> This is a P1 blocker for 6.5.0.
>
> TL;DR: This is a regression; I broke parsing of previously working code and
> don't know how to fix it.
>
> The Q_NOREPLY marker is emitted by qdbusxml2cpp to use a little known moc
> feature of
On Mittwoch, 14. Juni 2023 22:53:13 CEST Thiago Macieira wrote:
> On Wednesday, 14 June 2023 12:49:22 PDT Allan Sandfeld Jensen wrote:
> > As discussed earlier. Better naming in many cases until we can depend on
> > C++20 in API.
>
> There's nothing in C++20 that would al
On Mittwoch, 14. Juni 2023 17:48:27 CEST Thiago Macieira wrote:
> On Wednesday, 14 June 2023 08:35:16 PDT Marc Mutz via Development wrote:
> > >>> B) new enums MUST be scoped, also when nested in classes¹²
> > >>
> > >> -1 Disagree
> > >
> > > -1 Disagree
> >
> > Ok. But _why_? (Q to both)
>
>
On Mittwoch, 14. Juni 2023 14:59:40 CEST Marc Mutz via Development wrote:
> On 02.05.23 10:58, Volker Hilsheimer via Development wrote:
> > During the header review, but also in API discussions leading up to it, we
> > had a few cases where it would have helped if we had clearer guidelines
> >
On Mittwoch, 10. Mai 2023 08:01:11 CEST Marc Mutz via Development wrote:
> On 10.05.23 01:21, Thiago Macieira wrote:
> > On Tuesday, 2 May 2023 17:39:01 PDT Thiago Macieira wrote:
> >> Opinions?
> >
> > BTW, here's the opinion of the GCC devs:
> >
> > Don't ever use the -std= option to raise the
On Dienstag, 9. Mai 2023 08:51:37 CEST Marc Mutz via Development wrote:
> Hi,
>
> I'd like to propose the following clarifications:
>
> - no space between "operator" and it's symbol:
>
> // WRONG
> bool operator ==()
> // CORRECT
> bool operator==()
>
> Rationale:
On Mittwoch, 3. Mai 2023 19:40:18 CEST Marc Mutz via Development wrote:
> On 03.05.23 19:22, Thiago Macieira wrote:
> > On Wednesday, 3 May 2023 09:40:42 PDT Giuseppe D'Angelo via Development
wrote:
> >> To me it's a no brainer: any new enumeration
> >>
> >> added to Qt shall be an enum class.
Perhaps we should start by using C++20 by default if supported, and then later
require it? It seems we are missing a step.
Best regards
Allan
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Montag, 6. März 2023 22:11:59 CET Thiago Macieira wrote:
> On Monday, 6 March 2023 09:08:39 PST Allan Sandfeld Jensen wrote:
> > What is worse is that is seems to be the non-DSPr2 code path, so you need
> > a
> > machine with only DSPr1.
>
> This is not runtime-detec
On Montag, 6. März 2023 17:51:04 CET Lisandro Damián Nicanor Pérez Meyer
wrote:
> El domingo, 5 de marzo de 2023 14:36:55 -03 Thiago Macieira escribió:
> > https://bugreports.qt.io/browse/QTBUG-111740
> >
> > The reporter is saying that the QString::fromLatin1 function generates
> > corrupt
On Montag, 30. Januar 2023 10:03:53 CET Giuseppe D'Angelo via Development
wrote:
> On 30/01/2023 09:07, Allan Sandfeld Jensen wrote:
> > I would add my support to removing it from 6.6, It would simplify the
> > continued updating of Chromium that is starting to depend on c++
On Dienstag, 17. Januar 2023 23:07:42 CET Thiago Macieira wrote:
> The reason is that it is failing to parse a constant expression.
>
> VS2019 is still supported by MSFT in "Mainstream" mode and will be for over
> a year from today:
>
+1
On Dienstag, 29. November 2022 14:55:07 CET Volker Hilsheimer via Development
wrote:
> Hi,
>
>
> Kurt Pattyn is currently listed as the Maintainer fo Qt WebSocket. However,
> he has not responded to emails I sent him over the last few months. In the
> middle of October I informed him that I
On Samstag, 5. November 2022 16:56:27 CET Thiago Macieira wrote:
> On Saturday, 5 November 2022 01:16:36 PDT Marc Mutz via Development wrote:
> > Done. Also for qfloat16.
>
> qfloat16 needs some TLC to adapt to P1467. I have the patches for that and
> have tested that they work in a processor
On Freitag, 4. November 2022 21:47:14 CET Thiago Macieira wrote:
> On Friday, 4 November 2022 10:38:30 PDT Allan Sandfeld Jensen wrote:
> > Can we even do that, and still preserve ABI and API?
>
> I don't see why not. QFlags is already standard-layout, trivially copyable
On Freitag, 4. November 2022 16:49:30 CET Thiago Macieira wrote:
> I've just hit this: should we make some of our very simple types even
> simpler so they're structural types[1] and thus can be passed as template
> parameters?
>
> For example, QFlags. I've just tried it and I get:
>
> error:
On Mittwoch, 28. September 2022 10:31:52 CEST Volker Hilsheimer wrote:
> > On 27 Sep 2022, at 22:01, Elvis Stansvik wrote:
> >
> > Den tis 27 sep. 2022 kl 21:52 skrev Elvis Stansvik :
> >> Den tis 27 sep. 2022 kl 21:01 skrev Thiago Macieira
:
> >>> On Tuesday, 27 September 2022 09:48:01 PDT
it is about time we grant him approver rights.
Best regards,
Allan Sandfeld Jensen
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Samstag, 10. September 2022 00:05:10 CEST samuel ammonius wrote:
> Hello,
>
> I'm new to contributing to Qt directly, but I've been trying to create
> external C bindings for Qt for a few months now. Since C and C++ are so
> similar, I've recently been thinking it may just be better to add C
On Mittwoch, 3. August 2022 16:35:16 CEST Thiago Macieira wrote:
> On Wednesday, 3 August 2022 04:56:41 PDT Marc Mutz wrote:
> > - ARM
> > - x86 (Thiago would be the obvious candidate, if he's in for it)
>
> I agree. I already do this anyway, so it's just formalising something that
> exists.
>
>
On Mittwoch, 20. Juli 2022 10:43:36 CEST JiDe Zhang wrote:
> I trying fix https://bugreports.qt.io/browse/QTBUG-75954, I think the
> problem is related to it.
Interesting. Might be worth checking out if it acts differently between
different scenegraph backends. RHI OpenGL vs Software for
On Mittwoch, 20. Juli 2022 07:48:47 CEST JiDe Zhang wrote:
> I want to rotate the image to 45 degrees by Y axis, what should I do?
>
Why rotate it around the Y axis? Would that just be a squeezing scale
transform? 45 degrees would be scaling to cos(45) of the width. Are you sure
you don't want
On Mittwoch, 13. Juli 2022 12:14:27 CEST Felix Crazzolara wrote:
> Dear everyone,
>
> I would like to use Qt for a personal project. In my project, I use a
> relatively small part of Qt and I think that the components of QtBase here
> https://github.com/qt/qtbase
> suffice for my application.
>
On Montag, 13. Juni 2022 09:19:09 CEST Frederik Gladhorn wrote:
> Hello :)
>
> I've lately not had time to contribute to Qt (personal life keeping me
> busy).
> Since Volker and others did a great job porting Qt Speech to Qt 6, they
> know the code better than me by this time. I'd like to step
of the outcome of the election, I look forward to continuing to
work together with all of you, and keep improving Qt.
Best regards
Allan Sandfeld Jensen
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo
On Freitag, 20. Mai 2022 10:12:03 CEST Alexandru Croitor wrote:
> I'd like to nominate Allan Sandfeld Jensen.
>
> Allan is a full time employee at TQtC, is a maintainer, is very technical,
> working on things all the way from Core / Gui to WebEngine
> He's been part of t
On Donnerstag, 21. April 2022 16:09:37 CEST Thiago Macieira wrote:
> On Thursday, 21 April 2022 06:22:57 PDT Tomi Pannila wrote:
> > Is there a possibility to add a picture to Qt documentation where you
> > have a rectangle grid and shade the
> > edge cells with some color to identify them as
On Mittwoch, 16. Februar 2022 01:21:16 CET Thiago Macieira wrote:
> On Tuesday, 15 February 2022 11:37:30 PST Giuseppe D'Angelo via Development
>
> wrote:
> > First and foremost, does anyone know whether QtWayland is under any BC
> > promise at all?
>
> The question must be turned around: does
On Mittwoch, 19. Januar 2022 16:41:11 CET Thiago Macieira wrote:
> On Tuesday, 18 January 2022 22:43:40 PST Kevin Kofler via Development wrote:
> > Thiago Macieira wrote:
> > > By default, I'd like us to produce x86-64 v2 code, which is SSE4.
> >
> > But v1 will still be available for
On Mittwoch, 19. Januar 2022 04:01:06 CET Thiago Macieira wrote:
> 5) for glibc-based Linux, add v3 sub-arch by default
>
> I'd like to raise the default on Linux from baseline to v2 *and* add a v3
> sub- arch build, as described by point #3 above.
>
> Device-specific Qt builds (Yocto Project,
On Dienstag, 18. Januar 2022 15:10:48 CET Cristián Maureira-Fredes wrote:
> Hello,
>
> I would like to nominate Sona as maintainer [1]
> for the qt5compat module, which at the moment doesn't
> have one. Even if it's a special module we have around
> only for Qt6, we need a responsible person in
On Freitag, 28. Mai 2021 11:49:35 CEST Benjamin TERRIER wrote:
> Random thoughts: Could this willingness to replace virtual
> protected functions by signals be linked to QML?
> In QML we do not have virtual protected functions and can only use
> signals...
>
Yes, that how all the methods are
On Donnerstag, 27. Mai 2021 14:41:54 CEST you wrote:
> On Thu, 27 May 2021 at 14:17, Allan Sandfeld Jensen
>
> But it does not change my point about signal vs protected functions.
> Let's say I have a QWebEnginePage subclass that only allows some SSL errors
> by checking asynchron
On Donnerstag, 27. Mai 2021 13:55:01 CEST Benjamin TERRIER wrote:
> On Thu, 27 May 2021 at 11:25, Allan Sandfeld Jensen
>
> But then in my code, each time I see a CrazySSLPage I am never sure that it
> will ignore SSL errors. Maybe someone called QObject::disconnect() on it.
>
On Wednesday, 26 May 2021 18:39:56 CEST Benjamin TERRIER wrote:
> Hi,
>
> I just saw this ticket: https://bugreports.qt.io/browse/QTBUG-74587
> and this related gerrit change:
> https://codereview.qt-project.org/c/qt/qtwebengine/+/346723
>
> I am not sure what to think about it.
> Sure it is
On Mittwoch, 7. April 2021 16:53:16 CEST Henry Skoglund wrote:
> On 2021-04-07 16:11, Volker Hilsheimer wrote:
> >> On 7 Apr 2021, at 15:55, Allan Sandfeld Jensen wrote:
> >>
> >> On Mittwoch, 7. April 2021 15:18:10 CEST Giuseppe D'Angelo via
> >> Developm
On Mittwoch, 7. April 2021 15:18:10 CEST Giuseppe D'Angelo via Development
wrote:
> Il 07/04/21 14:56, Sze Howe Koh ha scritto:
> > Is it acceptable to remove them during Qt 6's lifetime? Or should we
> > wait till Qt 7?
>
> It's for Qt 7, I'm afraid. We're bound to an API/ABI compatibility
>
On Mittwoch, 3. März 2021 09:32:33 CET Jason H wrote:
> I saw Lars's Qt6 talk on youtube, where he said Qt6 requires C++17. He also
> mentioned the new QFuture:: then() function... This is an improvement, but
> it makes Qt code look like Javascript in 2015.
>
> In C++20 there are async/await
On Mittwoch, 13. Januar 2021 13:07:00 CET NIkolai Marchenko wrote:
> that's ... kinda what you're supposed to avoid... at least as far as I
> understand the convo earlier. so that two major versions aren't pushed to
> the same repo confusing people.
>
I don't see any problems with that. It is how
On Mittwoch, 13. Januar 2021 13:01:30 CET NIkolai Marchenko wrote:
> except when qt7 comes you'll be stuck with versionless qt6 branch that you
> wouldn't be able to move to qt7 because of aforementioned dependency
> breakages.
>
Why not? It would just be a new branch in the same repo
Best
On Mittwoch, 13. Januar 2021 12:31:50 CET Eric Lemanisser wrote:
> that's the obvious choice, if it was not already used by qt4.
>
Then rename the qt4 repo, it is not actively maintained anymore and only
stored for history. We couldn't do that when creating qt5 as it was still
actively
On Mittwoch, 13. Januar 2021 11:36:14 CET Nibedit Dey wrote:
> Hello Everyone,
>
> Is there any plan to move the qt6 source code to a different repo (qt6)?
> Currently, the branch lies inside the qt5 repo.
> Is there going to be a Qt6 super module in near future?
>
If it is going to be a general
On Donnerstag, 10. Dezember 2020 15:14:47 CET Ville-Pekka Karhu wrote:
> Hi all!
>
> We’ll have our scheduled maintenance break on next Monday (14th of Dec).
> We’ll begin our work at 8:00 EET and you can prepare for 3 hours of CI not
> working.
>
>
Considering the CIs needs to be reprovisioned
So, we can:
1. Live with it or find a work around
2. Break BC after 6.0.0 (we have don that before, though only when accidently
breaking BC in a point release)
3. Break BC again "soonish", like after 6.2 or 6.5
Any other options?
Best regards
'Allan
On Montag, 16. November 2020 02:53:14 CET Thiago Macieira wrote:
> On Sunday, 15 November 2020 08:29:56 PST Thiago Macieira wrote:
> > > * whether there is any chance to get a fix or workaround in the near
> > > future
> > > (or even right now), either in the form of an upgrade to the vendor
> > >
On Sonntag, 15. November 2020 01:37:32 CET Thiago Macieira wrote:
> On Saturday, 14 November 2020 03:05:13 PST Giuseppe D'Angelo via Development
> wrote:
> > 2) was removed in https://codereview.qt-project.org/c/qt/qtbase/+/306811
> > , or are you referring to something else? Was it a mistake to
On Dienstag, 3. November 2020 05:34:02 CET Jason McDonald wrote:
> Some food for thought for module maintainers.
>
> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
> those issues had that priority set more than one year ago, 342 of those had
> their priority set more
On Mittwoch, 28. Oktober 2020 09:15:33 CET Lars Knoll wrote:
> > On 28 Oct 2020, at 08:37, Allan Sandfeld Jensen wrote:
> >
> > On Dienstag, 27. Oktober 2020 17:34:44 CET Thiago Macieira wrote:
> >> Have we fixed it?
> >>
> >> I do not pla
On Dienstag, 27. Oktober 2020 17:34:44 CET Thiago Macieira wrote:
> Have we fixed it?
>
> I do not plan on updating qtchooser for Qt 6. Qt 6 should not install any
> binary with the same name as Qt 5 did.
Do we need to change the default name of moc and uic then?
Best regards
Allan
On Dienstag, 22. September 2020 11:35:07 CEST Benjamin TERRIER wrote:
> On Mon, 21 Sep 2020 at 14:10, Allan Sandfeld Jensen
>
> wrote:
> > Use the SHA1s in dependencies.yaml
>
> That's not very practical to do by hand, but it worked.
>
Yeah I know. Should be simpler
On Montag, 21. September 2020 13:05:46 CEST Benjamin TERRIER wrote:
> Hi,
>
> I am trying to contribute to the dev branch of qtwebengine, but I cannot
> get it to compile with Qt 5.15.1 or with Qt 6 preview.
>
> With Qt 5.15 the compiler complains that `QWebEngineCertificateError` does
> not
On Freitag, 18. September 2020 10:28:06 CEST Albert Astals Cid via Development
wrote:
> El divendres, 18 de setembre de 2020, a les 10:22:16 CEST, Lars Knoll va
escriure:
> > Sorting and equality are two different things. QVariant has never
> > supported
> > a lessThan operator.
>
> Yes, it has
On Freitag, 18. September 2020 02:54:53 CEST Thiago Macieira wrote:
> On Thursday, 17 September 2020 16:15:47 PDT Bernhard Lindner wrote:
> > Hi!
> >
> > There was a discussion about the decision to deprecate (remove?) QVariant
> > comparison (<,>) in Qt6 completely.
> >
> > Has anything changed
On Freitag, 11. September 2020 12:44:09 CEST Volker Hilsheimer wrote:
> > On 11 Sep 2020, at 12:37, Allan Sandfeld Jensen wrote:
> >
> > Should we add a generic virtual hook in qobject, so any qobject can expand
> >
their with effectively virtual functions in Qt6?
>
Should we add a generic virtual hook in qobject, so any qobject can expand
their with effectively virtual functions in Qt6?
I imagine something like QVariant QObject::virtual_hook(int id, QVariant
args);
Or do we already have other useful work-arounds for this common problem?
Best regards
On Mittwoch, 9. September 2020 10:17:25 CEST Allan Sandfeld Jensen wrote:
> On Mittwoch, 9. September 2020 09:14:29 CEST Lars Knoll wrote:
> > Hi Allan,
> >
> > On 7 Sep 2020, at 12:59, Allan Sandfeld Jensen
> > mailto:k...@carewolf.com>> wrote:
> >
> &g
On Mittwoch, 9. September 2020 09:14:29 CEST Lars Knoll wrote:
> Hi Allan,
>
> On 7 Sep 2020, at 12:59, Allan Sandfeld Jensen
> mailto:k...@carewolf.com>> wrote:
> On Mittwoch, 26. August 2020 08:46:41 CEST Lars Knoll wrote:
> Hi all,
>
> This is just a gentl
On Samstag, 20. Juni 2020 21:00:27 CEST Alberto Mardegan wrote:
> On 20/06/20 21:42, Konstantin Tokarev wrote:
> > Comparing metaObject() with staticMetaObject() is wrong because it would
> > fail even for QProcess.
>
> I didn't try, but why would it fail?
>
> > OTOH, using qobject_cast would
Hi Qt
I recently discovered there is a binutils tools for size optimizing dwarf
debug symbols, and it really works. When applied to Qt debug symbol binaries
it makes them about 25% smaller on average (some up to 40% smaller). And that
is just the simple optimization. We can save more by
On Montag, 4. Mai 2020 17:44:14 CEST Volker Hilsheimer wrote:
> > On 17 Apr 2020, at 13:21, Volker Hilsheimer
> > wrote:
> …
>
> > During this process and starting next week, we will update the relevant
> > documentation pages, such as:
> > http://quips-qt-io.herokuapp.com/quip-0005.html
> >
On Dienstag, 14. April 2020 02:08:22 CEST Giuseppe D'Angelo via Development
wrote:
> Hi,
>
> On 4/14/20 1:34 AM, Konstantin Tokarev wrote:
> >> The golden rule is that you're not allowed to touch any Qt API without
> >> creating a Q*Application object first, unless the documentation says
> >>
On Montag, 13. April 2020 18:50:17 CEST Kevin Kofler wrote:
> Hi,
>
> I have a question concerning development of plugins for Qt, so hopefully it
> is not entirely off-topic here:
>
> Today, a user on #fedora-kde ran across a crash which resulted from:
> * a GTK+/GNOME application (Jami) using
On Monday, 2 March 2020 08:45:29 CET Jaroslaw Kobus wrote:
> Allan Sandfeld Jensen (27 February 2020 23:03) replied:
> > That is how I see it too. It essentially violates Qt code guidelines. If
> > it
> > was a normal method we would name it "emitEmptied()"
On Friday, 28 February 2020 16:28:34 CET Matthew Woehlke wrote:
> On 27/02/2020 17.03, Allan Sandfeld Jensen wrote:
> > On Thursday, 27 February 2020 21:51:18 CET Matthew Woehlke wrote:
> >> On 26/02/2020 07.42, Tor Arne Vestbø wrote:
> >>> As others have a
On Thursday, 27 February 2020 21:51:18 CET Matthew Woehlke wrote:
> On 26/02/2020 07.42, Tor Arne Vestbø wrote:
> > As others have argued, a signal is not special, in the sense that any
> > function can do anything, including emitting signals, so annotating it
> > doesn’t seem critical, as we
On Thursday, 27 February 2020 21:43:33 CET Matthew Woehlke wrote:
> On 27/02/2020 13.57, Thiago Macieira wrote:
> > On Monday, 24 February 2020 03:30:25 PST André Somers wrote:
> >> You seem to assume everyone used QtCreator as their IDE of choice. That
> >> is
> >> not a reasonable assumption I
On Monday, 24 February 2020 15:03:41 CET Ville Voutilainen wrote:
> On Mon, 24 Feb 2020 at 15:52, Ville Voutilainen
>
> wrote:
> > On Mon, 24 Feb 2020 at 14:42, Lars Knoll wrote:
> > > But we could convey the information that this is a signal you’re calling
> > > *reliably* through other means.
On Friday, 21 February 2020 12:44:56 CET Allan Sandfeld Jensen wrote:
> On Friday, 21 February 2020 12:28:29 CET Giuseppe D'Angelo via Development
>
> wrote:
> > Il 21/02/20 12:15, Ville Voutilainen ha scritto:
> > >> without any annotation is not what we want.
On Friday, 21 February 2020 12:28:29 CET Giuseppe D'Angelo via Development
wrote:
> Il 21/02/20 12:15, Ville Voutilainen ha scritto:
> >> without any annotation is not what we want. We'd miss vital information
> >> and reduce readability.>
> > Can you please explain what that vital information
On Sunday, 16 February 2020 19:32:02 CET Thiago Macieira wrote:
> On Saturday, 15 February 2020 06:23:52 PST Marc Mutz via Development wrote:
> > C++20 will contain new classes with emit() member functions
> > (wg21.link/P0053). While that will only pose problems for users that
> > include the new
On Tuesday, 11 February 2020 20:19:36 CET André Pönitz wrote:
> On Tue, Feb 11, 2020 at 03:15:11PM +, Vitaly Fanaskov wrote:
> > I want to summarize intermediate results of the discussion and return it
> > back to the track.
> >
> >
> > Subject: using smart pointers in the API.
> > Good
On Samstag, 8. Februar 2020 05:00:31 CET Thiago Macieira wrote:
> If we don't need runtime detection, then just #include or a
> wrapper header to deal with MSVC not defining __SSE2__. qfloat16.h does
> that.
>
> We also need to decide whether we want the macro normalisation that
> qsimd_p.h does
On Donnerstag, 6. Februar 2020 21:17:02 CET Lars Knoll wrote:
> > On 6 Feb 2020, at 19:29, Allan Sandfeld Jensen wrote:
> > making the default SSE4.1 enabled but still offer users (linux distros
> > really), the option to force it down to only SSE2.
>
>
> We shou
On Donnerstag, 6. Februar 2020 12:45:51 CET Lars Knoll wrote:
> One problem is, that we can only get full benefit out of those if we can
> offer them inline. That would basically imply making our qsimd_p.h header
> public and including that one from qvectornd.h and qmatrixnxn.h (so that we
> can
On Samstag, 1. Februar 2020 10:15:02 CET you wrote:
> Il 01/02/20 09:27, Allan Sandfeld Jensen ha scritto:
> > To me the name is still perfect. It makes perfect sense. Just because it
> > is
> > movable doesn't mean you move the object itself, a move moves the content
>
On Samstag, 1. Februar 2020 00:31:17 CET Giuseppe D'Angelo wrote:
> On 31/01/2020 23:47, Allan Sandfeld Jensen wrote:
> >> The question stays: how do we call a unique_ptr equivalent?
> >
> > QScopedPointer? ;)
>
> That name was precisely the reason why the idea o
On Freitag, 31. Januar 2020 21:04:58 CET Ville Voutilainen wrote:
> On Fri, 31 Jan 2020 at 21:23, Alberto Mardegan
>
> wrote:
> > Old man here:
> >
> > On 31/01/20 13:07, Vitaly Fanaskov wrote:
> > > But how to use them in the API and which way is preferable is still
> > > unclear. There are
On Freitag, 31. Januar 2020 17:24:20 CET Sona Kurazyan wrote:
> Additionally, there are some discussions about QFuture being a mix between a
> “Task” and a “Future”. One of the options of improving this situation is to
> make a QTask (or QJob) out of the current QFuture. But then the question
>
On Friday, 31 January 2020 11:07:52 CET Vitaly Fanaskov wrote:
> Hello everyone,
>
> We’ve been discussing for a while how Qt6 API can be improved with using
> smart pointers. Recently we came into some conclusions and want to
> discuss them with the community.
>
> Smart pointers are for sure
On Dienstag, 28. Januar 2020 03:27:04 CET Thiago Macieira wrote:
> On segunda-feira, 27 de janeiro de 2020 15:16:35 PST Kevin Kofler wrote:
> > Thiago Macieira wrote:
> > > All security fixes are made available to everyone, for all Qt versions
> > > that they affect, provided it's still a
On Wednesday, 20 November 2019 20:20:29 CET Kari Oikarinen wrote:
> ## Parallel STL algorithms
>
> We could allow parallel execution tags in our API to let users ask for
> use of parallel algorithms.
>
> But what are the places in Qt API that actually need these? More data
> analysis stuff (if
On Thursday, 7 November 2019 16:06:41 CET drwho wrote:
> On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
> > On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
> >> 4) What about the memory footprint?
> >
> > A couple of megabytes.
>
> I'd love to see a build how too that
On Thursday, 17 October 2019 22:01:34 CEST Martin Smith wrote:
> >I for one, never liked
> >QObject* x, y;
> >because x is a pointer, and y is not. It seems like they should both be
> >QObject*s.
> But that argues for not allowing the comma.
>
> QObject* x;
> QObject* y;
>
> I've always done it
gt; variables, and/or switch to specifying per-screen DPI instead of a
> > >>>> scale
> > >>>> factor.
> >
> > On Thursday, 26 September 2019 04:48:26 CEST Thiago Macieira wrote:
> > >>> Sure, but where, on X11?
> >
> > On Th
On Thursday, 26 September 2019 04:48:26 CEST Thiago Macieira wrote:
> > If possible, I’d like us to move away from relying on setting environment
> > variables, and/or switch to specifying per-screen DPI instead of a scale
> > factor.
>
> Sure, but where, on X11?
xrandr?
We read the X11 setting
On Friday, 20 September 2019 00:07:38 CEST Thiago Macieira wrote:
> On Thursday, 19 September 2019 03:17:12 PDT Giuseppe D'Angelo via
> Development
> wrote:
> > On 18/09/2019 17:33, Thiago Macieira wrote:
> > >>> We've never required C++11 Standard Library. We've only required the
> > >>> core
> >
On Tuesday, 3 September 2019 07:53:29 CEST Liang Qi wrote:
> It happened so fast this time.
>
> But 5.12.5 was branched out before this cherry-pick mode change on 5.12
> branch, I plan to do the 5.12.5->5.12->5.13 merges after 5.12.5 is out. Is
> it OK?
That sounds good. Otherwise we might need
+1
Allan
On Monday, 2 September 2019 16:37:29 CEST Simon Hausmann wrote:
> +1
>
>
> Simon
>
> From: Development on behalf of Johan
> Helsing Sent: Friday, August 23, 2019 14:15
> To: development@qt-project.org
> Subject: [Development] Nominating David
On Thursday, 29 August 2019 14:54:45 CEST Michael Bruning wrote:
> Hi all,
>
> I would like to nominate Kirill Burtsev as approver for the Qt Project.
> Kirill joined the Qt WebEngine team about a year ago and has been mainly
> contributing to the web engine module, but also to qtbase and
>
On Friday, 23 August 2019 14:51:36 CEST Mutz, Marc via Development wrote:
> On 2019-08-23 14:31, Allan Sandfeld Jensen wrote:
> [...]
>
> > condition_variable_any::_M_mutex
>
> I didn't say _any :)
>
> > The std::conditional_variable has the same problem QWaitCon
On Friday, 23 August 2019 10:31:20 CEST Mutz, Marc via Development wrote:
> On 2019-05-29 12:53, Mutz, Marc via Development wrote:
> > === QWaitCondition -> std::condition_variable(_any) ===
> >
> > Plumbing that std::condition_variable can do better.
>
> So, I've looked at QWaitCondition
On Tuesday, 13 August 2019 18:13:05 CEST Thiago Macieira wrote:
> On Tuesday, 13 August 2019 00:50:48 PDT Friedemann Kleint wrote:
> > Hi,
> >
> > > VC++ 2019
> >
> > Just for the record, this compiler still has a number of optimizer bugs,
> > see https://bugreports.qt.io/browse/QTQAINFRA-2875
1 - 100 of 291 matches
Mail list logo
