I'm compiling my Qt application with C++17 on Windows with the Qt-provided
MinGW 7.3.0 and the Qt definition of a byte is conflicting with the new one
defined in the standard (http://wg21.link/p0298r3).
Here's a snippet of the issue: https://paste.ubuntu.com/p/Y73FRVqq2n/
Full build log:
https://
Il 24/07/19 09:25, Vadim Peretokin ha scritto:
I'm compiling my Qt application with C++17 on Windows with the
Qt-provided MinGW 7.3.0 and the Qt definition of a byte is conflicting
with the new one defined in the standard (http://wg21.link/p0298r3).
Here's a snippet of the issue: https://paste
Hi all,
I'm not sure this is solvable via QtPurchasing currently, but if anyone has
solved it, I'd love to hear about your approach.
Normally a purchase flow goes something like this:
1. Purchase happens.
2. Transaction information is returned.
3. If transaction was approved, some value is stor
Hi,
It’s been a while I had a look at Qt Purchasing, but generally
https://doc.qt.io/qt-5/qinappstore.html#restorePurchases was talking to the
store (at least Microsoft Store) to re-verify active purchases.
If something has been refunded and/or revoked, then those should not be listed
anymore.
Ok, so I'm supposed to call restorePurchases() and then check whether
"onPurchaseRestored" was *not* called for a specific Product? And in that
case assume it was not purchased and/or refunded?
That's going to be very error prone I think, because then I guess I'll have
to do all the usual timeout
On Tuesday, 23 July 2019 07:27:27 PDT Nikos Chantziaras wrote:
> Ugh. Having the call happen on every object creation sounds even uglier.
> It seems it's best to roll our own. Probably a lazily initialized global
> static object that you can add functors to before main() and then run
> all functors
A bit of further testing on this has offered a few more conclusions.
I was wrong in assuming network connectivity was needed. Turning on Flight
Mode and calling restorePurchases() still yields a callback of
onPurchaseRestored(), so the billing api must cache this information
locally on the phone s
On 24/07/2019 17:23, Thiago Macieira wrote:
On Tuesday, 23 July 2019 07:27:27 PDT Nikos Chantziaras wrote:
Ugh. Having the call happen on every object creation sounds even uglier.
It seems it's best to roll our own. Probably a lazily initialized global
static object that you can add functors to
On Wed, Jul 24, 2019 at 11:38 AM Giuseppe D'Angelo via Interest <
interest@qt-project.org> wrote:
> Il 24/07/19 09:25, Vadim Peretokin ha scritto:
> > I'm compiling my Qt application with C++17 on Windows with the
> > Qt-provided MinGW 7.3.0 and the Qt definition of a byte is conflicting
> > with
Hi,
I would recommend to open a ticket at
https://bugreports.qt.io/secure/Dashboard.jspa That way the developer taking
care of this module will be able to track and comment in the right place.
BR,
Maurice
From: René Hansen
Sent: Wednesday, July 24, 2019 4:49 PM
To: Maurice Kalinowski
Cc: in
Thanks for your mail.
Does it makes sense to move to Qt Quick as we donot have GPU on the
embedded hardware?
On Mon, 15 Jul, 2019, 01:43 André Pönitz, wrote:
> On Sun, Jul 14, 2019 at 10:19:25PM +0530, Ramakanth Kesireddy wrote:
> > Hi,
> >
> > Our Qt app is based out of Qt 5.6 C++ widgets. Inor
11 matches
Mail list logo
