below
-Original Message-
From: Development On Behalf Of Mike
Krus via Development
Sent: torstai 4. huhtikuuta 2024 17.14
To: Tuukka Turunen
Cc: Qt Project Development
Subject: Re: [Development] Removing Qt 3D from release configuration in dev
branch
Hi everyone
Hi everyone
Disclaimer: I’m one of the contributors to Qt3D, and a KDAB employee.
As mentioned, early discussions have taken place between KDAB and tQtC around
this issue,
although much needs to be clarified as to why, how and when this happens.
As mentioned by Tuukka, Qt3D was introduced in
Hi
It was reinstated as a default in 6.4 I believe. It’s certainly installed in my
6.4.0 installation.
Mike
> On 30 Nov 2022, at 08:30, Mark De Wit wrote:
>
> Dear Qt devs,
>
> I have a Qt 3D application that relies on the RHI render plugin, and is stuck
> on Qt 6.1.x due to the GPL
> On 2 Jun 2022, at 09:24, Edward Welbourne wrote:
>
> Sze Howe Koh (01 June 2022 16:03) wrote:
>> Changing the default of Qt Print Support to "Unassigned" sounds
>> reasonable in this case. How does this occur?
>
> I believe Jira admins do this on request.
> I suggest Mike e-mail Alex Blasche
Hi
I’ve been investigating QTBUG-103881 for 6.4 (dev)
The test instantiates a qml scene using QQmlComponent.
The scene has some items and sets some properties. For the record, this is the
scene [1]
The component is created properly (I think) and the scene is then created, but
some of the
Some configurations still seem to use qmake for some parts:
Hi
> On 20 Aug 2020, at 08:28, Jani Heikkinen wrote:
>
> Hi,
>
> Kindly reminder: Qt 6.0 Feature Freeze will be in effect 31st August 2020,
> see https://wiki.qt.io/Qt_6.0_Release .
That page mentions “Structure and platform freeze” on June 30th.
Can you elaborate what this covered and what
g
> visibility to the "other" types in moc generated code by using Q_MOC_INCLUDE
> in A to include B and vice versa. Does that make sense?
>
>
> Simon
> From: Development on behalf of Mike Krus
> via Development
> Sent: Monday, April 27, 2020 11:52
> To: Qt
Hi
I have 2 classes, A and B, derived from QObject, each have a property
of type pointer-to-other-class. So
class A : public QObject {
Q_PROPERTY(B *foo …)
…
};
And:
class B : public QObject {
Q_PROPERTY(A *foo …)
…
};
Because of the circular dependency, I can’t #include the full class
Hi
we just noticed that, as now reported inQTBUG-83486,
a recent patch to Qt 3D [1] has broken all applications that
use Scene3D and non-default aspects (in particular the often
required animation aspect).
This is now fixed in [2]
Would it be possible to bring forward the release of
> On 23 Jan 2020, at 14:36, Konstantin Tokarev wrote:
>
>
>
> 23.01.2020, 15:56, "Laszlo Agocs" :
>> 4. Longer term, let's rather focus the energy on improving performance (via
>> SSE, NEON) in math3d, as that would probably bring more benefits to Qt Quick
>> and Quick 3D than spending
having worked with him on Qt Auto: +1 from me
> On 2 Oct 2019, at 09:18, Simon Hausmann wrote:
>
> Hi,
>
> I would like to nominate Dominik for approver status. He started contributing
> to Qt back in 2013 and has been working primarily on the Qt automotive and
> embedded related bits. After
Hi
we’re busy doing the work but have a couple of blog posts in the pipeline.
It’s unclear if we’ll have benchmarks we can share, we’ll see.
Also, those specific changes make a difference in specific conditions so YMMV.
Will keep everyone posted,
Mike
> On 26 Sep 2019, at 08:48, Massimo
> On 4 Apr 2019, at 15:06, Tuukka Turunen wrote:
>
>
>
> On 04/04/2019, 10.54, "Development on behalf of Mike Krus via Development"
>
> wrote:
>
>> Since Qt 3D Studio now contains, for lack of a better word, a fork of much
>> o
Hi Laszlo,
thanks for all this updated information.
> On 2 Apr 2019, at 14:14, Laszlo Agocs wrote:
> First, a qt-labs repository request:
>
> Repo name: qtshadertools
> Name: Qt Shader Tools
> Responsible person: me
> Purpose: will import https://git.qt.io/laagocs/qtshadertools here. This is
15 matches
Mail list logo
