@VRonin yes - it's a list of QObject*
each entry describes a File:
Type (Image, Video, PDF, ...)
Name (obsolet for iOS Photos)
entries (if Folder)
and I'm constructing the collection per ex. from
PHFetchResult *smartAlbums = [PHAssetCollection fetchAssetCollectionsWithType:PHAssetCollectionTypeSmartAlbum subtype:PHAssetCollectionSubtypeAlbumRegular options:nil];
Apple is very conservative in allowing developers long term background threats/events.
Taken from the Apple docu:
Implementing Long-Running Background Tasks
For tasks that require more execution time to implement, you must request specific permissions to run them in the background without their being suspended. In iOS, only specific app types are allowed to run in the background:
Apps that play audible content to the user while in the background, such as a music player app
Apps that keep users informed of their location at all times, such as a navigation app Apps that support Voice over Internet Protocol (VoIP) Newsstand apps that need to download and process new content
Apps that receive regular update from external accessories
Apps that implement these services must declare the services they support and use system frameworks to implement the relevant aspects of those services. Declaring the services lets the system know which services you use, but in some cases it is the system frameworks that actually prevent your application from being suspended.
That said, a navigation app should fall in this category. But as it is, you're bound to do it in OBjective-C but its relative easy to include ObjectiveC code in Qt.
If you set the Qt::MaximizeUsingFullscreenGeometryHint window flag, the window will also cover the area under the statusbar, etc. But we don't have any APIs to automatically add margins for the inner content, the stuff you don't want under the statusbar, so for now you have to do that manually. I'm working on the latter as we speak.
I had no idea, that that window flag existed, or was not aktivated by default - on mobile apps.
I can work with that. The ticket is still open but my problems are solved. I'll close this topic.
@ekkescorner@jpnurmi reminds me that there's a problem if you're using multi-line Text inside Flickable.
He's right: as long as the TextArea has focus if you try to scroll the selection will be changed instead of scrolling the page.
If you're outside the field scrolling works well
I'll create a bugreport on this soon.
my workaround: I'm placing a small button (w icon) besides the field to toggle word-selection-mode. just tested. this works.
In most cases my TextFields are single line text where selection works well so I can live with this.
Plugin Pro file like flow:
TEMPLATE = lib
TARGET = iostestqmlplugin
QT += qml quick
CONFIG += qt plugin c++11 static
uri = IosQmlPluginTest # module name
QMAKE_MOC_OPTIONS += -Muri=$$uri # static plugin must use this
typeinfo plugins.qmltypes #static plugin required
classname IosqmlpluginPlugin # static plugin must set classname for plugin c++ class
TimeLabel 1.0 qrc:/TimeLabel.qml # your self qml document
3.qrc file must contains qmldir file, Qt default put qmldir in qrc file with prefix likes: “/qt-project.org/imports/your-plugin-modele-name”, You can special yourself prefix but must endwiths “your-plugin-module-name” and in main cpp need add addImportPath(eg: engine.addImportPath(“qrc:/your-self-prefix-not-contains-your-plugin-module-name”))
4.put plugins.qmltypes, qmldir and plugin library files together into where Qt install dir’s sub fold name qml($$[QT_INSTALL_QML] Qt default serach path), maybe you can special yourself path in your app pro file by variable QMLPATHS(QMLPATHS += /your/plugin/path)
Init the plugin resources(contains qmldir) at plugin c++ class construction function like:Q_INIT_RESOURCE(your-qrc-file-name);
6.pulugins.qmltypes file it’s required. can gernerate by qmlplugindup tool.
7.refrence QtWebView plugin project from Qt source
1.static plugin for module “QtQuick” with name “your-module-name” has no metadata URI
fix by add in pro file:QMAKE_MOC_OPTIONS += -Muri=$$URI #URI = your-module-name
we didn't use the Firebase C++ SDK as it is still limited compared to what the native iOS & Android SDKs offer.
You can use our AdMob plugin for iOS & Android for free, here's the documentation how to add it to your Qt project and how to use it: https://v-play.net/doc/plugin-admob/