+1
From: Development on behalf of Giuseppe
D'Angelo via Development
Sent: Thursday, May 4, 2023 1:03 PM
To: development@qt-project.org
Subject: Re: [Development] Nominating Edward Welbourne as QLocale / date/time
maintainer
Il 04/05/23 12:10, Marc Mutz via Dev
+1
+1
From: Development on behalf of Lorn Potter
Sent: Wednesday, November 30, 2022 9:40 AM
To: development@qt-project.org
Subject: Re: [Development] Nominating Mårten Nordheim and Timur Pocheptsov as
new co-maintainers of Qt WebSocket
+1 !!
On 29/11/2022 11:
+1 for both
From: Development on behalf of Giuseppe
D'Angelo via Development
Sent: Wednesday, August 24, 2022 9:27 PM
To: development@qt-project.org
Subject: Re: [Development] Nominating David and Eskil as Qt Wayland maintainers
Il 24/08/22 13:24, Thiago Maciei
It is not just Drag&Drop that is affected by this issue. The fix should also
consider my notes from https://bugreports.qt.io/browse/QTBUG-69716
From: Development on behalf of Zhang JiDe
Sent: Monday, June 6, 2022 10:49 AM
To: Volker Hilsheimer ; Giuseppe D'Ange
Arne Vestbø
3 Gatis Paeglis
I would like to propose Liang Qi as the new maintainer. He has been
with the company for more than a decade.
Gatis Paeglis.
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/lis
> AFAIK Gatis is working on this (see
> https://bugreports.qt.io/browse/QTBUG-69414 ). There is a magic define
I have currently postponed that work. The goal is to move all auto tests that
rely on mouse to DEFINES += QTEST_QPA_MOUSE_HANDLING. Here is an example of
before vs after: https://cod
+1, long-overdue 🙂
From: Development on behalf of Tor Arne
Vestbø
Sent: Thursday, May 16, 2019 6:14 PM
To: Volker Hilsheimer
Cc: Qt development mailing list
Subject: Re: [Development] Nominating Mikhail Svetkin for Approver status
+2
> On 16 May 2019, at 16:45,
+1
From: Development on behalf of Martin
Smith
Sent: Wednesday, May 15, 2019 1:51 PM
To: Topi Reiniö; Paul Wicking; development@qt-project.org
Subject: Re: [Development] Nominating Ryan Chu for Approvership
+1 from Martin
___
> Does it mean that the binaries we distribute should work on that?
I have been maintaining XCB plugin and the bundled xkbcommon and xcb 3rd party
sources based on the assumption that an answer to this question is - yes.
From: Development on behalf of Tony
Sar
> library doesn't provide another way to build itself.
libxkbcommon changelog for 0.7.2
https://lists.freedesktop.org/archives/wayland-devel/2017-August/034721.html
"Added a Meson build system as an alternative to existing autotools build
system. The intent is to remove the autotools build in o
> It’s convenient to quote what adds fuel to the fire of this discussion. Hence
> my attempt to add water by quoting what I thought it still relevant.
In a real life never add water to a fuel fire. It will cause even more fire 😊
Gatis.
From: Development on
b
m we really need a replacement.
See https://codereview.qt-project.org/#/c/42990/
Gatis Paeglis.
From: Development on
behalf of Jean-Michaël Celerier
Sent: Thursday, September 13, 2018 8:37:57 AM
To: Thiago Macieira
Cc: development
Subject: Re: [Development] Orp
; will strongly oppose any new APIs added to it.
+1 for deprecating qtx11extras as well and moving the code closer to actual
plugin. It is frustrating to have all that boilerplate code for 1 header file -
qx11info_x11.h
Gatis Paeglis.
From: Development on
beh
oes not have GCC 5.
From: Development on
behalf of Gatis Paeglis
Sent: Sunday, July 15, 2018 12:17:52 PM
To: Thiago Macieira; development@qt-project.org
Subject: Re: [Development] Raising the minimum Core Language to C++14 for
Linux/XCB
> There has been no
> There has been no reply on this subject. Shall I assume silence is consent and
> we can begin using C++14 constructs in the XCB plugin?
I think I know which patch you are talking about and then my answer is we
can't. The code that you
are looking at I want to eventually move in some common pl
+1 from me too.
From: Development on
behalf of Timur Pocheptsov
Sent: Wednesday, April 25, 2018 2:09:22 PM
To: Edward Welbourne; development@qt-project.org
Subject: Re: [Development] Nominating Mårten Nordheim as an approver
+ 1 from me, fully agree with every
ution. But if it works, it works.
From: Mitch Curtis
Sent: Monday, April 16, 2018 5:28:07 PM
To: Gatis Paeglis; development@qt-project.org
Subject: RE: QTestLib: sending mouse move and release events outside windows
I think that maybe we’re talking about different
eep on receiving all mouse events,
then you need to grab the mouse/pointer. That is different API from the above
Enter/Leave scenario. QTestLib currently does not support any of the above.
From: Mitch Curtis
Sent: Monday, April 16, 2018 1:14:23 PM
To: Gatis P
That warning message was added by [1]. I have never fully understood the
motivation for that warning. The documentation from [2] does not say if global
coordinates are allowed. QTest sends all mouse events down to
QWindowSystemInterface, which does expect a window as an argument, or nullptr
on
> here is the link to the Wiki on "Writing good tests" as requested at QtCS:
> http://wiki.qt.io/Writing_good_tests .
Regarding the following point:
> If you must track mouse move events, consider replacing the use of
> QTest::mouseMove where the first parameter is a QWidget with the overlo
> I'd like to push this discussion, because if code is converted to a new
> base, it should be clear to everyone HOW to do so.
I agree regarding consistency. If we are spending time on this, then it should
be done properly. I think Qt Coding Conventions wiki should be moved to
somewhere where c
n the team when qtdeviceutilities is the topic.
Gatis Paeglis.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
22 matches
Mail list logo
