Good morning,
for me both suggestions (first separate the code, then moving it to Qt)
sounds good to me.
+1
André
Am 30.11.23 um 23:00 schrieb apoenitz:
On Thu, Nov 30, 2023 at 07:41:06PM +, Fabian Kosmale wrote:
Hi,
I agree that it would be nice to properly separate Solutions (to enfor
On Thu, Nov 30, 2023 at 07:41:06PM +, Fabian Kosmale wrote:
> Hi,
>
> I agree that it would be nice to properly separate Solutions (to enforce their
> reusability, and to make it easier to include the module into other projects).
>
> I'm also convinced that Jarek would do a good job as the ma
On Thursday, 30 November 2023 20:36:03 CET Fabian Kosmale via Development
wrote:
> this change (https://codereview.qt-project.org/c/qt/qtbase/+/512774) was
> intentional and aimed to resolve
> https://bugreports.qt.io/browse/QTBUG-117514. However, given the lack of a
> changelog, I don't believe t
Hi,
I agree that it would be nice to properly separate Solutions (to enforce their
reusability, and to make it easier to include the module into other projects).
I'm also convinced that Jarek would do a good job as the maintainer of the
module.
I have however two questions:
1. How this will affe
Hi,
this change (https://codereview.qt-project.org/c/qt/qtbase/+/512774) was
intentional and aimed to resolve
https://bugreports.qt.io/browse/QTBUG-117514. However, given the lack of a
changelog, I don't believe
the BIC break between 6.6.0 and 6.6.1 was intentional.
I hope Marc or Thiago have
Hi all.
As you may know, we've started to separate parts of code originally created
specifically for Qt Creator from other parts of Creator's infrastructure in
order to make them more easily reusable in other projects or possible become a
proper Qt module at some time. These "Solutions" are curr
On Tue, Nov 21, 2023 at 05:00:43PM +0100, André Somers wrote:
> > If not, could we start propagating QTreeWidgetItem or QStandardItem in
> > those examples instead to avoid reinventing?
>
> No, please. I would suggest to instead deprecate these classes, at minimum
> the Widgets (QListWidget, QTabl
My binary built against Qt v6.6.0 from the online installer fails to run
against v6.6.1 from the same source. The problem is a missing symbol...
_ZN14QReadWriteLock16destroyRecursiveEP21QReadWriteLockPrivate@Qt_6_PRIVATE_API
...which demangles to
QReadWriteLock::destroyRecursive(QReadWriteLock
Il 30/11/23 11:49, Giuseppe D'Angelo via Development ha scritto:
It turns out that not every platform officially supported by Qt ships
OpenSSL 3 yet. Some of these platforms are promising to maintain OpenSSL
1 for a little while longer,
Orthogonal but related, the patch kind of exposed a serio
Hi,
OpenSSL 1 has reached EOL last September:
https://www.openssl.org/blog/blog/2023/09/11/eol-111/
Qt has supported OpenSSL 3 for a while, and so last week I pushed a
patch to drop OpenSSL 1 support from Qt. "This has made a lot of people
very angry and been widely regarded as a bad move.
10 matches
Mail list logo
