Re: [Development] Moving Qt's undo framework out of Qt Widgets

> On 5 Apr 2017, at 12:37, Oswald Buddenhagen wrote: > > On Wed, Apr 05, 2017 at 09:24:15AM +, Mitch Curtis wrote: >> So, should this get its own module, and if so, can widgets depend on >> it? >> > an own module just for that seems over the top - i don't think

Re: [Development] State of 5.9 and dev branches

Thanks for cleaning this up quickly! When it comes to testing, do we want to go one step further and make the tests be completely independent of the current time? We would like to avoid time bombs like these, and if something _is_ going to fail at some future date we would like to know so right

[Development] QUIP 8: High-DPI Support

Hi all, A draft of QUIP 8: High-DPI Support is now available: https://codereview.qt-project.org/#/c/194524 Comments are welcome! Either here or on codereview. The plan is to write this up in there parts: 1) High-DPI terms and overview of other platforms 2) High-DPI support rationale

Re: [Development] Flaky auto tests on macOS 10.12

> On 19 Jun 2017, at 08:34, J-P Nurmi wrote: > > Hi all, > > After a few successful qt5.git CI rounds, auto tests were enabled for macOS > 10.12 in the CI last week. [*] Even though many flaky auto tests had been > already blacklisted on macOS 10.12 earlier >

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

> On 16 Jun 2017, at 23:21, Thiago Macieira wrote: > > On Friday, 16 June 2017 13:23:07 PDT Thiago Macieira wrote: >> QDEBUG : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) >> QHostAddress("fe80::250:56ff:feab:4818%eth1") >> FAIL! :

Re: [Development] Flaky auto tests on macOS 10.12

> On 19 Jun 2017, at 13:09, Tony Sarajärvi wrote: > > It is the intention that we do this. But we're constantly running, not beside > our horse, but after it. We have just begun activating ourselves to discuss > about 5.10 platforms and we have FF coming up in two weeks

Re: [Development] Getting QtWebEngineProcess.app to run in sandbox after being signed

Hi, Not sure if I can be of much help, but: - This thread discusses and solves a similar problem: https://forum.qt.io/topic/49250/solved-qtwebengineprocess-not-working-in-sandboxed-application - If this could be reduced to a simple sandboxed-app-with-helper-process test case (no QtWebEngine

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

> On 30 Aug 2017, at 09:30, Olivier Goffart wrote: > > Am Dienstag, 29. August 2017, 17:30:56 CEST schrieb Thiago Macieira: >> On Tuesday, 29 August 2017 01:10:53 PDT René J.V. Bertin wrote: >>> Which we just rediscovered :) Funny though, apparently 1 misdirected >>>

Re: [Development] Apple officially deprecates OpenGL

> On 4 Jun 2018, at 22:20, Walter Purvis wrote: > > Is this going to cause issues with Qt Quick applications? I.e., will Qt Quick > apps be broken or unacceptably slow in future versions of macOS? (The next > version of macOS merely deprecates OpenGL, but it raises the question of when > it

[Development] QTest qWaitForWindowExposed and qWaitForWindowActive (was: Consistently flaky test QTabWidget test)

> On 2 May 2018, at 09:29, Thiago Macieira wrote: > > FAIL! : tst_QTabWidget::paintEventCount() Compared values are not the same >Actual (tab2->count): 2 >Expected (1) : 1 >Loc: [tst_qtabwidget.cpp(573)] > [on macOS 10.12] Hi, I recently

Re: [Development] Mismatch of display resolutions and window sizes in Android applications

This is by design for Qt::AA_EnableHighDpiScaling: you get the logical window size. The physical size can be computed by multiplying with QQuickWindow::effectiveDevicePixelRatio(). For QtLocation it looks like you have to enable high-dpi tiles by setting “osm.mapping.highdpi_tiles" (or a

Re: [Development] Using Native web view on OS X

> On 25 Jan 2018, at 21:05, Steve Schilz wrote: > >> 22.01.2018, 18:37, "Alberto Mardegan" : >> Hi all! >> ??I've developed a desktop application which uses the WebView QML >> module, with the hope of publishing it in the Apple

Re: [Development] Using native webview on OS X

> On 23 Jan 2018, at 15:11, Konstantin Tokarev <annu...@yandex.ru> wrote: > > 23.01.2018, 17:09, "Morten Sørvig" <morten.sor...@qt.io>: >> >> The QtWebEngine requirement does seem to run counter to the purpose of the >> QtWebView module. &

Re: [Development] LLVM and Qt

> On 30 Jul 2018, at 06:00, Thiago Macieira wrote: > > On Sunday, 29 July 2018 13:36:43 PDT Lisandro Damián Nicanor Pérez Meyer > wrote: >> It would also be pretty nice to know if there is a policy with respect the >> llvm supported version. As they do not keep ABI compatibility distros >>

Re: [Development] LLVM and Qt

> On 30 Jul 2018, at 06:00, Thiago Macieira wrote: > > On Sunday, 29 July 2018 13:36:43 PDT Lisandro Damián Nicanor Pérez Meyer > wrote: >> It would also be pretty nice to know if there is a policy with respect the >> llvm supported version. As they do not keep ABI compatibility distros >>

Re: [Development] Upgrade the XCode running in the CI's macOS 10.11

> On 9 Jul 2018, at 02:15, Thiago Macieira wrote: > > This is the second time I've run into a compiler bug with that XCode's > ancient > Clang. > > Can we please upgrade the XCode installation there to the latest available > for > macOS 10.11? > > If that's the latest, can we declare

Re: [Development] Using native webview on OS X

> On 22 Jan 2018, at 18:22, Alberto Mardegan > wrote: > > On 22/01/2018 18:49, Konstantin Tokarev wrote: >> From [1] it seems like QT_MAC_USE_NATIVE_WEBVIEW environment variable >> is required to use native backend. >> >> [1]

Re: [Development] Qt for WebAssembly

> On 9 Mar 2018, at 19:09, Tim Murison wrote: > I'd also like to echo and hopefully amplify what Jason H said about > qmlweb. IMO, this is the solution that Qt should be embracing and > integrating upstream. qmlweb aims to do what Qt has always done, make > cross-platform

Re: [Development] Qt for WebAssembly

> On 9 Mar 2018, at 15:53, Jason H wrote: > > > I don't want to steal your thunder, but what is fundamentally different about > this approach this time? Why will the results be any different? Oh, who knows what will happen. But there are indicators that this time may be

Re: [Development] Qt for WebAssembly

> On 13 Mar 2018, at 02:15, Jason H wrote: > >> On 03/12/2018 11:42 PM, Jason H wrote: >>> 1. True ActiveX was extremely limiting, NaCL less so, Emscripten/asm.js >>> less so. I can't really argue much difference between WebAssembly and >>> asm.js though, given asm.js's

Re: [Development] Qt for WebAssembly

> On 13 Mar 2018, at 15:27, Svenn-Arne Dragly wrote: > > I also think Qt for WebAssembly is exciting because it opens up the > possibility to show a minimal demo of a full application in the browser. > Instead of showing a video of the application on a product page,

Re: [Development] Qt for WebAssembly

> On 9 Mar 2018, at 13:57, Morten Sørvig <morten.sor...@qt.io> wrote: > > * (No) thread support > > Wasm and Emscripten do have pthreads support. However this requires > SharedArrayBuffer, > which has been disabled in all major browser after recent secu

[Development] Qt for WebAssembly

Hi all, As you may have noticed work on Qt for WebAssembly is underway. With the recent updates the wip/webassembly branches are now based on Qt 5.11, which they will continue to be while we work on bringing up Qt Quick. The tracking bug for the project is QTBUG-63917 (with subtasks). This is a

Re: [Development] should 5.12 build on iOS ?

> On 28 Dec 2018, at 17:19, Martin Koller wrote: > > A colleague built 5.12 for iOS but got linker errors: > > Undefined symbols for architecture arm64: > "_CGImageDestinationCreateWithData", referenced from: > QMacPasteboardMimeTiff::convertFromMime(QString const&, QVariant, >

[Development] Qt for WebAssembly 5.13

Hi all, Qt for WebAssembly shipped as a tech preview for 5.12, and for 5,13 we want to fill in some of the missing pieces, and also make Q_OS_WASM a supported platform. Supported here does not mean that everything that does not work today will work, but rather that what we claim will work

Re: [Development] QTBUG-61258 and Qt3D status

Hi, > On 14 Dec 2018, at 14:07, Massimo Callegari wrote: > (also cause of broken video playback on core context QTBUG-51064) I was able to spend some time looking at the related QTBUG-62694, and: - The fault appears to be that the implementation in AVFVideoFrameRenderer::renderLayerToFBO()

Re: [Development] Orphan modules

> On 12 Sep 2018, at 11:02, Edward Welbourne wrote: > > Tor Arne Vestbø (12 September 2018 10:25) >> I think the qtmacextras module should be maintained by the same >> [maintainer] as macOS, Morten. > > That would depend on - Morten: are you willing to take it on ? To be honest I assumed

Re: [Development] Assistant WebKit/WebEngine support

> On 24 Jun 2019, at 22:44, Lars Knoll wrote: > > >> On 24 Jun 2019, at 21:54, Tor Arne Vestbø wrote: >> >> >> >>> On 24 Jun 2019, at 14:43, Simon Hausmann wrote: >>> >>> I have two more numbers to add: Compressed (7z) the download size would >>> be around ~44 MB. I measured on Windows

Re: [Development] Qt Static Package

We’re successfully building Qt Quick Controls 2 statically for the WebAssembly target, so it should be possible. I don’t think we’re doing anything special. The test cases include the “gallery” example. The generated qml_plugin_import.cpp file has the style plugins as well:

[Development] Updated high-DPI support for Qt 5.14

Hi all, We’ve recently merged several patches which improves Qt’s high-DPI support. The changes include: * Support for fractional device pixel ratios (e.g. Windows 150%) * Support per-screen DPI in more places like QStyle * Cleanup of configuration API and options. These fixes applies mostly

Re: [Development] Updated high-DPI support for Qt 5.14

> On 13 Sep 2019, at 17:50, Thiago Macieira wrote: > > On Friday, 13 September 2019 08:35:59 PDT Elvis Stansvik wrote: >>> What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS? >> >> I wonder too. I assume they've not been removed? The latter is the one that >> KDEs

Re: [Development] Updated high-DPI support for Qt 5.14

> On 27 Sep 2019, at 17:04, Thiago Macieira wrote: > > On Friday, 27 September 2019 03:56:44 PDT Morten Sørvig wrote: >> Configuring Windows is a good example here: you set the slider to one of >> 100% - 125% - 150% - 175% - 200% depending on monitor pixel density an

Re: [Development] Updated high-DPI support for Qt 5.14

> On 16 Sep 2019, at 15:21, Florian Bruhin wrote: > > Looks like that change didn't add a changelog entry and didn't bother to > update > the documentation at all… I’ve updated https://wiki.qt.io/New_Features_in_Qt_5.14 . We’ll add similar content to the change log once it gets posted. The

Re: [Development] Updated high-DPI support for Qt 5.14

> On 26 Sep 2019, at 04:48, Thiago Macieira wrote: > > On Wednesday, 25 September 2019 05:54:20 PDT Morten Sørvig wrote: >> I see two differences between setting the DPI vs a factor: >> >> - You set one value per screen (DPI) instead of two (DPI & factor) >

Re: [Development] Updated high-DPI support for Qt 5.14

> On 3 Oct 2019, at 09:44, Mark De Wit wrote: > > Is there a chance that the high-dpi work will fix the dpi-awareness of the > Fusion theme as reported in https://bugreports.qt.io/browse/QTBUG-74100 ? Yes, looks like an easy fix: https://codereview.qt-project.org/c/qt/qtbase/+/276261 > >

[Development] Stepping down as Qt for macOS maintainer (but don't worry)

Hello all, I’d like to formally step down as Qt for macOS maintainer, and suggest that Tor Arne Vestbø takes over in my place. He’s already maintaining Qt for iOS (and QPA), and has done a lot of good work on macOS over the past couple of years. Cheers, Morten

Re: [Development] Please remove this warning: Warning: QT_AUTO_SCREEN_SCALE_FACTOR is deprecated. Instead use: QT_ENABLE_HIGHDPI_SCALING to enable platform plugin controlled per-screen factors.

> On 15 Nov 2019, at 20:54, Thiago Macieira wrote: > > Just remove it. Make it work with the current settings, despite there being a > better way. > -- Yep, this did turn out to be a bit spammy. How about this: - QT_AUTO_SCREEN_SCALE_FACTOR is Done on X11, and will continue to work

Re: [Development] Updated high-DPI support for Qt 5.14

> On 24 Sep 2019, at 17:54, Thiago Macieira wrote: > > On Monday, 16 September 2019 06:00:27 PDT Morten Sørvig wrote: >> Could KDE possibly set per-screen DPI instead of a scale factor? >> Applications can now use the >> QGuiApplication::setHighDpiScaleFactorRou

Re: [Development] Updated high-DPI support for Qt 5.14

> On 1 Oct 2019, at 23:18, Christoph Cullmann wrote: > > Hi, > > actually, unrelated to how one can configure the stuff, at the moment, > I see still a lot of Qt internal rendering artifacts for fractional scaling. > > See https://bugreports.qt.io/browse/QTBUG-66036 > > For some I made now

Re: [Development] Qt 5.13 & 5.14 add device-independent pixels to device-dependent

> On 27 Jan 2020, at 20:16, Thiago Macieira wrote: > > I had fixed this prior to 5.13 but the patch was never accepted: > https://codereview.qt-project.org/c/qt/qtbase/+/188493 > https://bugreports.qt.io/browse/QTBUG-58329 > https://build.opensuse.org/package/view_file/ >

Re: [Development] Qt 5.13 & 5.14 add device-independent pixels to device-dependent

> On 29 Jan 2020, at 04:14, Thiago Macieira wrote: > > On Tuesday, 28 January 2020 06:48:53 PST Morten Sørvig wrote: >> There are several possible solutions: >> >> 1) The scale factor for screen positions is 1: [the current choice] >> Simple to implement. De

Re: [Development] Qt 5.13 & 5.14 add device-independent pixels to device-dependent

> On 14 Feb 2020, at 21:46, Thiago Macieira wrote: > > On Friday, 14 February 2020 07:18:10 PST Thiago Macieira wrote: >> On Thursday, 13 February 2020 14:13:52 PST Christoph Cullmann wrote: >>> I had in Kate/Konsole and Co. broken repainting as soon as winId() was >>> called >>> on any

Re: [Development] Qt 5.13 & 5.14 add device-independent pixels to device-dependent

> On 13 Feb 2020, at 18:53, Thiago Macieira wrote: > > On Tuesday, 28 January 2020 19:14:50 PST Thiago Macieira wrote: >> I don't know what makes KMail different. I thought it was the use of a >> qtwebengine window, but the qtwebengine examples seem to work fine. >> >> My current theory is

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

> On 23 Apr 2020, at 11:30, Ville Voutilainen > wrote: > > On Thu, 23 Apr 2020 at 12:25, Philippe wrote: >> >> Almost all the time I second your positions, but not this time ;) >> >> QList is historically a cause of ambiguity, and Qt6 is the chance to get rid >> of that. > > Indeed.

[Development] Qt 6 high-dpi support

> > P.S. Consider a similar type of "technical debt" being settled by Qt: I'm > thinking of the "DPI awareness" setting in 5.14, i.e. for a default widgets > program, Qt nowadays tells WIndows that it's "DPI aware" and wants the truth > about screen coordinates, even on those portable PCs

Re: [Development] Windows maintainer change

+1 from me as well, and I’d like to thank Friedemann for his work on Qt on Windows through the years. Morten > On 15 Jun 2021, at 11:13, Tor Arne Vestbø wrote: > > Hear hear! +1 > >> On 15 Jun 2021, at 11:05, Shawn Rutledge wrote: >> >> +1 >> >> Thanks for the work that all 3 of you have

Re: [Development] Confused about HiDPI scaling and fonts

Hello! (This is mailing list is for discussing development _of_ Qt - inter...@qt-project.org is the correct list for Qt usage questions) The setting looks correct and fonts should be resized. There is no need to set QT_ENABLE_HIGHDPI_SCALING on the environment when setting the

Re: [Development] Confused about HiDPI scaling and fonts

It may be easier to show the expected behaviour with a video: https://www.youtube.com/watch?v=vgGnPTgQqjo The important thing is that text visual size and window visual size is kept in sync as the system DPI changes. From the report I got the impression that this was maybe not the

[Development] Nominating David Skoland as approver

contributions and is currently taking on getting auto-tests running in the CI system. I trust him to be a good approver. https://codereview.qt-project.org/q/owner:david.skoland%2540qt.io https://codereview.qt-project.org/q/reviewer:david.skoland%2540qt.io Best Regards, Morten Sørvig

Re: [Development] QTBUG-95930 / QTBUG-99546 need some attention

On 19 May 2022, at 16:32, Ilya Fedin mailto:fedin-ilja2...@ya.ru>> wrote: On Thu, 19 May 2022 14:20:05 + Morten Sørvig mailto:morten.sor...@qt.io>> wrote: Looks inconclusive to me - no clear consensus either way. (I’m also not sure if it's a bug - it’s just "the

Re: [Development] QTBUG-95930 / QTBUG-99546 need some attention

On 17 May 2022, at 22:14, Ilya Fedin mailto:fedin-ilja2...@ya.ru>> wrote: On Tue, 10 May 2022 19:40:02 + Morten Sørvig mailto:morten.sor...@qt.io>> wrote: On 9 May 2022, at 16:47, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On Monday, 9 May 2022 07:07:23

Re: [Development] QTBUG-95930 / QTBUG-99546 need some attention

> On 9 May 2022, at 16:47, Thiago Macieira wrote: > > On Monday, 9 May 2022 07:07:23 PDT Morten Sørvig wrote: >> b) In practice, QT_SCREEN_SCALE_FACTORS has become a system setting since >> it’s being set on behalf of the user. This means the values should be >> su

Re: [Development] QTBUG-95930 / QTBUG-99546 need some attention

On 8 May 2022, at 21:02, Ilya Fedin mailto:fedin-ilja2...@ya.ru>> wrote: 9 months has passed since the initial report and it's still in a state where it's unknown is it a bug or an intended behavior. Would be nice Thanks for the reminder! This is about the behaviour of the

Re: [Development] Introducing: test batching

> On 29 Aug 2022, at 13:48, Thiago Macieira wrote: > > On Monday, 29 August 2022 05:34:48 -03 Mikołaj Boć wrote: >> We plan to enable the feature on CI for WASM. Since that has not yet been >> done, breaking the tests unintentionally is possible. With CI on, it will >> become everyone’s

[Development] Fixing the 6.5 build when cross-compiling (missing Qt6::qtprotobufgen)

Hi, I’m running into a configure error for a top-level Qt 6.5 wasm build. I use “init-repository --module-subset=all” to check out the Qt modules. The host system does not have protobuf installed, which configure warns me about during the host tools build (this is fine): -- Configuring

[Development] Qt for WebAssembly feature freeze exceptions

Hi all, We have two pending changes for the wasm platform which I'd like to request a feature freeze exception for: * Adding the initial accessibility backend. This feature will initially be opt-in, and we are aiming to make it as non-disruptive as possible. A couple of

[Development] Nominating Mikołaj Boć as approver

Hi, I’d like to nominate Mikołaj Boć as an approver for the Qt project. Mikołaj joined the Qt Company earlier this year and hit the ground running. He has contributed features and many bug fixes for the Qt for WebAssembly platform integration, as well as bug fixes for other parts of Qt. I

Re: [Development] Nominating Mikołaj Boć as approver

ect.org/q/reviewer:Mikolaj.Boc%40qt.io> (copy/paste error on my part :) Morten On 21 Dec 2022, at 15:21, Morten Sørvig via Development mailto:development@qt-project.org>> wrote: Hi, I’d like to nominate Mikołaj Boć as an approver for the Qt project. Mikołaj joined the Qt Company earlier this year

Re: [Development] The QT_SCREEN_SCALE_FACTORS rounding problem is still annoyingly valid

> On 25 Jan 2023, at 14:39, Ilya Fedin wrote: > > > This is a follow-up to the thread I started a year ago. The fix was > momentally reverted back then leading to me patching Qt all that time. I > still get reports from users using distribution packages as I obviously > can't patch their Qt.

Re: [Development] The QT_SCREEN_SCALE_FACTORS rounding problem is still annoyingly valid

On 27 Jan 2023, at 18:04, Ilya Fedin wrote: My patch doesn't modify setScreenFactor, so the rounding is applied only to the variable value (and to the property on QScreen object, as it's the only remaining source without rounding in QHighDpiScaling::screenSubfactor), so the programmatic

[Development] Nominating Piotr Wierciński for approval status

I would like to nominate Piotr Wierciński for approver rights in the Qt project. Piotr joined the Qt company early 2013 and has since then contributed to Qt for WebAssembly. This includes many bugfixes and also larger efforts such as getting tests running in the CI system. Piotr is a pleasure

Re: [Development] Trouble getting reviews in months and years

On Apr 12, 2024, at 11:51, Ilya Fedin wrote: On Thu, 11 Apr 2024 10:53:07 + Morten Sørvig wrote: - Should Qt read Gdk settings? Should the XCB platform plugin read Gdk settings? The current approach is that we stick to X11-level settings, at least as far as DPI is concerned. I hope

Re: [Development] Trouble getting reviews in months and years

Hello Ilya! > On Apr 9, 2024, at 00:17, Ilya Fedin wrote: > > > 2. https://codereview.qt-project.org/c/qt/qtbase/+/444859 which is 1.5 > years old and no review > This one could be candidate for discussion on the mailing list. There are two issues: - Should Qt read Gdk settings? Should the