Then I would check the cmake bug tracker to see if there's something related there.

I‘m not moving away from QWidgets. This makes this interesting. However, is there a reason Linux is not supported? Or might it just run on Linux as well?

I edited socketcanbackend.cpp to include the missing include file (<linux/sockios.h>) and compiling is proceding...

Hi, Did you set the QT_DEBUG_PLUGINS environment variable to 1 before starting your application ? It might give you additional clues.

@soccercj jsulm is right. android_arm_v64a is installed. But QtCreator does not pick it up. You need to add it manually by clicking add button.

Right ! Sorry, I had your host and target build mixed. For other readers, there's also this important note about the minimal host build suggested there: This build won't be suitable for developing Qt programs for your host platform, but it will contain the tools necessary to cross-build Qt.

I remember there was a post not long ago with similar symptoms. Can you try a more recent version of Qt Crestor ?

Hi Guys, thanks for replying - I need to enable my email notifications... Also sorry for not being able to provide example code. I am explicitly instancing the InputPanel myself - and not so long ago learned that really only one instance is needed. Still it is a matter of where placing the instance inside the QML hierarchy as Overlays are special, because they are not part of the hierarchical structure. parent: Overlay.overlay did not work in the first place. I am not exactly sure what finally did the trick but it might have been placing the InputPanel as a direct child to the Window (and thus making it a sibling - not a child - to contentItem). Works now. Thanks so much Felix

I don't know about this, but I'd give the app manually permission for all files, and see what happens. I remember there being various issues with QUrl, but don't remember details. And, of course, something not working in Android, and even the supposedly evolved and mature Qt 6x in Android, is no surprise...

If you have 3GB of memory (or more) in your MacBook you could try upgrading to Sonoma via the OpenCore Legacy Patcher

Ok, I rerun the installer again and finally found the option und "Qt". Thanks a lot!

My case is to develop simplified TextArea within ability just to write, read, copy and paste text without extensive functionality. You can do that in QML with C++ helpers if needed, but as said before the c++ code for TextArea is not public API.

@Christian-Ehrlicher said in Qt 6.8/6.11: tabified QDockWidget freezes dock-area width after undock — regression from 5.15?: Please wait for Qt 6.11.2 or a new 6.8 version. Take a look into bugreports.qt.io - don't have the exact bug number at hand. Thank you for the quick responce! I've found the ticket: https://qt-project.atlassian.net/browse/QTBUG-147209

Go to Tools > Debug Qt Creator > Inspect C++ Code Model ... there you should get access to some information that the code model uses. Otherwise you would have to enable some logging to get more info.

@Qt6User Is this because you want to install into an old hardware that supports Win32?

Your code above is correct so you either mix debug and release libraries (e.g. you compile your app in release mode but using debug Qt libs) or you don't show your full code.

@Bubu-Droid Why do you first create https://forum.qt.io/post/839002, to which I have replied, and then this new topic? It is precisely because people answer in one place that we don't want you to raise duplicates. I posted there: Obviously to start with: QPdfDocument::Error QPdfDocument::error() const (and statusChanged(QPdfDocument::Status status)). This is vital and first thing you should check. Verify ProjectSettings::instance().pdfPath exists. Have you tried multiple/absolute minimal PDF documents? Get rid of any concurrency/moveToThread. Is it safe/sensible to call loadDoc->moveToThread() while loadDoc->load() is running? Even if it is allowed, why/what is the effect of setting off a load before moving to a thread? Please pick one or other topic and stick to it.

@Bubu-Droid Obviously to start with: QPdfDocument::Error QPdfDocument::error() const (and statusChanged(QPdfDocument::Status status)). This is vital and first thing you should check. Verify ProjectSettings::instance().pdfPath exists. Have you tried multiple/absolute minimal PDF documents? Get rid of any concurrency/moveToThread. Is it safe/sensible to call loadDoc->moveToThread() while loadDoc->load() is running? Even if it is allowed, why/what is the effect of setting off a load before moving to a thread?

Do not run it in android emulator. Simply connect your phone to your computer and turn your phone debug mode on. You can debug your app directly in your phone.

Ok, akismet triggering is not always clear. Beside this issue, what was your question about ?