[Interest] Qt interfacing to Android native UI ?

[Edward Sutton]

Hi Sze-Howe,

On Nov 4, 2015, at 5:11 PM, Sze Howe Koh <szehowe.koh at gmail.com<mailto:szehowe.koh at gmail.com>> wrote:

On 4 November 2015 at 22:51, Edward Sutton <edward.sutton at subsite.com<mailto:edward.sutton at subsite.com>> wrote:

I am having layout or other issues that make the mixed widget / qml not
display well or at all on Android and iOS when Combining Qt Widgets and QML
with QWidget::createWindowContainer() .  Hopefully that is something that is
solvable else the mixed QML and C++ widget approach may be a dead-end.

There are known issues with QWidget::createWindowContainer().
QQuickWidget was introduced as a better alternative.

Thank you *very* much for pointing this out.  There seem to be many issues with QML not -repainting, sizing, and positioning issues that seem inconsistent across OS X, iOS, and Android.  At this point I do not know if the problem is QWidget::createWindowContainer or my lack of QML expertise and understanding about layout and positioning of QML components.

I am hopeful that switching to use of QQuickWidget may make the behavior more consistent.

Thanks again,

-Ed




I will continue reading Interacting with QML Objects from C++  with the goal
of connecting a Tumbler added to Combining Qt Widgets and QML with
QWidget::createWindowContainer()  to be readable and writable from C++.

Thanks again Federico.

-Ed


Regards,
Sze-Howe

This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20151105/d9b91d27/attachment.html>