I’ve been using Qt for mobile and desktop development for a while now and even though I am satisfied with the results, the platform specific features, as you say, have not been great. But consider yourself lucky because Qt is more robust on iOS than Android. Especially with the new dynamic navigation bars that some phones have the UI sometimes freezes when the window size changes because the navigation bar is showing. Getting the platform specific features up and running on iOS is easier compared to Android because of its JNI requirement. With iOS you can simply call the Objective-C++ code.
I’ve never used it but V-Play (https://v-play.net/) has some a lot of platform specific features to make your life easier. They have a different licensing model so I’ve never used them, and I’ve been creating my own UI toolkit, and library for the platform specific features (https://github.com/Furkanzmc/qutils/tree/develop). It is under active development so a lot is changing. I haven’t written proper guides but you can find explanations in the code comments. You might find something useful there when you run into a problem. (e.g the status bar issue, or colour changing, push notifications.) Regards, Furkan Üzümcü On Aug 13, 2018, 09:55 -0400, Jason H <jh...@gmx.com>, wrote: > This past week I worked with some devs who had a Xamarin (C#) app for iOS. Qt > was woefully behind. I had to muck about with Objective-C, (with Apple's site > now defaulting to Swift code examples). > > Simple things like setting screen brightness and status bar visibility were > as simple as setting a property on a C# object. When will Qt have this level > of platform integration? It took me about 4 hours to get a delegate working > (I'm not a Obj-C coder) with what should have been (and is in C#) two lines > of code. This is not coding less and creating more. > > Qt could easily be ahead with a platform-agnostic platform object so that the > same code would work on android (something not true of Xamarin as it ties the > property name to the Obj-C name and therefore is not portable) > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
