(Since I didn't get any response from my last question about picking I
thought I'd try asking it in a different way.)
How do I prevent the object picking mechanism from "seeing" back-face
culled entities so that it picks entities based on what the user is
actually seeing in the scene?
Thank you!
On 6 December 2016 at 15:53, Ch'Gans wrote:
> Something else I had in mind, is to use QPainterPath::simplified()
> and/or QPainterPath::toFillPolygons() to paint a "far" item and use
> the "real" painter path to paint a "close" item. Basically as you zoom
> in, there are less items to draw, so you
I'm pretty sure QPainterPath is reentrant especially since QPainter depends
on QPainterPath and QPainter is reentrant.
On Tue, Dec 6, 2016 at 5:56 PM Ch'Gans wrote:
> On 7 December 2016 at 01:18, Philip Schuchardt wrote:
> > Since QGraphicsView can only render in the main gui thread, rendering
On 7 December 2016 at 01:18, Philip Schuchardt wrote:
> Since QGraphicsView can only render in the main gui thread, rendering in a
> separate process will prevent the blocking on the main thread. You could
> even implement "big pixel" zooming. You zoom in on the visible buffer while
> a back buffe
On 6 December 2016 at 22:26, Ulf Hermann wrote:
> Hello,
>
> I had a somewhat similar, but not quite the same problem when building the
> timeline view for the QML profiler in Qt Creator. It's currently usable with
> up to about 1 million events in the timeline and you can zoom and scroll it.
> Th
I am continually disappointed and frustrated by the way Qt is handled in
Android. I have had success with an approach up to now of using a
QObject-derived platform shim object, which is API consistent with iOS and OSX.
However it seems I'm now encountering a showstopper and I don't know what to
I'm still stuck. I don't know how to do this.
To recap: main.cpp make a singleton called platformShim and adds it as a
property to the QQmlEngine.
Then later when trying to use a Connections element to provide a signal handler
I am told
QQmlEngine: Illegal attempt to connect to PlatformShim( tha
Since QGraphicsView can only render in the main gui thread, rendering in a
separate process will prevent the blocking on the main thread. You could
even implement "big pixel" zooming. You zoom in on the visible buffer while
a back buffer is being rendered in the background by the separate process.
Hello,
I had a somewhat similar, but not quite the same problem when building the
timeline view for the QML profiler in Qt Creator. It's currently usable with up
to about 1 million events in the timeline and you can zoom and scroll it. There
might be potential for further optimization. I used
