Hi,
Has anyone been able to build Qt 5.3.2 with MSVC 2017? I'm running into a
weird error that I think is related to how I set up my mkspecs/win32-msvc2017
file.
The error during the build that happens right away is:
Creating qmake...
execute: File or path is not found (make)
execute: File or
o Macieira [thiago.macie...@intel.com]
Sent: September 23, 2018 1:12 AM
To: interest@qt-project.org
Subject: Re: [Interest] Qt 5.3.2 with msvc2017
On Saturday, 22 September 2018 17:42:42 PDT Russell, Matthew wrote:
> Hi,
>
> Has anyone been able to build Qt 5.3.2 with MSVC 2017? I'm r
Hi,
Is it possible with QML to read a buffer operated on by a compute shader?
If I understood this message properly,
http://lists.qt-project.org/pipermail/interest/2016-November/025167.html , then
this wasn't possible in 5.8, but might be available in 5.9.
Specifically, I'm showing point data
9.
Have a look at the buffercapture example
(qt5/qt3d/tests/manual/buffercapture-qml).
Let me know if you have any trouble.
On miƩrcoles, 1 de marzo de 2017 22:09:15 (CET) Russell, Matthew wrote:
> Hi,
>
> Is it possible with QML to read a buffer operated on by a compute shader?
Have a look at the buffercapture example
(qt5/qt3d/tests/manual/buffercapture-qml).
Let me know if you have any trouble.
On miƩrcoles, 1 de marzo de 2017 22:09:15 (CET) Russell, Matthew wrote:
> Hi,
>
> Is it possible with QML to read a buffer operated on by a compute shade
With Qt 5.8.0 on a Windows Surface, I'm experiencing flickering in my app that
has both a SceneGraph (modelled after the Squircle example) and Qt3D renderer
(RenderSettings, with a viewport, with a RenderSurfaceSelector) in a QQuickView
The flicking only seems to occur when the QML and SceneGrap
Hi,
How can I simulate/emulate gestures with Qt?
I worry that the answer is obvious, but I've spent a while now trying to figure
out how to use Qt Simulator or Qt Emulator to absolutely no avail. I don't
even see options for it in QtCreator.
Ultimately all I want to do is test some pinch gest
Hi
Is there a way to have a scene graph (called on beforeRendering) clear the
buffers of a Scene3d on top of it?
i.e. I have a scene graph under my QML (similar to the Squircle example) where
I call glClearColor, and a Scene3d with a RenderSurfaceSelector.
glClearColor clears the scene graphs
Why can my Q_GADGET be read perfectly in QML (JS) but not my Q_OBJECT?
I created a class, registered it (Q_DECLARE_METATYPE), and then push instances
of it into a QVariantMap. If the object is a Q_GADGET my JS can read it
perfectly, but when I switch it to a Q_OBJECT, the objects are blank.
I
ter, and a Q_GADGET is always
passed by value. That means Q_GADGET is only suitable for smallish
self-contained classes, because it will always be copied.
> On 13 Apr 2017, at 20:31, Russell, Matthew wrote:
>
> Why can my Q_GADGET be read perfectly in QML (JS) but not my Q_OBJECT?
>
Hi,
My QML `ListView` doesn't show my data until I perturb it with the mouse (e.g.
just drag it up and down.) After this the view shows the model without issue.
Is there way to kick this `ListView` into working?
I'm using Qt 5.8 on Linux 14.04. My model is a subclass of
`QAbstractListModel`
Hi,
Is there anything that could prevent QQuickWindow::sceneGraphInvalidated from
being invoked?
I've integrated the "Scene Graph - Rendering FBOs in a thread" (
http://doc.qt.io/qt-5/qtquick-scenegraph-textureinthread-example.html ) example
into my code.. It's hard to post code samples, but
(not able to reply to my previous message, hopefully subject matching will
work.)
I re-read the description of the order of the signals in the comments on this
bug report : https://bugreports.qt.io/browse/QTBUG-42620
My problem turned out to be that I had my renderers owned by some QObjects in
I've encountered the weirdness issue with my Qt 5.9.1 app. When launched, it
seems to be fine until I check the memory usage with Task Manager, at which
point, the memory footprint slowly increases from ~100 MiB to a few gigs and my
computer shuts it down or crashes. I do not see this behaviou
14 matches
Mail list logo