@abhishek999 This also does not answer my question.
Again: did you use same Qt version to build QGIS as you use to build your app?

And why do you have this in your pro file:

INCLUDEPATH += C:/Qt/5.15.0/msvc2019_64/include/QtXml

There is no need to add Qt include folders to the include path, you just have to enable the Qt modules you want to use in "QT +="

@Pl45m4 said in Problem with deleting QBuffer:

Simple: Link you release build to Qt release libs and your app's debug build to Qt's debug libs.

Yes. Apparently I was linking external release libraries instead of debug ones. The issue is solved. Thank you!

@SimonSchroeder said in Some doubts about Linux deployment:

@Paul-Colby I didn't know that linuxdeploy had plugins. We are currently using linuxdeploy to create the AppDir and then linuxdeployqt to add the Qt dependencies. However, if I'm not mistaken linuxdeploy also requires an older Linux version. (But, as you can see from my example we also didn't manage to create an AppImage with linuxdeployqt alone.)

Actually, I was able to deploy a working appimage using the three tools above! With the "low-level " approaches I still had problems.

I'm pretty new to these tools, but as far as I understand they can work together as plugins or just as three separate calls. I'm using Ubuntu 24.10 right now so they work on pretty modern systems (I didn't test the appimage on older systems because I don't need to support them).

@abhic
As @SimonSchroeder says, not sure why it should be an issue. But if it really bothers you, don't forget you could delay calling the connect()s/attaching your views to models etc. till the event loop has started by doing them in a function on a QTimer::singleShot(0) which you set off just before the app.exec().

Thank you all for your help. Based on your analysis, here is my solution,
Create section

auto pTextItem=new QGraphicsTextItem("QGraphicsTextItem",pV); auto id=reinterpret_cast<void*>(dynamic_cast<QGraphicsItem*>(pTextItem));

deletion

void DeleteGraphics(void* id) { if (id==nullptr) return; auto scene=m_pQGraphicsView->scene(); auto items=scene->items(); QGraphicsItem* item = static_cast<QGraphicsItem*>(id); if(items.contains(item)){ scene->removeItem(item); delete item; } }

@JonB Nothing to do with QSettings. It was a Unix locale issue. It turns out that the QSettings stuff was left there by the original developer of that code to allow testing without switching the language of his system. It mightily confused me ...

Ok,. To get smoother experience, have you tried running dumpcpp on that control?

That way you can get QAxObject subclasses specially suited for the control, and you don' have to write your own subclass like MyChildQaxWidget.

For various reasons I've trashed WSL, so this is no longer an issue :) I've installed an Lubuntu 22.04 build VM

@GrecKo Thank you very much! You really help me solve this problem!

@JonB At first I tried to run Wasm using asyncify parameter but it didn't change anything. I suspect that there are others things that are not fitted for Wasm, for example, click on a ToolBar ToolButton that opens a popup menu make Wasm crash, just like right click to open a context menu. I'm still hoping that there's a way to do those things with Wasm as common ways don't work. For the moment I'm simply putting my actions on ToolBars.

@JonB said in QTabWidget - unable to load multiple documents in multiple tabs:

In case that made a difference

In case @blossomsg forgot to implement some function which is needed for QPdfView or so...
Like Q[...]Model derived class without implementing setData

Good that it works now

@5taras I've only ever compiled static Qt libraries for Windows with MSVC. Scoop does not provide "%ROOT%\gnuwin32\bin", but it provides commands like mv and rm. It also adapts the PATH environment variable such that these tools are available on any command line.

It compiles for me, too, but it doesn’t run.

@Programist said in Glitched integrated terminal on Windows:

@JonB Unchecking Use internal terminal fixes the problem

As I said, I have never used Use internal terminal. and never had a problem with the normal, external terminal. And that option was only added to Creator a while ago, it never used to have an internal terminal.

@beginner123 This has nothing to do with qrc. When using qmake, if you set RC_ICONS, qmake creates the rc file in the building folder and adds it to the auto-generated Makefile. But cmake doesn't provide such feature., so you need to create it and add it manually.

@JonB I'm getting some errors when editing the link🌚 Thanks for the correction.

@JonB Interesting, thanks. I always thought of NTFS as case insensitive per se.

@JonB said in Frequent unresponsiveness of this site:

heroku

Oh well, I remember that one! About two or three weeks ago I had trouble opening the webpage at all on two different days. It just wouldn't load. I used different websites to check if it was just down for me and the majority of those pages claimed that the Qt forum was up an running. Pinging forum.qt.io would would send a response from heroku. Didn't have any problems recently (no slow downs, no unresponsive/unreachable webpage).

What did you do to fix the problem ?

This is not legal advice. But I can tell you an anecdotal story from my previous company I worked for.

The company produced heavy duty machines that could, for a better user experience, be equipped with a of the shelf android tablet and a custom app made in Qt.

We used to own a normal commercial licence there and developed that app with that licence. After some years during a renewal process, the QtC decided that this was an embedded device since the tablet was sold/shipped with the app preinstalled and would like money for each sold unit.

The end of the story is, the mechanic setting the machine up now has to do the extra step of connecting the tablet to the internet, getting the app from the Appstore and than placing it back into the machine.

Oh, and the company startet to transition away from Qt.