Re: [Interest] Qt Positioning on iOS?

2020-03-06 Thread Israel Brewster
Ok, clearing everything and trying again seems to have worked. Guess something got stuck somewhere along the line. I still have to test if geofencing will work with the app in the background though. Thanks! --- Israel Brewster Software Engineer Alaska Volcano Observatory Geophysical Institute -

Re: [Interest] Qt Positioning on iOS?

2020-03-06 Thread ekke
you should add something like this into your info.plist: NSLocationWhenInUseUsageDescription $(PRODUCT_NAME)usesLocationtogetWeatherDataforcurrentLocation “NSLocationAlwaysAndWhenInUseUsageDescription” $(PRODUCT_NAME)usesLocationtogetWeatherDataforcurrentLocation Am 06.03.20 um 19:08 schrieb

[Interest] Qt Positioning on iOS?

2020-03-06 Thread Israel Brewster
Simple question: how do I get Qt Positioning (C++) to work on iOS (current versions of everything)? I tried the code on the Qt Positioning page, and apparently the various createDefaultSource() calls all worked (I tried both QGeoPositionInfoSource and QGeoAreaMonitorSource), in that they returne

[Interest] Using Qt Enums as QML object keys... Qt6?

2020-03-06 Thread Jason H
First, sometimes I find that not all Qt enums are exported to QML. Like the QProcess::ProcessState, IIRC. Are these bugs? Shouldn't all Qt enums in QObject recived classes be Q_ENUM()ed? Next, QML's uage of these is normally an int, when I print these with console.log() they come out as 0,1,2,3,

Re: [Interest] Callgrind under Linux

2020-03-06 Thread Giuseppe D'Angelo via Interest
Il 06/03/20 18:13, Christian Kandeler ha scritto: By the way: Is there a list of such environment variables that let you configure Qt behavior at runtime? I wish it was (or similarly there was one of the compile macros to define). I've tried to write one myself, but it falls out of sync quit

Re: [Interest] Callgrind under Linux

2020-03-06 Thread Christian Kandeler
On Fri, 6 Mar 2020 17:54:48 +0100 Giuseppe D'Angelo via Interest wrote: > Il 06/03/20 15:56, Konstantin Tokarev ha scritto: > >> We did find a closed issue about > >> it:https://bugreports.qt.io/browse/QTBUG-62118 > >> But no solution or hint about the cause of this. > > You can configure Qt wit

Re: [Interest] Callgrind under Linux

2020-03-06 Thread Giuseppe D'Angelo via Interest
Il 06/03/20 15:56, Konstantin Tokarev ha scritto: We did find a closed issue about it:https://bugreports.qt.io/browse/QTBUG-62118 But no solution or hint about the cause of this. You can configure Qt with explicitly disable RDRAND, or use same hack as used in tst_qrandomgenerator.cpp, passing S

[Interest] PySide2 signal argument name?

2020-03-06 Thread Jérôme Godbout
Hi, how does one emit a signal with argument from python and access them on the qml side? in python: mySignal = Signal(int, str) // the following cannot be made Signal(int foo, str bar), maybe I got the syntax wrong? in qml: onMySignal: { // ???, how does one access the argument if they do not

Re: [Interest] Callgrind under Linux

2020-03-06 Thread Konstantin Tokarev
06.03.2020, 17:30, "Jérôme Godbout" : > Hi, > > one of my colleague is trying to start valgrind callgrind to profile a part > of the application using Qt 5.12.7, latest Qt Creator with Ubuntu. the start > command look like this: > > valgrind --tool=callgrind --instr-atstart=no ./OpM-3_DU_SW > >

Re: [Interest] Callgrind under Linux

2020-03-06 Thread Jérôme Godbout
We did find a closed issue about it: https://bugreports.qt.io/browse/QTBUG-62118 But no solution or hint about the cause of this. From: Interest On Behalf Of Jérôme Godbout Sent: March 6, 2020 9:27 AM To: interest@qt-project.org Subject: [Interest] Callgrind under Linux Hi, one of my colleague i

[Interest] Callgrind under Linux

2020-03-06 Thread Jérôme Godbout
Hi, one of my colleague is trying to start valgrind callgrind to profile a part of the application using Qt 5.12.7, latest Qt Creator with Ubuntu. the start command look like this: valgrind --tool=callgrind --instr-atstart=no ./OpM-3_DU_SW it did the macro for the start/stop and dump. Added the

Re: [Interest] WebEngine proxy whitelist

2020-03-06 Thread Allan Sandfeld Jensen
On Friday, 6 March 2020 11:02:55 CET Benjamin TERRIER wrote: > On Thu, 5 Mar 2020 at 21:54, Allan Sandfeld Jensen wrote: > > I don't know why they would say that, as far as I know it works. In any > > case I > > would suggest using the same mechanism we use for testing PAC support: > > The command

Re: [Interest] WebEngine proxy whitelist

2020-03-06 Thread Benjamin TERRIER
On Thu, 5 Mar 2020 at 21:54, Allan Sandfeld Jensen wrote: > I don't know why they would say that, as far as I know it works. In any > case I > would suggest using the same mechanism we use for testing PAC support: > The command line argument "--proxy-pac-url=file://$$PACFILE" > > And since it is