QML and Qt Quick

@xargs1 thanks for your response. is it also possible to access the image data before the saving process?

Solved Here is the code to get the full image path from android gallery using java equivalent code written with Qt: #include "imagepickerandroid.h" imagePickerAndroid::imagePickerAndroid() { } void imagePickerAndroid::buscaImagem() { QAndroidJniObject ACTION_PICK = QAndroidJniObject::getStaticObjectField("android/content/Intent", "ACTION_PICK", "Ljava/lang/String;"); QAndroidJniObject EXTERNAL_CONTENT_URI = QAndroidJniObject::getStaticObjectField("android/provider/MediaStore$Images$Media", "EXTERNAL_CONTENT_URI", "Landroid/net/Uri;"); QAndroidJniObject intent=QAndroidJniObject("android/content/Intent", "(Ljava/lang/String;Landroid/net/Uri;)V", ACTION_PICK.object<jstring>(), EXTERNAL_CONTENT_URI.object<jobject>()); if (ACTION_PICK.isValid() && intent.isValid()) { intent.callObjectMethod("setType", "(Ljava/lang/String;)Landroid/content/Intent;", QAndroidJniObject::fromString("image/*").object<jstring>()); QtAndroid::startActivity(intent.object<jobject>(), 101, this); qDebug() << "OK"; } else { qDebug() << "ERRO"; } } void imagePickerAndroid::handleActivityResult(int receiverRequestCode, int resultCode, const QAndroidJniObject &data) { jint RESULT_OK = QAndroidJniObject::getStaticField<jint>("android/app/Activity", "RESULT_OK"); if (receiverRequestCode == 101 && resultCode == RESULT_OK) { QAndroidJniObject uri = data.callObjectMethod("getData", "()Landroid/net/Uri;"); QAndroidJniObject dadosAndroid = QAndroidJniObject::getStaticObjectField("android/provider/MediaStore$MediaColumns", "DATA", "Ljava/lang/String;"); QAndroidJniEnvironment env; jobjectArray projecao = (jobjectArray)env->NewObjectArray(1, env->FindClass("java/lang/String"), NULL); jobject projacaoDadosAndroid = env->NewStringUTF(dadosAndroid.toString().toStdString().c_str()); env->SetObjectArrayElement(projecao, 0, projacaoDadosAndroid); QAndroidJniObject contentResolver = QtAndroid::androidActivity().callObjectMethod("getContentResolver", "()Landroid/content/ContentResolver;"); QAndroidJniObject cursor = contentResolver.callObjectMethod("query", "(Landroid/net/Uri;[Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;Ljava/lang/String;)Landroid/database/Cursor;", uri.object<jobject>(), projecao, NULL, NULL, NULL); jint columnIndex = cursor.callMethod<jint>("getColumnIndex", "(Ljava/lang/String;)I", dadosAndroid.object<jstring>()); cursor.callMethod<jboolean>("moveToFirst", "()Z"); QAndroidJniObject resultado = cursor.callObjectMethod("getString", "(I)Ljava/lang/String;", columnIndex); QString imagemCaminho = "file://" + resultado.toString(); emit imagemCaminhoSignal(imagemCaminho); } else { qDebug() << "Caminho errado"; } }

Thanks for the responses - really good info. Think I'll investigate the QML worker thread option.

One of the tricks I use is to set all dimensions in milimeters instead of pixels, something like this: property real mm: Screen.pixelDensity property real btnSize: 8 * mm Rectangle { width: btnSize height: btnSize } This, in a perfect world, would give you a rectangle with the same size in devices with different pixel density. But please note that Screen.pixelDensity is the QML version of the c++ QScreen.physicalDotsPerInch, wich according the docs: "This value represents the pixel density on the screen's display. Depending on what information the underlying system provides the value might not be entirely accurate". My experience shows that in laptops and screen monitors que values are very good, you can measure the screen with a ruler and check that the rectangle is 8mm, however I have had bad experiences in mobile android devices, probably because of poor screen/drivers quality. So I usually in my applications I do something like: property real calibrationFactor: 1.0 property real mm: Screen.pixelDensity * calibrationFactor where calibrationFactor is a value that the user can change in some Settins menu to "calibrate" the overall size of the buttons/elements of the app. Also there's more than this to do a one size fits all screens app. Usually there's a all lot of tricks like trying to find the screen dimension and loading different UI's at run time, or using flickable elements and listview elements that can scale up more or less ok with different screen sizes. ALso check this very interesting video https://www.youtube.com/watch?v=nNyhsdX6BsI&list=PLizsthdRd0YwgXOHoXxBrIEgBdzACclcg&index=3

i concluded that we should define a property like fg in NumberAnimation and we have property int fg:menuspiral.width/3 in type Window now it works. NumberAnimation on x { property int fg duration:2000 loops: Animation.Infinite running:true from: 0; to:fg }

Okay, so nobody knows what are the drag and minimumXY properties are for in the PinchArea... but does somebody know where to get more information on how to use them?! Thanks nx7z

@SGaist OS X 10.10 and Win 10

Sorry for misunderstanding. Can you try this one as a MyField? TextInput { id: myField width: (maximumLength + 1) * fm.averageCharacterWidth height: fm.height + 4 maximumLength: 10 selectByMouse: true clip: true FontMetrics { id: fm font: myField.font } } In this case setting font.pixelSize should work perfectly fine. MyField { font.pixelSize: 14 } Sorry for misleading you in a first place.

Hi, Why not use QFileSystemModel ? It's designed to browse a file system and is threaded to avoid blocking the GUI thread.

Hi, It's the QtWebView module that offers a wrapper around OS X, iOS and Android web views.

Hi, There's a conversion done when you set the color property thus currently what you are doing is comparing a color with a string. The solution is: background.color = Qt.colorEqual(background.color, "steelblue") ? "purple" : "steel blue"

It is solved with Qt 5.5. I do not found this issue in Qt 5.5