Re: [Interest] Can't deploy anymore on QtCretor 4.5

You need to edit the Android manifest file, not the pro.user file. Creator has a special editor dialog for it. On 09/12/17 02:05, Xavier Bigand wrote: Hello, It seems to be a nice version, but I still have some trouble when targeting Android, with the version 4.4 I had to edit the .pro.user

[Interest] Can't deploy anymore on QtCretor 4.5

Hello, It seems to be a nice version, but I still have some trouble when targeting Android, with the version 4.4 I had to edit the .pro.user to make the deployment working by forcing the BuildTargetSdk at android-26. But now it seems that something different goes wrong, here is my output: 00:39:0

Re: [Interest] ASSERT: "m_engines.contains(engine)" in file qqmlenginedebugservice.cpp, line 802 qqmlenginedebugservice.cpp: 802

I did that for background processing or some sort, but I have hit a limitation myself: qmldir singleton are create only once and won't be usable on other QQmlEngine, C++ singleton you can control and create an instance per QQmlEngine/thread with the callback, but no luck for those qml singleton on

Re: [Interest] ASSERT: "m_engines.contains(engine)" in file qqmlenginedebugservice.cpp, line 802 qqmlenginedebugservice.cpp: 802

Just in case if anyone care, creation QQmlEngine in UI thread and then moving to background thread resolved the issue. Moreover QML debugger works with both threads! 2017-12-08 14:43 GMT+03:00 Alexander Ivash : > Well, as I said it seems to be working, at least in very simple > scenarios, like rea

Re: [Interest] QtIFW and LGPL3

On Friday, 8 December 2017 04:33:45 PST Oliver Niebuhr wrote: > Questions are: > 1.) Do I have to put the IFW Installer Scripts, *.ui Files etc. under > the LGPL3 License and make it public? > 2.) Do I have to publish the (from my end unchanged) QtIFW Source Code too? The LGPLv2.1 or v3 require yo

[Interest] QtIFW and LGPL3

Hello List. I know I can not get legal advice here of course. But I would love to hear what you think about it :) Case: 1.) Personal Tool built with Qt5 (5.10 ATM) Open Source LGPL3 2.) No Changes in the Qt Source Code by me 3.) Qt Installer Framework built with statically built Qt 5.10 with Open

Re: [Interest] ASSERT: "m_engines.contains(engine)" in file qqmlenginedebugservice.cpp, line 802 qqmlenginedebugservice.cpp: 802

Well, as I said it seems to be working, at least in very simple scenarios, like reading file & doing JSON.parse from separate thread. So, if this is artificial limitation of QML Debugger, then would be great to get it fixed. Can I at least silence that assert by somehow excluding QQmlEngine in thre

Re: [Interest] ASSERT: "m_engines.contains(engine)" in file qqmlenginedebugservice.cpp, line 802 qqmlenginedebugservice.cpp: 802

What needs to be done to get rid of this assertion (is it possible at all or QmlDebugger is always expect single QQmlEngine? ) You can have multiple QML engines attached to the debugger, but the current assumption is indeed that they all live in the GUI thread. This can probably be fixed, but

[Interest] ASSERT: "m_engines.contains(engine)" in file qqmlenginedebugservice.cpp, line 802 qqmlenginedebugservice.cpp: 802

I'm playing with https://github.com/qyvlik/QmlThread project which allows to create QQmlEngine per thread to execute QML/Js in background and it mostly seems to be working just fine. But on attempt to debug QML I'm getting assertion. I might be completely wrong, but from the first look it seems li

[Interest] How to downgrade QtC from maintenance tool

Hi all, Is it possible to downgrade the previously updated QtC, using MaintenanceTool utility? BR, Denis ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest