On Wed, Jan 8, 2014 at 5:31 AM, Sebastian Lehmann wrote:
> Hi,
>
> I'd find it "natural" if there was something like a QtCore plugin.
> Then, QtQuick and Qt3D (and other stuff) could depend on it; i.e.
> something analogous to the existing Qt modules dependency, but in the
> QML world.
>
> I alrea
ect: Re: [Development] Qt.vector3d() and friends
>
> Hi,
>
> I'd find it "natural" if there was something like a QtCore plugin.
> Then, QtQuick and Qt3D (and other stuff) could depend on it; i.e.
> something analogous to the existing Qt modules dependency, but in
Hi,
I'd find it "natural" if there was something like a QtCore plugin.
Then, QtQuick and Qt3D (and other stuff) could depend on it; i.e.
something analogous to the existing Qt modules dependency, but in the
QML world.
I already encountered situations in which I wanted to use QtQuick
stuff
Sean Harmer sayeth:
> Hi,
>
> during the development of the new version of Qt3D's QML API we have come
> across an interesting (well if you like that kind of thing) problem.
>
> The issue is that at present the QML value type helpers for types such as
> QVector3D are provided by QtQuick meaning th
Hi,
during the development of the new version of Qt3D's QML API we have come
across an interesting (well if you like that kind of thing) problem.
The issue is that at present the QML value type helpers for types such as
QVector3D are provided by QtQuick meaning that we have to do
import QtQuic
