On Thursday, 11 April 2019 06:43:25 PDT Olivier B. wrote:
> I just noticed that my COPIES fail in Qt 5.11.1+ in visual studio
> solutions. This seems caused by the change in
> mkspecs/features/file_copies.prf; to use $(QINSTALL) instead of the
> previous $$QMAKE_COPY.
> But unlike in makefiles, QIN
On Thursday, 11 April 2019 06:44:40 PDT Jason H wrote:
> Thanks! If it's that easy, and more reliable, why doesn't qApp->quit() do it
> that way?
Because it is not "quitLater", it's "quitNow". The difference between those
two things is the sequencing of the event loop interruption compared to oth
On Wednesday, 10 April 2019 15:18:55 PDT Jason H wrote:
> In a QObject who is exported to QML, and is instantiated just below the
> top-level Window: // in the object's open() method:
> if (!_serialPort.open(QIODevice::ReadWrite))
> qApp->quit(); // won't actually quit - no use if I can't
Hello,
I try to get the city and country from coordinates.
For this I use the functions geocode/reverseGecode. The pointer is valid but if
the function is accessed with valid coordinates from the GeoPositionInfoSource
signal, I get a EXC_BAD_ACCESS
I use “osm” as the geo service provider.
Any
You are indeed correct. I am iterating on a minimal test case and the first versions do work. I'm working back to the minimal case that I experienced the issue. This may take some time though.
Thank you for your help
Sent: Thursday, April 11, 2019 at 10:07 AM
From: "Konstantin Shegunov"
On Thu, Apr 11, 2019 at 4:57 PM Jason H wrote:
> Update on this:
> It didn't work. I called it, nothing (discernable) happened. Got a bunch
> of serial port not open errors
>
Something else's amiss. Here's the test-case:
#include
#include
int main(int argc, char *argv[])
{
QCore
Update on this:
It didn't work. I called it, nothing (discernable) happened. Got a bunch of serial port not open errors
Sent: Thursday, April 11, 2019 at 9:44 AM
From: "Jason H"
To: "Konstantin Shegunov"
Cc: "Interests Qt"
Subject: Re: [Interest] Signals, slots before the event loop st
Thanks! If it's that easy, and more reliable, why doesn't qApp->quit() do it that way?
Sent: Thursday, April 11, 2019 at 8:54 AM
From: "Konstantin Shegunov"
To: "Jason H"
Cc: "Giuseppe D'Angelo" , "Interests Qt"
Subject: Re: [Interest] Signals, slots before the event loop starts?
On
I just noticed that my COPIES fail in Qt 5.11.1+ in visual studio
solutions. This seems caused by the change in
mkspecs/features/file_copies.prf; to use $(QINSTALL) instead of the
previous $$QMAKE_COPY.
But unlike in makefiles, QINSTALL is not defined in the visual studio
solutions :(
_
On Thu, Apr 11, 2019 at 3:48 PM Jason H wrote:
> What is the best way to do that? I think in the past, I used a 0ms timer,
> but that always feels janky.
>
QMetaObject::invokeMethod(qApp, &QCoreApplication::quit,
Qt::QueuedConnection);
is my preference.
_
> Sent: Thursday, April 11, 2019 at 7:35 AM
> From: "Giuseppe D'Angelo via Interest"
> To: interest@qt-project.org
> Subject: Re: [Interest] Signals, slots before the event loop starts?
>
> Il 11/04/19 00:18, Jason H ha scritto:
> > In a QObject who is exported to QML, and is instantiated just bel
Thanks Jérôme for pushing me into the right direction.
Now I see where I went wrong.
The buffers data assignment must be done as follows:
data: { var vertexArray = new Float32Array([ -1., 1., 0., 1., 1., 0.,
-1., -1., 0., 1., -1., 0. ]); return vertexArray; }
Cheers, Volker
Am 10.04.2019 um
12 matches
Mail list logo