07.09.2016 17:10, Wolfgang Baron пишет:
Am 07.09.2016 um 09:30 schrieb Alexandru Croitor:
If my memory serves, it used to work about a year ago with Qt 5.5 +
Quick Controls 1, because I tested a QML app on an Android emulator.
Don't know what changed now.
Thanks for the insight. Could anybod
On Wed, Sep 07, 2016 at 04:10:18PM +0200, Wolfgang Baron wrote:
>
> Am 07.09.2016 um 09:30 schrieb Alexandru Croitor:
> >If my memory serves, it used to work about a year ago with Qt 5.5 + Quick
> >Controls 1, because I tested a QML app on an Android emulator. Don't know
> >what changed now.
>
>
Am 07.09.2016 um 09:30 schrieb Alexandru Croitor:
If my memory serves, it used to work about a year ago with Qt 5.5 +
Quick Controls 1, because I tested a QML app on an Android emulator.
Don't know what changed now.
Thanks for the insight. Could anybody shed some light on the priority of
bei
If my memory serves, it used to work about a year ago with Qt 5.5 + Quick
Controls 1, because I tested a QML app on an Android emulator. Don't know what
changed now.
On 31 Aug 2016, at 18:43, Wolfgang Baron
mailto:wolfgang.ba...@gmx.net>> wrote:
Your comment about the shader errors made me th
Your comment about the shader errors made me think. I grabbed a physical
android device and voila, it worked. Apparently, the AVDs provided by
the AVD manager are just not good enough for running QtQuick (yes, even
QuickControls1 etc. don't work, just a white or a black screen). Maybe I
clicked
I dunno about the shader errors, but what if you add
qputenv(“QML_IMPORT_TRACE”, “1”) at the beginning of main.cpp?
It looks like the material style etc. plugins are deployed, the QML engine just
can’t find them when it tries to import them.
From: Interest [mailto:interest-bounces+mitch.curtis=
