On 2023-02-18 13:42, Axel Spoerl via Development wrote:
Hi David,
The margin for recognizing a mouse resize is handled by the window
manager, hence not controlled by Qt.
(...)
That depends if the QDockWidget is using native decorations or not, see
[1].
When not using native decos,
On 2023-01-23 14:25, Jörg Bornemann via Development wrote:
(...)
One ugliness I've noticed: CMAKE_UNITY_BUILD is documented to not play
well with CMAKE_EXPORT_COMPILE_COMMANDS. This might hurt users of
clangd (using clangd with Qt's sources).
Yes, but probably you won't be developing with
On 2022-01-03 13:40, Lars Knoll wrote:
(...)
One other possible solution to improve compile times is the hack we
used 15 years ago in KDE, where we grouped many .cpp files into one
compilation unit. There’s however a balance needed here, as it reduces
the efficiency of -j, but maybe compiling
On 2022-01-03 08:43, Marc Mutz wrote:
Hi,
The Qt Creator folks have noted that compilation of Qt projects
against Qt 6.2 is sometimes almost twice as slow as it was in 5.15:
https://bugreports.qt.io/browse/QTBUG-97601
While we have some ideas where this may come from (including more std
On 2020-11-18 07:34, Oliver Wolff wrote:
Hi
On 16/11/2020 23:29, Sérgio Martins via Development wrote:
On 2020-11-16 21:57, Thiago Macieira wrote:
On Monday, 16 November 2020 13:38:06 PST Cristian Adam wrote:
LLVM.org clang.exe binary reports the x86_64-pc-windows-msvc target,
which
is Clang
On 2020-11-16 21:57, Thiago Macieira wrote:
On Monday, 16 November 2020 13:38:06 PST Cristian Adam wrote:
LLVM.org clang.exe binary reports the x86_64-pc-windows-msvc target,
which
is Clang/MSVC. clang-cl is just a different command line options
parser,
which always sets the *-msvc target.
On 2020-11-15 16:29, Thiago Macieira wrote:
On Sunday, 15 November 2020 04:34:49 PST Kevin Kofler via Development
wrote:
Thiago Macieira wrote:
> At least one platform -- not a main one -- will stop working.
IMHO, it would be useful in such cases to specify which platform you
are
talking
On 2020-04-23 14:55, Thiago Macieira wrote:
On Thursday, 23 April 2020 05:25:33 PDT Vitaly Fanaskov wrote:
Provide clang-based tools to (semi-)automatically port users' code
bases to
a new version of Qt. These tools might either fix a code or at least
add a
comment in potentially problematic
On 2020-02-28 18:32, Thiago Macieira wrote:
On Friday, 28 February 2020 07:28:34 PST Matthew Woehlke wrote:
If we had to do it over again, it might make sense to follow Python
and
make signals *objects* instead of *methods*. Then the code would look
like:
this->emptied.emit(...);
Binary
On 2020-02-21 13:00, Ville Voutilainen wrote:
On Fri, 21 Feb 2020 at 14:58, Sérgio Martins
wrote:
> Why do I need to know that it's a signal being emitted? How is that
> "vital information"? I could just as well
> invoke any other callback, but I find myself not exactly yearning for
> being
On 2020-02-21 12:41, Ville Voutilainen wrote:
On Fri, 21 Feb 2020 at 14:30, Mitch Curtis wrote:
> > without any annotation is not what we want. We'd miss vital information
> and reduce readability.
> Can you please explain what that vital information is?
How can you tell if it's a signal
On 2020-01-07 12:52, Roland Winklmeier wrote:
Second, I switched my nightly build to 5.14 branch and was building
debug
binaries as usual. Configure arguments:
configureArguments=-developer-build -debug -opensource -nomake examples
-nomake tests -confirm-license -opengl desktop -dbus -openssl
On 2019-12-06 16:42, René J.V. Bertin wrote:
Hi,
(...)
This was after I got this error from an attempt to build QtWebEngine
5.12.6 with /usr/bin/c++ which points to GCC 8:
So you're building QtWebEngine with GCC 8 while Qt was built with clang
mkspec ?
```
Using gcc version 4.2, but at
On 2019-11-29 08:15, Ville Voutilainen wrote:
On Wed, 27 Nov 2019 at 17:52, Sérgio Martins via Development
wrote:
(...)
I suggest we rename such signals, as KDE is already doing for KF6
(maybe
leave the old signatures there, to reduce Qt6 SIC)
There's also a new clazy check 'overloaded
Hi,
The Qt5 PMF connect syntax is wonderful and very elegant compared to Qt
4.
Unless, ofc, you have overloaded signals, which makes it painful to
write and read. Not even qOverload makes it look much better.
I suggest we rename such signals, as KDE is already doing for KF6 (maybe
leave
On 2019-08-20 16:56, Bogdan Vatra via Development wrote:
Hi,
Isn't silly to have so many wrappers around a such a simple thing as
strings? All the major frameworks out there (i.e. Java, C#) they have a
single
String which does all the magic.
We do have a single one that does all the
On 2019-08-06 22:49, Sérgio Martins via Development wrote:
On 2019-08-06 13:48, René J. V. Bertin wrote:
Joerg Bornemann wrote:
Unfortunately, this isn't possible at the moment.
This issue is tracked in QTBUG-47629.
Thanks, I'll try the patch!
Can you also check how much memory
On 2019-08-06 13:48, René J. V. Bertin wrote:
Joerg Bornemann wrote:
Unfortunately, this isn't possible at the moment.
This issue is tracked in QTBUG-47629.
Thanks, I'll try the patch!
Can you also check how much memory is occupied by reading that 100 MB
file ?
My memory is hazy but I
On 2019-06-15 07:45, Bogdan Vatra via Development wrote:
Hi,
În ziua de joi, 13 iunie 2019, la 18:22:14 EEST, Thiago Macieira a
scris:
On Thursday, 13 June 2019 01:06:06 PDT Bogdan Vatra via Development
wrote:
> Hi,
>
> There is one more missing feature to add to your list: build & debug
>
On 2019-05-25 21:55, Bernhard Lindner wrote:
Using XML without using a schema validator is (or at least should be)
a no-go. So even if
the Qt XML component should be continued in some way, Qt should also
not lack a schema validator.
Have you tried other C++ schema validators ?
We should be
On 2019-05-22 09:09, Alex Blasche wrote:
From: Volker Hilsheimer
A version-controlled configuration file with user names and privileges
would provide that,
with the added benefit of making the list of approvers easily visible
to everyone with
On 2019-05-21 15:58, Thiago Macieira wrote:
On Tuesday, 21 May 2019 00:15:04 PDT Bernhard Lindner wrote:
Unlucky me. Deprecation of these two components literally broke every
application I have ever written using Qt. I hope they will have new
maintainers some day.
Note I said QtXml is
On 2018-12-13 13:48, NIkolai Marchenko wrote:
This non obvious (from function name) behaviour actually caused
infinite
loop regression in our code just recently.
The person used it inside a while loop thinking it will loop upwards
and
stop.
If your compiler supports it, you should get a
On 2018-11-20 08:38, Richard Gustavsen wrote:
Hi,
I'd like to nominate Christian Ehrlicher for approver rights.
+1
Regards,
--
Sérgio Martins | sergio.mart...@kdab.com | Senior Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA
On 2018-10-31 11:40, Martin Koller wrote:
In this file I find:
// auto generated. DO NOT EDIT.
class QCssScanner_Generated
Who/what generates this file ?
Looks like is generated by util/lexgen
$ cd util/lexgen
$ qmake && make
$ ./lexgen css3-simplified.lexgen
Regards,
--
Sérgio Martins |
On 2018-10-29 15:56, Thiago Macieira wrote:
On Monday, 29 October 2018 04:43:09 PDT Olivier Goffart wrote:
> 1) it will copy containers. For Qt containers, that's rather cheap (two
> atomic refcount operations), but it's not free. And for Standard Library
> containers, that is likely very
On 2018-10-07 09:56, Lars Knoll wrote:
IMO #pragma once is both safer and nicer to use than classic header
guards.
Regarding safety, clang has -Wheader-guard which catches typos in header
guards, so most of our codebase should be ok.
(Would be nice to have clang-cl -Werror builds on our
On 2018-10-07 09:56, Lars Knoll wrote:
Hi,
Just a quick question: Does anybody have any good arguments against us
starting to use #pragma once instead of header guards throughout our
code base?
Hi Lars,
This was already discussed back in January:
On 2018-09-05 06:58, Uwe Rathmann wrote:
On Tue, 04 Sep 2018 20:51:38 +0200, Martin Koller wrote:
added the native X11 graphicssystem support from Qt4 to Qt5
Very cool.
Andrew told me that there were 2 concurrent attempts to revive X11 as
the
situation for running widget applications on
Hi,
Looks like some 'override' keywords crept into a few destructors. This
is probably because clang-tidy warns about it (and now QtCreator).
IMO we should avoid it, as it's misleading. Dtors are a special case and
have completely different semantics. They don't replace their base class
On 2018-01-19 18:32, Thiago Macieira wrote:
On Friday, 19 January 2018 09:26:10 PST Edward Welbourne wrote:
Jaroslaw Kobus (19 January 2018 17:09)
> "give" may be confused with "get", which is usually an accessor. I may
> also think "Am I giving (to QCoreApplication)" or "The
>
On 2018-06-21 04:40, Thiago Macieira wrote:
Hello
Yesterday during the PDXCPP Meet Up, I was asked if we had come up with
a good
solution to the increase in size of native binaries on Android when
switching
from GCC to Clang. I reported I had no idea there was even a problem.
So, what's the
On 2018-06-18 10:04, Frederik Gladhorn wrote:
Hi all,
as part of the closing ceremony of this year's Qt Contributors' Summit
we
agreed to start using clang-format, to have fewer discussions around
coding
style and rather focus on the actual code.
I have not yet thought about all angles, how
33 matches
Mail list logo
