with a little help from Jake Petroules:
here's HowTo avoid all these warnings.
Add into .pro
iOS {
...
disable_warning.name = GCC_WARN_64_TO_32_BIT_CONVERSION
disable_warning.value = No
QMAKE_MAC_XCODE_SETTINGS += disable_warning
ekke
Am 20.06.17 um 11:52 schrieb ekke:
> if I
Why this option needs modifications to iOS platform plugin? What kind of
modifications? Can you give me a brief insight?
I need this so much that I’m considering all options before having to
reimplement all the needed graphics in another technology.
Thanks!
Regards,
Nuno
> On 20 Jun 2017,
> On Jun 20, 2017, at 8:41 AM, Nuno Santos wrote:
>
> Jake,
>
> Thanks for your insights.
>
> Do you think it is possible to open a qml view inside a App Extension?
It should be, but not without modifications to the iOS platform plugin.
>
> My options:
>
> 1)
Jake,
Thanks for your insights.
Do you think it is possible to open a qml view inside a App Extension?
My options:
1) Try to do it via Qt side. Based on what you have just told me seems to be
impossible.
2) Grab a Xcode project that already works an link with the necessary Qt
frameworks so
Application extensions are simply normal Mach-O executables with
_NSExtensionMain as their entry point instead of main. They are executed and
quit by the system when needed, and the timing of these events cannot be
controlled manually.
qmake does not support building app extensions (although
2017-06-20 13:52 GMT+02:00 Ola Røer Thorsen :
> function doStuff() {
>var o = theGadget;
>console.log("o.name"); // prints "Name"
>o.name = "Some other name"; // No error, but nothing really happens
> either
>console.log("o.name"); // Still prints "Name"
Hi,
I finally had some time to research on this.
I was able to create a test app with Qt Creator and manually place another app
(extension) inside the generated .app bundle PlugIns folder. The app extension
is an audio unit plugin for AUV3 hosts such as Modstep. I have then used
Modstep to
Hi all,
I have a Q_GADGET-based class with properties that I instantiate in C++ and
expose to qml via QVariant in a list model. The class is registered to Qt
and Qml using Q_DECLARE_METATYPE,
qRegisterMetaType and qmlRegisterUncreatableType.
The properties are defined like this:
class MyGadget
On 19 June 2017 at 22:18, Kai Koehne wrote:
>
> Hi,
>
> This sounds like a bug, please feel free to create a bug report.
>
> Anyhow, as a workaround you can launch the maintenance tool with the
> --show-virtual-components argument. This will show you also packages that are
>