@jeremy_k said in onPressAndHold not working with Qt.TapAndHoldGesture:

TextArea takes focus when it receives a press, rather than a click.

That's a good idea. I've tried playing around with focus, however it seems no matter how I set it, that doesn't change objects funcionality.

For the future generations of humanity:

QJniObject toast = QJniObject::callStaticObjectMethod( "android/widget/Toast", "makeText", "(Landroid/content/Context;Ljava/lang/CharSequence;I)" "Landroid/widget/Toast;", QNativeInterface::QAndroidApplication::context(), displayText.object<jstring>(), timeout ); if (toast.isValid()) { qDebug() << "Toast is valid"; toast.callMethod<void>("show"); } else { qDebug() << "Toast JNI object not valid"; }

Ok, how about this - Anybody know a way I can add code or set env to enable rotation, (portrait/landscape, or...). As it is, the qt apps don't respond to phone sensors, but are fixes...

I have found a solution! I did multiple things:

Used newer template files for Android from Qt/6.2.3/android_arm64_v8a/src/android/templates/ (res/values/libs.xml - overwritten, build.gradle - overwritten, AndroidManifest.xml - copy and paste and then edited the content and added the missing things from my old one) Used newer gradle files from /Qt/6.2.3/android_arm64_v8a/src/3rdparty/gradle/gradle/wrapper/ - overwritten Upgrade of Qt Creator, Qt 6.2.2 -> 6.2.3, Android SDK, Android NDK

My current Manifest:

<?xml version="1.0"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="org.dontpanic" android:installLocation="auto" android:versionCode="20000" android:versionName="2.0"> <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="31"/> <!-- The comment below will be replaced with dependencies permissions upon deployment. Remove the comment if you do not require these default permissions. --> <!-- %%INSERT_PERMISSIONS --> <!-- The comment below will be replaced with dependencies permissions upon deployment. Remove the comment if you do not require these default features. --> <!-- %%INSERT_FEATURES --> <supports-screens android:anyDensity="true" android:largeScreens="true" android:normalScreens="true" android:smallScreens="true" /> <application android:name="org.qtproject.qt.android.bindings.QtApplication" android:extractNativeLibs="true" android:hardwareAccelerated="true" android:label="@string/app_name" android:icon="@drawable/icon" android:requestLegacyExternalStorage="true"> <activity android:name="org.qtproject.qt.android.bindings.QtActivity" android:configChanges="orientation|uiMode|screenLayout|screenSize|smallestScreenSize|layoutDirection|locale|fontScale|keyboard|keyboardHidden|navigation|mcc|mnc|density" android:label="@string/app_name" android:launchMode="singleTop" android:screenOrientation="portrait"> <intent-filter> <action android:name="android.intent.action.MAIN"/> <category android:name="android.intent.category.LAUNCHER"/> </intent-filter> <!-- Application arguments --> <meta-data android:name="android.app.arguments" android:value="-- %%INSERT_APP_ARGUMENTS%% --" /> <!-- Application arguments --> <meta-data android:name="android.app.lib_name" android:value="-- %%INSERT_APP_LIB_NAME%% --" /> <!-- Background running --> <!-- Warning: changing this value to true may cause unexpected crashes if the application still try to draw after "applicationStateChanged(Qt::ApplicationSuspended)" signal is sent! --> <meta-data android:name="android.app.background_running" android:value="false" /> <!-- Background running --> <!-- extract android style --> <!-- available android:values : * default - In most cases this will be the same as "full", but it can also be * something else if needed, e.g., for compatibility reasons * full - useful QWidget & Quick Controls 1 apps * minimal - useful for Quick Controls 2 apps, it is much faster than "full" * none - useful for apps that don't use any of the above Qt modules --> <meta-data android:name="android.app.extract_android_style" android:value="minimal" /> <!-- extract android style --> </activity> <service android:name="org.dontpanic.NotificationService"> <meta-data android:name="android.app.lib_name" android:value="-- %%INSERT_APP_LIB_NAME%% --"/> </service> <receiver android:name="org.dontpanic.NotificationReceiver" android:enabled="true" android:exported="true"/> <receiver android:name="org.dontpanic.RebootReceiver" android:enabled="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.BOOT"/> <action android:name="android.intent.action.LOCKED_BOOT_COMPLETED"/> <action android:name="android.intent.action.BOOT_COMPLETED"/> <action android:name="android.intent.action.QUICKBOOT_POWERON"/> <action android:name="android.intent.action.REBOOT"/> <action android:name="com.htc.intent.action.QUICKBOOT_POWERON"/> <action android:name="android.intent.action.USER_PRESENT"/> <category android:name="android.intent.category.DEFAULT"/> </intent-filter> </receiver> </application> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/> </manifest>

@ekkescorner Assam Boudjelthia has done a great work on this and now prepared cherry-picks for 5.15 🙂
see QTBUG-98974
can someone help and test ?

@Phips04 Your welcome

@Soviet-Ball you don't need this anmore in Qt 6.6:
FileDialog on Android supports content URLs.

QFileInfo().fileName()

gives you the file path
so easy now :)

@SGaist Hey so the reference problem is solved. Seems like the file can be opened, the player works but there is no sound :-/. I'll probably open another thread for this issue. Thanks for the help again!
EDIT: Or maybe it's working :D. On other devices I got a report that the sound is OK. Will investigate that further!

@shokarta try with Android FileDialog

FileDialog { title: qsTr("Select a File") fileMode: FileDialog.OpenFile onAccepted: { if(selectedFiles.length) { console.log("we selected: ", selectedFiles[0])

Selected File 'München.pdf' from FileDialog
...this gives you per ex:

content://com.android.providers.downloads.documents/document/32

// you can check from C++ and verify fileUrl:

QFileInfo fileInfo(fileUrl); qDebug() << "verifying fileUrl: " << fileUrl; qDebug() << "BASE: " << fileInfo.baseName(); qDebug() << "FileName: " << fileInfo.fileName(); qDebug() << "Path: " << fileInfo.path(); qDebug() << "absoluteFilePath: " << fileInfo.absoluteFilePath(); return fileInfo.exists();

this gives you:

verifying fileUrl: "content://com.android.providers.downloads.documents/document/32" BASE: "München" FileName: "München.pdf" Path: "content://com.android.providers.downloads.documents/document" absoluteFilePath: "content://com.android.providers.downloads.documents/document/32" file exists

@Mehmet-Yilmaz said in UI/UX Mockup tool:

Can I use Qt design as a UI/UX tool or I need to buy an external tool

Well, nobody beside yourself can answer THAT question.

Regards

Hi,

Since you are using V-Play, you might want to bring that question to their forum.

AFAIK, no. But you can check that yourself.

@ekkescorner Hi,
Well, when we develop a mobile app with Qt for Android and iOS (we'll use Start-Up Plan), if we sell the app a customer, Can this customer publish the app on Google Play and AppStore?

Hi,

At V-Play, we have an example on how to achieve this in our Twitter sample app. Check out the screenshots: (Sorry, didn't have time to record an animation ;) )

0_1499349566897_vplay-collapse1.png

1_1499349566898_vplay-collapse2.png

2_1499349566898_vplay-collapse3.png

This sample needs the V-Play SDK to run, which might be useful if you are into app development.
If you don't want to install a third-party SDK, you still might be able to get some inspiration from the sample app.

Cheers,
Lorenz

@piJar
stupid question (just to make sure): you did connect with the debugger right?

@lukas_kosinski would also be great to have more codes - esp Code39 and EAN-Barcodes are essential for my apps