Mobile and Embedded

@Davronito you're welcome! Don't forget to use the topic tools to set the topic to solved 😉

@J-Hilk Thank you. This solution worked.

I'm able to mostly work around this issue by explicitly calling setSpacing(0); on my layout objects. Seems they inherit a property that is inconsistent between arm and x86 versions of the library. This still is not fixing this case: QFontMetrics metrix(label->font()); uint16_t width = metrix.boundingRect(label->text()).width(); if (width > maxWidth) QString clippedText = metrix.elidedText(text, Qt::ElideRight, maxWidth); where the clippedText returned is incorrect (much shorter than needed) on the arm arch version. But I can work around this one more issue for now.

@Mohit-Tripathi that is correct, Like @jsulm said, QByteArray only accepts char as it lowest form. You have to assign the 1st index the high byte and the 2nd index (of the byte array) the Low byte (or flipped, depending on endianness ) That said, your previous int to hex string conversion is unneeded and probably wrong too.

@SherifOmran You need to request access to media files, see https://doc.qt.io/qt-5/qtmultimedia-ios.html Use https://doc.qt.io/qt-5/qstandardpaths.html to get the directory containing the media files.

Not directly but you have this stack overflow answer that covers the iOS API in Objective-C and for Android, there's an example in the QtAndroidExtras module.

@hetalik Good to read that your problem has been solved. Please mark post as solved then. [edit:koahnig] Not sure if there is an issue with the forum. Possibly it is already marked as solved, but it is clearly shownb as unsolved for me. However, the entry under "Topic Tools" would allow only "Mark as Unsolved".

Ah, I see what you are doing here. When does the user select the device: before or after the discovery? If it's before discovery, no need to do a discovery at all. Connect immediately. If during the discovery, no need to wait for finished() at all, connect as soon as user selects it (stop the discovery first) .

SOMETIMES, this will not be a configuration issue as mentioned in other answers. In my case, the problem was one file that happened to have been saved with a .CPP extension rather than .cpp. QMake (Qt5) was misidentifying the file and trying to compile it with the C compiler rather than the C++ compiler. The QMake from Qt4 was not exhibiting this issue. Renaming the file fixed the issue. My comment at the time was "Could this really be that f&%%& simple!!"

the problem solved my phone display size setting was on smallest mode the emoji quality is fine only on normal display size (It should not be smaller or bigger) [image: 03a22be2-4996-455c-add8-4641780e4b4f.png] This means that anyone using my app must always have a standard display size and I have to force them to do that. But in AndroidStudio isn't like this

Hi I dont know the answer but i was wondering if QWidgets or QML ?

Some good news, I fixed the fonts by manually creating the font folder and transferring the fonts to the RPI. In regards to the touchscreen, I ended up observing that the touchscreen worked on the application for the most part. When I use the touchscreen on the app, the touch event occurs in a different location on the interface from where I touched. I want to think that it is a calibration issue but when I exit the application, touchscreen events work as intended. Could it be an issue with EGLFS? I am still wondering if I need EGLFS to run or if there is a second option that I can explore. Anyways, I am running v4.19.83-v7+

I'd install all of the GStreamer plugin packages.

@Surendar-Dharani as mentioned by @maxwell31 regarding libraries, you may want to take a look at step #15 from this guide (I know it's related to cross-compilation, but that step may apply to your issue).

try to add this to main.py import os os.environ["QT_IM_MODULE"] = "qtvirtualkeyboard"

@Mohit-Tripathi said in Why only condition is working for "if" condition?: Can I know why? This is simple Boolean algebra: False && False ==> False False && True ==> False True && False ==> False True && True ==> True False || False ==> False False || True ==> True True || False ==> True True || True ==> True