On Thu, Jun 9, 2022 at 10:14 PM Thiago Macieira
wrote:
>
> Doesn't work for libraries.
>
Can you explain please? I see this correspond to 5.0.0 until
QCoreApplication constructor called but I thought it would be 'better
than a leak'.
QCoreApplicationPrivate::app_compile_version is a part of
Hi everyone,
On Wed, Jun 8, 2022 at 5:18 PM Fabian Kosmale wrote:
>
> What remains to be done:
> - There are concerns that mixing Qt versions might lead to an unbounded
> memory leak with the current implementation.
I can't find any precedent but if we *really* want then probably we
can get
Volker:
On Fri, Mar 4, 2022 at 8:56 PM Konstantin Ritt wrote:
> Oh well, my codereview.qt-project.org account is also inaccessible. This
> is not about your attitude towards RU gov, but your attitude towards me
> personally.
>
> [image: sshot.png]
>
> Sure I can use Tor to log-in from some
My point is that if you do not restrict the access to the source code,
then people in Russia and Belarus still can: use Qt, find bugs, do
fixes. The only thing which is cut is the option to contribute back.
It affects only those who speak English and want to work with the
entire world regardless
The block is actually helping the Russian government. It wants to isolate
ru people and you want to isolate ru people too. How wise!
Leaving ru alone with propaganda won't help at all.
People who do or want to contribute to the worldwide opensource projects
are *not* the same as people who make
On Wed, May 26, 2021 at 5:25 PM Jason H wrote:
>
> 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
> hear this. I previously used this for read-only frames for analysis, i.e.
> Barcode reading and object detection. How do we do that now?
I second that.
I started to work on the error() signal renaming here:
https://codereview.qt-project.org/q/topic:%22error-occured%22
On Wed, Feb 5, 2020 at 10:12 PM Thiago Macieira
wrote:
>
> On Wednesday, 5 February 2020 09:41:58 PST Alexander Akulich wrote:
> > On Wed, Feb 5, 2020 at 6:58 PM Thi
Are we going to provide some Qt5 → Qt6 migration tool? It is trivial
to grep the sources for "SIGNAL(error(QAbstractSocket::SocketError))"
and print a warning about the dangerous Qt4-style connection.
___
Development mailing list
On Thu, Feb 6, 2020 at 4:52 PM Alex Blasche wrote:
>
> Considering that our naming convention for error() signals is inconsistent
> anyway, I favour an approach that highlights API changes early.
The convention can not be inconsistent. It can either do not exist
("we have no convention, so
Do we want to sort out all overloads of error() signal/getter in all
(essential?) modules for Qt 6?
For example, Qt Multimedia still has more than a dozen public classes
with such overloads (of a signal and a getter) in 5.15 and dev.
___
Development
On Wed, Feb 5, 2020 at 6:58 PM Thiago Macieira
wrote:
>
> The correct signal for an error situation is errorOccurred, like in
> QLocalSocket and QProcess.
Actually both QLocalSocket and QAbstractSocket renamed the "error()"
getter to keep using "error()" signal as opposed to many other Qt
On Wed, Feb 5, 2020 at 7:29 PM Alexander Akulich
wrote:
>
> On Wed, Feb 5, 2020 at 1:11 PM Ville Voutilainen
> wrote:
> >
> > Isn't that an ABI break?
>
> Yep; this is what we're doing here (we're deprecating and sorting out
> the API to break the ABI in Qt 6).
On Wed, Feb 5, 2020 at 1:11 PM Ville Voutilainen
wrote:
>
> Isn't that an ABI break?
Yep; this is what we're doing here (we're deprecating and sorting out
the API to break the ABI in Qt 6).
___
Development mailing list
Development@qt-project.org
bout it.
On Wed, Feb 5, 2020 at 6:58 PM Thiago Macieira
wrote:
>
> On Wednesday, 5 February 2020 02:12:06 PST Alexander Akulich wrote:
> > Oh, I'm sorry for the spam! You already renamed error() getter to
> > sockerError() [1], so the issue is not relevant now.
> > It's a b
.
[1]
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=5.15=94b3dd77f29a00ebbd1efdc66d75f57e1c75b152
On Wed, Feb 5, 2020 at 1:04 PM Alexander Akulich
wrote:
>
> What I'm talking about is to repeat [1] for QAbstractSocket [2] as a
> last-minute change for Qt 5.15.
> If such a patch is no
or not. (I hope and expect it to be a small change that is not sad to
drop)
[1]
https://code.qt.io/cgit/qt/qtbase.git/commit/?id=4672e319e6dd0fbaa986e056e52dbb06d78fcfa5
[2] https://doc.qt.io/qt-5/qabstractsocket.html#error-1
On Wed, Feb 5, 2020 at 12:42 PM Alexander Akulich
wrote:
>
>
Hi all,
does the 5.15 feature freeze mean that we can not adjust signal names
anymore? IIRC it was said that "deprecated-free" code for Qt 5.15
will/should be compatible with Qt 6.
IIRC there was an intention to rename
QAbstractSocket::error(SocketError) signal to errorOccured() to align
it with
I would expect a significant negative effect on the quality of Qt
shipped in Linux distributions and thus negative effect on the
Qt-based applications and Qt reputation.
A maintainer can assume a bit more backporting, but let's have some
retrospective on the current LTS:
Compared to Qt 5.12.2,
Your decision is not a reason to contribute more. It is going to hurt
the ecosystem because it makes it harder to get new developers and
users.
In some of my previous companies, we had a long release cycle so as a
Linux developer I could justify my paid time spent on upstreaming a
fix to get it
Hi Volker,
I have no idea about Go, but deferred signal emission is somewhat
useful in async programming (at least in my practice). In that case,
there is a need to 'defer' execution to continue after the control is
returned (usually in EventLoop via QMetaObject::invokeMethod(...,
Cristian,
the previous discussion is "Why can't QString use UTF-8 internally?"
There is something wrong with our maillist, the best link I found is
[1]. For some reason link to the thread head [2] is broken.
[1] https://lists.qt-project.org/pipermail/development/2015-February/040199.html
[2]
rpm packages) on
> archlinuxarm (wrote PKGBUILDs) with all the deps and some hacky qt5 linkage
> address patching for .so lib, it staring and not crashing but asking for
> more deps yet (like image resources deps, so work in progress)
>
> Alexander Akulich (Kaffeine) from Open Mobil
Hello Igor,
Does the linked solution help? See also comment #2 at
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1731646
(referenced in the stackoverflow answer).
(The subject question belongs to interest@, not development@. Please drop
development@qt-project.org in further
23 matches
Mail list logo
