Re: [Interest] Make a specific Unicode glyph wider in a QTextLayout

On Sunday 15 December 2024 18:07:46 Central European Standard Time Wang Gary wrote: > Hi again, > > > > > Replace the non-visible character in the model with a visible one in > > > > the > > > > view? > > > > > > Well, there are some reasons that I personally would like to avoid > > > that. Firs

Re: [Interest] Make a specific Unicode glyph wider in a QTextLayout

On Sunday 15 December 2024 15:56:53 Central European Standard Time Wang Gary wrote: > > > So the question is, what's the proper approach to implement such a > > > feature > > > using Qt's public API? Do the mentioned two approaches sound right? > > > > Replace the non-visible character in the mod

Re: [Interest] Make a specific Unicode glyph wider in a QTextLayout

On Sunday 15 December 2024 08:23:50 Central European Standard Time Wang Gary wrote: > Hi, > > I'm attempting to implement a feature in a plain text editor that similar > to Notepad++'s "show hidden characters", which allows toggle the visibility > of non-printable characters, like zero-width spac

Re: [Development] (Bikeshed, pedantic) East constexpr vs West constexpr

On Thursday 19 September 2024 16:00:22 Central European Summer Time Thiago Macieira wrote: > On Wednesday 18 September 2024 22:10:44 GMT-7 Marc Mutz via Development wrote: > > Enforcing one over the other would make it impossible to follow > > https://wiki.qt.io/Things_To_Look_Out_For_In_Reviews#

Re: Non-consistent ICE in 14.1 and 14.2

On Thursday 29 August 2024 14:38:04 Central European Summer Time Alexander Monakov wrote: > On Thu, 29 Aug 2024, Richard Biener via Gcc wrote: > > On Thu, Aug 29, 2024 at 1:49 PM Allan Sandfeld Jensen > > > > wrote: > > > Hi GCC > > > > > > I

Non-consistent ICE in 14.1 and 14.2

Hi GCC I wanted to report one or more bugs, unfortunately they are not consistently reproducable, which is odd. It happens when compiling the chromium part of qtwebengine after the update to gcc 14 and during development for updating Chromium to 126. On almost every run over a few thousand file

[Development] Nominating Anu Aliyas for approver rights

] Reviews: https://codereview.qt-project.org/q/reviewer:anu.ali...@qt.io[2] Best regards, Allan Sandfeld Jensen [1] https://codereview.qt-project.org/q/owner:anu.ali...@qt.io [2] https://codereview.qt-project.org/q/reviewer:anu.ali...@qt.io -- Development mailing list Development@qt

Re: [Development] Changing Qt's Binary Compatibility policy

On Thursday 30 May 2024 15:56:26 CEST Volker Hilsheimer via Development wrote: > My larger concern is that for patch releases, we have no processes to avoid > that we end up adding poor APIs. We don’t do a header review, and we don’t > have a whatsnew documentation file. The changelog should be eno

Re: [Development] Moving QDesktopServices from Gui to Core?

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

Re: [Development] Moving QDesktopServices from Gui to Core?

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 mo

Re: [Development] Issues with QPainter::drawPolygon (off by one error?)

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, 1

Re: [Development] Let's drop MSVC 2019 for dev (6.8)

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.

Re: [Development] Let's drop MSVC 2019 for dev (6.8)

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 pac

Re: [Development] Let's drop MSVC 2019 for dev (6.8)

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: > https://lists.qt-project.org/pipermail/interest/2023-Janu

Re: [Interest] Qt uses fontconfig on Linux, but what about Windows?

On Montag, 18. Dezember 2023 05:14:38 CET Thomas Larsen Wessel wrote: > Thanks :) In case others will be looking / googling for this, I will try to > share what I found out in the meantime. Please correct me where I am wrong > > :) > > At first I thought fontconfig was more of a software library

Re: [Interest] Qt uses fontconfig on Linux, but what about Windows?

On Samstag, 16. Dezember 2023 15:58:00 CET Thomas Larsen Wessel wrote: > Quote from https://doc.qt.io/qt-6/qt-embedded-fonts.html: > > *Qt normally uses fontconfig to provide access to system fonts*. If > > > fontconfig is not available, e.g. in dedicated embedded systems where > > space > > is a

Re: KIO workers and the Qt5->Qt6 transition

On Dienstag, 12. Dezember 2023 15:57:49 CET Nicolas Fella wrote: > Hi, > > this is a variant of the plugin problem outlined in > https://mail.kde.org/pipermail/kde-devel/2023-December/002234.html > > TL;DR Qt6 can't load Qt5-based plugins and vice versa > You can. It is probably not a good idea

Re: [Development] Cannot find 'html5lib' when configuring qt with MSVC compiler even if it's installed.

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 Hsu

Re: [Development] QTBUG-111330: moc help needed: parsing QtDBus Q_NOREPLY

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 s

Re: [Development] QTBUG-111330: moc help needed: parsing QtDBus Q_NOREPLY

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 ex

Re: [Interest] QtCreator new C++ formatting is not good sometimes...

On Montag, 26. Juni 2023 18:11:55 CEST Alexander Dyagilev wrote: > Hello, > > Let's suppose I have this: > > I always prefer a base class to be specified on the second line. > > In older versions if I press Enter I was getting something like this: > > Now I'm getting this: > > This is neither

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

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 wou

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

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) > >

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

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 > > abou

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

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

Re: [Development] Proposing changes to https://wiki.qt.io/Qt_Coding_Style

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: th

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

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.

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

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

Re: [Development] QTBUG-111740 - MIPS DSP or DSPv2 verification needed

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

Re: [Development] QTBUG-111740 - MIPS DSP or DSPv2 verification needed

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 trans

Re: [Development] Do we need VS2019 for Qt 6.6?

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 o

Re: [Development] Do we need VS2019 for Qt 6.6?

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: > https://learn.microsoft.com/en-us/visualstudio/releases/2019/se

Re: [Interest] Qt 6.5 Is Irrelevant...

On Montag, 19. Dezember 2022 16:59:41 CET Michael Jackson wrote: > So not really a “jolt every 3 years”. You have had 3 _total_ jolts over the > course of 30 years. > Except them dropping support for pre-AVX, pre-AVX2 CPUs, constantly dropping support for GPUs older than 4 years all the bloody ti

Re: [Development] Nominating Mårten Nordheim and Timur Pocheptsov as new co-maintainers of Qt WebSocket

+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

Re: [Development] C++20 structural types (was: C++20 @ Qt)

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 emul

Re: [Development] C++20 structural types (was: C++20 @ Qt)

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 copy

Re: [Development] C++20 structural types (was: C++20 @ Qt)

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: ‘QFl

Re: [Interest] Scripting within Qt6 and QJSEngine

On Mittwoch, 5. Oktober 2022 09:28:19 CEST Christian Kandeler via Interest wrote: > On 9/26/22 17:47, Filippo Rusconi via Interest wrote: > > Greetings, > > my C++ software program (GUI) was scriptable using the QtScript module > > of Qt5. > > > > I now would like to build it using Qt6 and to tak

Re: [Development] Qt 6.2.6 LTS Commercial released

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 Elvi

[Development] Nominating Szabolcs David as Approver

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

Re: [Development] Could support for C be added to Qt?

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 su

Re: [Development] Proposing to add (CPU) architecture maintainers

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. > >

Re: [Development] What is the correct way to use QTransform to rotate a QImage by the Y axis?

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 instance

Re: [Development] What is the correct way to use QTransform to rotate a QImage by the Y axis?

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 t

Re: [Development] Licensing of qtbase

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. > >

Re: [Development] Nominating Volker Hilsheimer as maintainer of Qt Speech

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 dow

Re: [Development] Chief Maintainer election

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

Re: [Development] New Chief Maintainer

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

Re: [Interest] webenginewidgets (Win MinGw11.2.0)

On Mittwoch, 18. Mai 2022 08:58:20 CEST Alexander Carôt wrote: > >>MinGW is unsupported in qtwebengine in the sense it doesn't work at all. > > Understood – I wonder what would be required in order to make it support > qtwebengine. It sounds not to be trivial. > Well, technically it might not be

Re: [Interest] webenginewidgets (Win MinGw11.2.0)

On Dienstag, 17. Mai 2022 18:47:03 CEST Thiago Macieira wrote: > On Tuesday, 17 May 2022 01:33:16 PDT Allan Sandfeld Jensen wrote: > > It is not supported for MinGW. Only MSVC, and clang-cl on windows. > > And clang-cl is not supported for qtbase. Not officially perhaps, but it

Re: [Interest] webenginewidgets (Win MinGw11.2.0)

On Dienstag, 17. Mai 2022 07:55:41 CEST Alexander Carôt wrote: > Hello all, > > after success on OSX I am now trying to get my code working with Windows > (MinGw11.2.0). > > I installed Qt6.3 including any other additional library but qmake tells me: > > Project ERROR: Unknown module(s) in QT: w

Re: [Development] QRect::contains and undocumented(?) edge

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 edges

Re: [Interest] qtwebbroser questions

On Montag, 11. April 2022 11:48:09 CEST Alexander Carôt wrote: > Hej Allan, > > thanks for the reply ! > > >> If you want a browser based on QtWebEngine I can recommend Falkon or > >> Qutebrowser > > Theoretically this is the best choice, however, I need to be on Qt6 and they > all still seem to

Re: [Interest] QtWebEngine missing in Qt6.2.4 ?

On Freitag, 8. April 2022 16:38:51 CEST Sze Howe Koh wrote: > It is now "QT += webenginequick" (in contrast to "QT += > webenginewidgets"): > https://doc.qt.io/qt-6/qtwebenginequick-module.html > > This is a kind of source compatibility break; it would be nice if > there were deprecation warnings

Re: [Interest] Reasons why deleteLater() might not work

On Freitag, 1. April 2022 15:17:59 CEST Michael Jackson wrote: > I have a bit of code where in I am removing a QWidget from the UI and it > needs to be truly cleaned up as its parent QObject is also being cleaned > up. I thought I did the appropriate: > > layout->removeWidget(widget); > widget->se

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

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 an

Re: [Interest] Build Issues with QT 6.2.3

On Sonntag, 6. Februar 2022 00:15:54 CET BeneschTech LLC wrote: > OS: Ubuntu 20.04 LTS > Compiler Suite: clang 15 (from git) > > In the webengine build, a file fails because of -Werror. Maybe we need to > take that off of the build flags? > Did you build with the warning-are-errors feature flag

Re: The future of KDE in Debian?

On Montag, 24. Januar 2022 21:20:11 CET Marco Valli wrote: > O-h m-y g-o-d... > > https://www.phoronix.com/scan.php?page=news_item&px=Qt-Digital-Advertising-1 > .0 > > Regards Maybe I am missing something, what is the problem with a company releasing a new product for paying customers. A new pr

Re: [Development] Updating x86 SIMD support in Qt

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 distribution

Re: [Development] Updating x86 SIMD support in Qt

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, Bo

Re: [Development] Nominating Sona Kurazyan as maintainer of qt5compat

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 ch

Re: [Interest] What's up with Qt's graphic stack (6.2.1) (and WebEngine)?

On Mittwoch, 24. November 2021 18:40:07 CET Nils Jeisecke wrote: > Hi Allan, > > > We are planning to do that, but it is somewhat complicated. The > > QQuickWidget we use, only support OpenGL and Software in Qt 6.2, and > > there is no other QRHIWidget available or planned. We will be trying with

Re: [Interest] What's up with Qt's graphic stack (6.2.1) (and WebEngine)?

On Mittwoch, 24. November 2021 12:24:23 CET Nils Jeisecke wrote: > Thanks for your response Allan. > > On Tue, Nov 23, 2021 at 4:28 PM Allan Sandfeld Jensen wrote: > > We only support two backends in WebEngine currently, either WGL OpenGL or > > the software backend. The so

Re: [Interest] What's up with Qt's graphic stack (6.2.1) (and WebEngine)?

On Dienstag, 23. November 2021 14:53:30 CET Nils Jeisecke via Interest wrote: > Hi list, > > while checking out the status of Qt's graphics stack with very basic > QtQuick based applications I've made the following observations: > > 1. Windows 10 in VMWare Fusion: No window content is rendered fo

Re: [Interest] bulding Qt from git

On Montag, 25. Oktober 2021 17:27:38 CEST Alexander Carôt wrote: > Final three conclusions of this resolved thread: > > 1.) I learned that the dev branch is not necessarily stable. In this case Qt > staff is working on qtpositioning and when trying to build the dev branch > one needs to -skip qtp

Re: [Interest] Ashamed bug :)

On Samstag, 4. September 2021 09:23:45 CEST Ilya Diallo wrote: > Le sam. 4 sept. 2021 à 00:14, Thiago Macieira a > > écrit : > > On Friday, 3 September 2021 14:04:01 PDT David M. Cotter wrote: > > > there's also the rather daunting barrier to entry for folks who COULD > > > fix > > > it: > > > >

Re: [Interest] Qt 6.2 vs. Qt 5.15 – The Feature Parity Comparison – QtPDF

On Freitag, 3. September 2021 09:52:04 CEST Heiko Gerdau wrote: > Am 02.09.21 um 15:14 schrieb Benjamin TERRIER: > > Hi > > > > I just went through the latest news article: > > https://www.qt.io/blog/qt-6.2-vs.-qt-5.15-the-feature-parity-comparison > >

Re: [Interest] Configuring Qt's built-in freetype ?

On Donnerstag, 26. August 2021 13:36:42 CEST Jean-Michaël Celerier wrote: > Hi, > > for consistency, I am shipping my app with freetype on all platforms. > This looks "correct", definitely better than using macOS or Win32's font > rendering, but ! Qt's built-in freetype does not look as good than

Re: [Interest] QJsonDocument::fromVariant failing with list

On Dienstag, 8. Juni 2021 23:47:50 CEST Thiago Macieira wrote: > On Tuesday, 8 June 2021 13:57:53 PDT Jason H wrote: > > Which is neiher what I acually had but performs the same bad conversion as > > what I had. I am not sure why the QVariantList vs QList have different > > fidelity - the one with

Re: Technical question on font rendering (gamma correction)

On Donnerstag, 27. Mai 2021 16:53:26 CEST Richard Lane wrote: > Hi, > > Since Qt 5.9 .otf fonts have been rendered with alpha-blending and gamma > corrected in Qt apps / environments. The only other rendering engine to do > this is Skia (used in Chrome browser etc.). I have a hardware calibrator >

Re: [Development] QWebEnginePage and Qt 6: protected virtual functions and signals

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 handl

Re: [Development] QWebEnginePage and Qt 6: protected virtual functions and signals

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 asyn

Re: [Development] QWebEnginePage and Qt 6: protected virtual functions and signals

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. >

Re: [Development] QWebEnginePage and Qt 6: protected virtual functions and signals

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 nice

Re: Does Freetype work best with gamma 2.2, and how does it interact with KDE gamma setting?

2Fdocs.kde.org%2Fstable5%2Fen%2Fkgam > ma5%2Fkcontrol%2Fkgamma5%2Findex.html&recipient=bGludXhAY2FyZXdvbGYuY29t) > On May 4 2021, at 11:29 am, Allan Sandfeld Jensen wrote: > > Qt5 uses a gamma of 1.7 for text rendering on X11. > > > > The KDE gamma slider is an effect on

Re: Does Freetype work best with gamma 2.2, and how does it interact with KDE gamma setting?

Qt5 uses a gamma of 1.7 for text rendering on X11. The KDE gamma slider is an effect on the whole screen, not how elements are blended together inside singular apps. Not sure there is any other place we could read an expected gamma from on Linux, the only other source is using real gamma from m

Re: Does Freetype work best with gamma 2.2, and how does it interact with KDE gamma setting?

On Dienstag, 4. Mai 2021 01:07:42 CEST Richard L wrote: > Hi, > > Two questions on gamma. > I have a monitor calibrator. If I hardware calibrate my monitor to a target > gamma of 2.2 will freetype text look better than a different target gamma > (say 2.0 or 1.8)? KDE Plasma has a software gamma sl

Re: [Interest] Futur of Qt Webengine in Qt 6

On Mittwoch, 14. April 2021 13:00:01 CEST Frank Hemer wrote: > On Montag, 12. April 2021 17:35:43 CEST Allan Sandfeld Jensen wrote: > > On Montag, 12. April 2021 13:20:36 CEST Frank Hemer wrote: > > > Hi all, > > > > > > i wonder what are the plans for Qt W

Re: [Interest] Futur of Qt Webengine in Qt 6

On Montag, 12. April 2021 13:20:36 CEST Frank Hemer wrote: > Hi all, > > i wonder what are the plans for Qt Webengine in Qt 6. > > While webkit has been removed and replaced by webengine, there is still no > replacement supported by the mingw compiler yet. > As a commercial customer it was disapp

Re: [Development] Deprecated/Obsolete API that survived the transition from Qt 5 to Qt 6

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 > >> Dev

Re: [Development] Deprecated/Obsolete API that survived the transition from Qt 5 to Qt 6

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 > pro

Re: [Interest] The willy-nilly deletion of convenience, methods (was: Mixing Commercial and Open...)

On Montag, 22. März 2021 10:38:09 CET Roland Hughes wrote: > On 3/22/21 4:07 AM, Bernhard Lindner wrote: > >> Licensing FUD + death-of-perpetual-license + death-of-OpenSource-LTS + > >> Qt-6-rolling-out-incomplete + deleted-convenience-methods = > >> customers-leaving > > > > I wonder if the loss

Re: DWZ 0.14 released

Btw, question for gcc/binutils Any reason the work done by tools like dwz couldn't be done in the compiler or linker? Seems a bit odd to have a post-linker that optimizes the generated code, when optimizations should already be enabled. Best regards Allan On Montag, 8. März 2021 13:43:11 CET T

Re: [Interest] Qt WebEngine 5.15.3 tag

On Donnerstag, 4. März 2021 15:16:27 CET Benjamin TERRIER wrote: > Hi, > > Given that the Qt WebEngine module is an exception to the commercial only > LTS support, > could we have v5.15.3 tags for https://code.qt.io/cgit/qt/qtwebengine.git/ > and https://code.qt.io/cgit/qt/qtwebengine-chromium.git

Re: [Development] QFuture and C++20

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 mecha

Bug#919577: closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

On Samstag, 13. Februar 2021 14:09:36 CET you wrote: > This is an automatic notification regarding your Bug report > which was filed against the g++-8 package: > > #919577: g++-8: Can't build GN tool due to bug in raw-string parsing > > It has been closed by Debian FTP Masters . > > Their explan

Bug#919577: closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

On Samstag, 13. Februar 2021 14:09:36 CET you wrote: > This is an automatic notification regarding your Bug report > which was filed against the g++-8 package: > > #919577: g++-8: Can't build GN tool due to bug in raw-string parsing > > It has been closed by Debian FTP Masters . > > Their explan

Re: [Interest] qmake bug. Any workaround?

On Freitag, 15. Januar 2021 15:54:25 CET Alexander Dyagilev wrote: > Hello, > > I am trying to create a .pro file to compile Microsoft Detours lib. > > Failed, it generates linker error: > > detours.obj:-1: error: LNK2019: unresolved external symbol > DetourCopyInstruction referenced in function

Re: [Development] Qt6 repo

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

Re: [Development] Qt6 repo

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 regard

Re: [Development] Qt6 repo

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 maintaine

Re: [Development] Qt6 repo

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

Re: Is font rendering sharper under Wayland?

On Donnerstag, 31. Dezember 2020 05:23:53 CET Lawrence D'Oliveiro wrote: > On Thu, 31 Dec 2020 12:18:27 +0900, Tatsuyuki Ishi wrote: > >> On Thu, 31 Dec 2020 15:26:43 +1300, Lawrence D'Oliveiro wrote: > >> > >> Surely antialiasing makes hinting unnecessary. > > > > It doesn't. "Antialiasing makes

Re: [Development] Monthly maintenance break - December (Mon 14th Dec 2020)

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

Re: [Interest] Qt 6.0 removed Xml Patterns

On Freitag, 11. Dezember 2020 10:53:03 CET Robert Hairgrove wrote: > I cannot seem to find any articles about QXmlPatterns which would > explain WHY this very useful module was deprecated in 5.13 (or 5.15?), > then removed in 6.0? > > Is it a licensing issue? > No, it was just unmaintained. I thi

Re: [Interest] Will a Qt 5.x release support macOS 11?

On Donnerstag, 10. Dezember 2020 01:50:41 CET Sze Howe Koh wrote: > On Wed, 9 Dec 2020 at 20:48, Tor Arne Vestbø wrote: > > > On 9 Dec 2020, at 13:16, Tor Arne Vestbø wrote: > > > > > > Hi Benjamin, > > > > > > Qt 5 will officially support macOS 11 in upcoming 5.15 and 5.12 patch > > > releases

Re: [Interest] Will a Qt 5.x release support macOS 11?

On Mittwoch, 9. Dezember 2020 08:07:45 CET Ben Haller via Interest wrote: > Hi all. Just wondering whether there is any plan for any Qt 5.x release to > support macOS 11. At present, Qt 5.15 supports only through macOS 10.15 > (https://doc.qt.io/qt-5/macos.html#supported-versions), as far as I ca

Re: [Development] Making Binary Incompatible Changes after Qt 6.0

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 ___

Re: [Interest] Qt WebEngine, MHTML and custom schemes

On Montag, 30. November 2020 15:00:10 CET Benjamin TERRIER wrote: > Hi, > > When accessing an MHTML file using a custom local scheme (either using > 'qrc:/' or using 'QWebEngineUrlSchemeHandler') it triggers a download. > > However, when using 'file:/' the MHTML file is displayed as a web page. >

Re: [RFC] Increase libstdc++ line length to 100(?) columns

On Montag, 30. November 2020 16:47:08 CET Michael Matz wrote: > Hello, > > On Sun, 29 Nov 2020, Allan Sandfeld Jensen wrote: > > On Sonntag, 29. November 2020 18:38:15 CET Florian Weimer wrote: > > > * Allan Sandfeld Jensen: > > > > If you _do_ change it. I wou

  1   2   3   4   5   6   7   8   9   10   >