Hi,
I would like to script the creation and usage of all of the QWidget classes.
What’s the likelihood of acceptance (of a merge request) if I were to add
Q_INVOKABLE to the constructors and methods of each QWidget derived class and
QWidget itself?
I guess the downside is enlarged meta objects
--
Alex
Hi,
This update was concluded. Please report any issues and concerns to
jira-ad...@qt-project.org.
--
Alex
From: Development on behalf of Alex
Blasche via Development
Sent: Thursday, 21 November 2024 14:53
To: development@qt-project.org
Su
On Wednesday 27 November 2024 00:02:58 Pacific Standard Time Jani Heikkinen via
Development wrote:
> [17:08:31] vohi[M]: no, they're going in
> [17:08:43] the issue is rewriting the qtscxmlc patches
> [17:09:14] we also need to turn qtactiveqt testing back on
> [17:09:56] same issue: qtactiveq
On Wednesday 27 November 2024 06:51:23 Pacific Standard Time Volker Hilsheimer
via Development wrote:
> As per the comments to that change, it’s a) not going to fly and b) not the
> choice a single person can make, even if that person is the maintainer of
> Qt Core 🙂
>
> A more pragmatic and scal
> On 27 Nov 2024, at 02:18, Thiago Macieira wrote:
>
> On Tuesday 26 November 2024 16:32:20 Pacific Standard Time Tor Arne Vestbø
> via
> Development wrote:
>>> Someone who cares about Windows/MSVC may want to take the mantle here,
>>> because cpp-winrt will be disabled for C++17.
>>
>> Plea
Qt 6.8 status
* Qt 6.8.1 release content is frozen, packages are created and package
testing is ongoing
* The target is to release Qt 6.8.1 Fri 29th of November
Qt 6.9 status
* New snapshot from 'dev' created but testing is still ongoing
* Qt 6.9 platform and module freeze is in
