Mobile and Embedded

@mrdebug At the moment, i use QtMultimedia, which works fine on android too. However, i have some features on my wish list, like mixing and fading between tracks, multiple output devices, etc. Gstreamer has a comprehensive documentation and it seems to be more suitable than ffmpeg, because of its modularity. But thank you very much for the link. Wow, your project looks pretty clean and well arranged.

It's not exactly that been seeking. But your example is useful for some cases. Seeking solution to set Window to the safe area without using Rectangle and margins. Trying to find solution for old-fashion applications.

Haven't found any working example. After 5 days of experiments on Qt 6.11.1 got written example It's on purpose written not optimized and very detailed within logging functions details. Don't know of working it on other versions of Qt. It's using SafeArea means on Qt 6.9 maybe will be working too.

Reported: QTBUG-147229 A sort of workaround is to take away autoDefault for all pushbuttons on the form. Then the ready button on the ios keyboard works like show/hide since there are no default button for the form. Though the keyboard still shows up when the QTableWidget gets active.

Solution found. Since Qt 6.9 might be used SafeArea with Window QML component. Code samples published here. No need to use native code implementation for handling safe area on iOS or Android devices.

Finally I solved the problem with the bars. Although I called the Java method to hide the bars they seemed to ignore the command. The problem was that I must call the hide() method after the application signaled that it is active. Every time the application becomes active the hide() method must be called. Additionally in the Android resource tree the file themes.xml must not contain any control statements for the system bars. My new themes.xml looks like this now: <resources> <!-- base set of styles that apply to all versions --> <style name="TPanelAppTheme" parent="@android:style/Theme.DeviceDefault"> </style> <!-- declare the theme name that's actually applied in the manifest file --> <style name="TPanelAppTheme.NoActionBar"> </style> <style name="Tpanel_settings" parent="Theme.AppCompat"> </style> </resources> Everything else is controlled by code. Hope this helps someone. A.T.

@mskyyyf-wiieyy I'm not clear on what the MouseArea accomplishes in that solution, but I think you're telling me that any interactive control like a slider or a live-search text field should be parented to Overlay.overlay and thus be immune to all the effects of the layout passes that result from those interactions. Correct?

@Narasimha said in QPushButton->setMenu(QMenu) transparent removal not working: Important: Explain internal Qt painting behavior. To add to @Axel-Spoerl : I mean regarding this point, you could look it up yourself, if you care... Qt has a very nice and detailed documentation. Basically you demand a final and ready-to-use solution while refusing to do little work yourself. And you also did not mention if it worked with Qt 4.8 before. Edit: Also, your code compared to your expected output does not make any sense... You apply a background-color #333 to both of your widgets A and B while your expected result shows a light gray background color for the left widget (assuming widget A). That makes me doubt that you've really taken the time to seriously look into the code or the problem.

@jfurtak good to hear that my app was helpful. ...yep, life isn't easier now with edge-to-edge windows ;-) BTW: did a short test on iOS, where you always (in Landscape and Portrait) have a navigation line at bottom. There it's also not possible, to swipe from bottom to open the Drawer. if it's important for you to open Drawer from bottom by swiping you should create an Issue at Qt Bugreports with all your screenshots and code. Feel free to mention me there. Would be better to continue discussing there.

That message "Android support is not yet configured" comes from https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/android/androiddevice.cpp?h=20.0#n1296 - that would suggest like @JKSH suggested that the Qt for Android is not yet installed. Whether it should not be even possible to Add -> Android Device when Qt for Android is not yet installed is another way to look at this. @TP850 Please install Qt for Android first from Qt Installer or Maintenancetool

Hello @ap.sirius, I'm not able confirm how this works in Qt 5 or what would be the proper workaround if the fixes in QTBUG-97503 or related fixed tickets indeed do not work for you, but this is fixed in Qt 6 and I'm not seeing this kind of behavior there. I would suggest migrating to Qt 6 (6.8 LTS or newer) if possible.

I would suggest trying tools recommended by Android: https://developer.android.com/ndk/guides/memory-debug HWASan works, but it also has some limitations ( Only for 64 bit apps, for example)

had similar problems, but only with some versions of GBoard this is workaround for Landscape keyboard: do not anker the keyboard [image: 4c87dcdb-5de5-457f-be37-3e5288800222.png] [image: d762d5f3-a841-4ac0-867d-b394cfd72fd5.png]

I'm not using 6.8.x, but with Qt 6.10.1+ Safe Areas are working for me see also my Test App https://github.com/ekke/ekkesTestStatusBar

for me it's working on Android and iOS with Qt 6.10.1+ see also my test app: https://github.com/ekke/ekkesTestStatusBar