On Tue, 10 May 2022 19:40:02 +
Morten Sørvig wrote:
> > 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
On Fri, 20 May 2022 10:31:03 +
Morten Sørvig wrote:
> That’s fair point. The QT_ environment variables are often sharp
> tools, and do make it possible to configure Qt in such a way that it
> appears broken.
>
> I’m not sure I see what KDE could realistically change here - given
> that they
On Thu, 19 May 2022 14:20:05 +
Morten Sørvig wrote:
> Looks inconclusive to me - no clear consensus either way. (I’m also
> not sure if it's a bug - it’s just "the current behavior")
>
> However, we might be able to find a way forward: the rounding policy
> is also under user control with
В Fri, 20 May 2022 10:31:03 +
Morten Sørvig пишет:
> Continuing on the more pragmatic track, I’ve pushed a change to add
> rounding support, along with some additional testing:
> https://codereview.qt-project.org/c/qt/qtbase/+/412296
>
> Morten
Has the work stalled? Would be really nice to
В Wed, 13 Jul 2022 06:50:14 +
Tarja Sundqvist пишет:
> Hi all!
>
>
>
> We have released the Qt 6.4.0 Beta2 today. As earlier, you can get
> it via the Qt online installer. Source packages are also available in
> the Qt Account and download.qt.io. Delta to the beta1 attached.
>
>
>
>
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
if someone finally decided on this so I can push the patch to gerrit or
create a bug report on KDE bugtracker.
On Wed, 07 Sep 2022 08:45:45 +0200
Kevin Kofler via Development wrote:
> It scares me that a Qt 7 is already being planned or discussed at
> all, considering that your major consumers such as KDE Plasma are not
> even ported to Qt 6 yet! (Note that I am talking about *consumers*
> here, not only
> They do not seem to close or dismiss the menu. They capture that fine
> for Print Screen. My guess would be that they pass the event back to
> the operating system and/or windowing manager. I do not know whether
> Qt or a Qt application could easily do the same.
I just tried to press PrtSc
В Wed, 19 Oct 2022 08:30:30 +0100
Laszlo Papp пишет:
> I have also tried various Qt applications, like Inkscape, where this
> also does not work as soon as you bring up a context menu.
But Inkscape is a gtk2 application
___
Development mailing list
On Thu, 20 Oct 2022 08:03:25 -0700
Thiago Macieira wrote:
> On Thursday, 20 October 2022 00:48:33 PDT Ilya Fedin wrote:
> > I just tried to press PrtSc while having an open context menu in
> > Firefox and it's closed as soon as I pressed the key, Spectacle
> > created
On Fri, 16 Sep 2022 06:32:38 +
Shawn Rutledge wrote:
> Another aspect that I haven’t kept up with very well is how
> containerized applications should do printing. We have “portal”
> support for file dialogs, for example, but is CPDB intended to work
> the same way regardless whether the
I'm trying to force my window to follow aspect ratio. On other systems
this is possible by changing position/size progrmatically, but Wayland
doesn't let to change window position. I heard that it's possible to
achieve what I want by passing a buffer less than surface size. I
tracked
On Tue, 29 Nov 2022 11:14:08 +
JiDe Zhang wrote:
> Hi All, I am developing a wrapper of wlroots with Qt, it's
> https://github.com/vioken/qwlroots. Now, I have been implement a
> tinywl example use it:
> https://github.com/vioken/qwlroots/blob/main/examples/tinywl/main.cpp,
> there is a
Forgot to mention: this wasn't a problem until Qt 6 as the application
was using the Qt::AA_DisableHighDpiScaling that was disabling reading
this variable in Qt 5. So it's kind of regression.
___
Development mailing list
Development@qt-project.org
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. The application is just unusable for those users
using KDE's
В Fri, 27 Jan 2023 12:38:34 +
Morten Sørvig via Development пишет:
> > 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
On Mon, 13 Mar 2023 20:28:58 +0400
Ilya Fedin wrote:
> But your original change hasn't moved Q_NOREPLY, it added inline to it
> and QDBusPendingReply
Ah, the inline was on another line, haven't noticed at first, so
probably it should be "inline Q_NOREPLY void " rather t
On Wed, 15 Feb 2023 14:19:29 +
Morten Sørvig via Development wrote:
> 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
On Mon, 20 Mar 2023 13:44:30 +
Edward Welbourne via Development wrote:
> The means to achieve this appear [2] to hinge on setting the active
> codepage for the application in a manifest file, that it gets combined
> with after it is linked.
>
> [2]
>
On Thu, 16 Mar 2023 07:55:37 -0700
Thiago Macieira wrote:
> If Q_NOREPLY were [[qt::no_reply]], where would the correct place be?
>
Isn't the goal to move it where it was previously? Before [1] it was
after inline and before void, after [1] it become before inline and now
[2] moves it after
On Mon, 13 Mar 2023 08:38:54 -0700
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 Tue, 20 Jun 2023 14:12:25 +
Jani Heikkinen via Development wrote:
> Qt 6.5 status:
>
> - Branching from '6.5' to '6.5.2' done
>
> - Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt
> 6.5.2 content later this week
>
> - The target is to release Qt 6.5.2 Wed 28th June
On Thu, 13 Jul 2023 17:55:51 +
Tarja Sundqvist via Development wrote:
> Hi Mathieu & all,
>
> unfortunately, Qt 6.5.2 has been delayed. The final test round for
> the release candidate is currently ongoing, though. My current
> estimate is that we can release 6.5.2 at the beginning of next
On Tue, 30 May 2023 16:55:51 -0700
Thiago Macieira wrote:
> After trying myself, it turns out the problem is not QTimer or the
> event dispatcher, but the Windows API. The following test:
> https://codereview.qt-project.org/c/qt/qtbase/+/480705
> passes on Linux (glib and native), macOS but
On Wed, 28 Jun 2023 19:21:30 -0300
Lisandro Damián Nicanor Pérez Meyer wrote:
> Hi,
>
> On Tue, 20 Jun 2023 at 02:41, Ilya Fedin wrote:
> >
> > Hi,
> >
> > I have a change[1] I made two years ago. People were adding another
> > people to reviewers as
ore detail what this is about. Cheers
> Axel
>
> Von: Development im Auftrag von
> Ilya Fedin Gesendet: Donnerstag, 29. Juni 2023
> 00:43 An: development@qt-project.org
> Betreff: Re: [Development] Can't get review for more than two years
>
> On Wed
Hi,
I have a change[1] I made two years ago. People were adding another
people to reviewers as no one of them had knowledge to review the
change. Since some time people has just started ignoring pings. More
than two years has passed but the change is still there, with no votes
nor clear
On Wed, 13 Mar 2024 07:58:20 +
Marc Mutz via Development wrote:
> Hi,
>
> In API review, we detected some overrides that changed the access
> specifier vis-a-vis the original virtual function
> (https://wiki.qt.io/Things_To_Look_Out_For_In_Reviews#Polymorphic_Classes
> Item 5.3).
>
>
On Thu, 24 Aug 2023 15:37:05 -0400
Eduardo Hopperdietzel wrote:
> Hi David,
>
> I've made a little Wayland app that uses both SHM and DMA, and I
> tested it on Weston, Sway, and my own compositor. I also tried it on
> three different machines: two with Intel i7 CPUs and one with a
> smaller ARM
Hello, I was asked to write here about QFreedesktopApplication[1]. My
main intention was to get nice GApplication APIs that implement a
number of XDG standarts to be accessble by Qt applications. The main
thing is running the GApplication instance, although I made a number of
wrapping APIs to use
Hello, I was asked to write here about QFreedesktopApplication[1]. My main intention was to get nice GApplication APIs that implement a number of XDG standarts to be accessble by Qt applications. The main thing is running the GApplication instance, although I made a number of wrapping APIs to use
On Sun, 24 Apr 2022 07:53:49 -0700
Thiago Macieira wrote:
> Hello Ilya
>
> Please explain why we need this API in the first place. If an
> application requires a Qt event loop that links to GLib and use
> GMainLoop, then they can easily link to glib directly themselves and
> access
On Sun, 24 Apr 2022 19:43:09 +0200
Kevin Kofler via Development wrote:
> So if Qt implements the same D-Bus interface using GApplication, will
> that not break the KDE applications that use the existing
> KDBusService?
No, I made the uniqueness opt-in via setFlags
> And why is using the
On Sun, 24 Apr 2022 20:01:10 -0700
Thiago Macieira wrote:
> Then this should be implemented regardless of whether glib is used.
>
> We also need to know whether the KDE equivalent is being used and
> avoid confusing the launcher by emitting twice.
As I said, it's opt-in...
> I don't agree
On Fri, 8 Dec 2023 15:33:04 +0100
Elias Steurer via Development wrote:
> Hi Volker,
>
> Thanks for the update on the Qt Contributors Summit. It's great to
> hear about the initiatives to make the contribution process smoother,
> especially for newcomers.
>
> However, while setting up a Gerrit
On Fri, 22 Mar 2024 12:32:45 +
Jani Heikkinen via Development wrote:
> Hi all!
>
> Qt 6.7.0 RC2 is available via online installer. Src packages are also
> available in the Qt Account and download.qt.io. Delta to the first rc
> attached.
>
> The target is to release Qt 6.7.0 final release
В Mon, 08 Apr 2024 22:36:56 -0500
Thiago Macieira пишет:
> On Monday 8 April 2024 17:17:04 CDT Ilya Fedin wrote:
> > 2. https://codereview.qt-project.org/c/qt/qtbase/+/444859 which is
> > 1.5 years old and no review
>
> Submitted during Christmas break and no ch
On Mon, 08 Apr 2024 22:36:56 -0500
Thiago Macieira wrote:
> On Monday 8 April 2024 17:17:04 CDT Ilya Fedin wrote:
> > 2. https://codereview.qt-project.org/c/qt/qtbase/+/444859 which is
> > 1.5 years old and no review
>
> Submitted during Christmas break and no ch
I have multiple changes which hang for months and years which no idea
what to do to push them forward... I tried to write there asking for
review but reviewers seem to just ignore the messages...
1. The oldest change I have is
https://codereview.qt-project.org/c/qt/qtbase/+/343628 which is 3
On Thu, 11 Apr 2024 10:53:07 +
Morten Sørvig wrote:
> 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
> >
>
On Tue, 16 Apr 2024 08:12:51 +
Morten Sørvig wrote:
> Should this be up to the application (somehow)? There is more than
> one way to handle DPI settings on X11, so we could enable apps to
> make choices which are different from the Qt default.
Well, there's only one way currently
On Mon, 6 May 2024 09:51:56 +0200
Lars Knoll via Development wrote:
> I’m a bit unsure about the windows code, but on Linux
> and macOS it’s simply launching ‘xdg-open’ or ‘open’.
That's not really the truth for Linux: it also does D-Bus calls to
xdg-desktop-portal. While this isn't really a
42 matches
Mail list logo
