You seem to be in the case described in QTBUG-135203.

I just created one with a minimal project with a dummy main.cpp and: TEMPLATE = app QT += widgets SOURCES = main.cpp QMAKE_APPLE_DEVICE_ARCHS = x86_64 arm64 as .pro file content. The build is screaming at me because the x86_64 symbols are missing so it does work correctly (the architecture missing is expected in my case). I also tested with that variable removed from the .pro file and set on the command line and it's working as expected as well. So some things to check: Do you have QMAKE_APPLE_DEVICE_ARCHS set somewhere in one of your project file ? Are you doing this call from a clean state (i.e. did you call make distclean before calling qmake? Do you have some .qmake.stash file lying around that might wreak havock ?

I started getting "1060 Out of heap space" when I upgraded to Qt 6 and VS 2022. The "-std:c++17" flag triggers it. The solution was to update to VS 2022 ver. 17.14. This may be unrelated, but I'm posting it to help anyone else coming here with this problem.

I started getting "1060 Out of heap space" when I upgraded to Qt 6 and VS 2022. The "-std:c++17" flag triggers it. The solution was to update to VS 2022 ver. 17.14. This may be unrelated, but I'm posting it to help anyone else coming here with this problem.

I started getting "1060 Out of heap space" when I upgraded to Qt 6 and VS 2022. The "-std:c++17" flag triggers it. The solution was to update to VS 2022 ver. 17.14. This may be unrelated, but I'm posting it to help anyone else coming here with this problem.

@Christian-Ehrlicher Good news! It's working! The solution was to upgrade from VS 2022 ver. 17.13, to ver. 17.14. I tried getting VS to update itself, but it locked up and wiped itself. I had to download and re-install VS 17.14. Here's the kicker: I got the suggestion from OpenAI/ChatGPT! I'm an AI skeptic, but I have to give credit where it's due. Also, ChatGPT suggested "-bigobj", but that didn't make a difference. A sincere thanks to Christian and hskoglund from a 77-year old, half-blind hack :o)

I see. This might be useful to some, but I'll probably refrain from trying to mislead Qt and Atlassian about my country. After all, it’s their decision, so I don’t see any point in getting around it.

@Mephisky said in segmentation fault in QTCPSocket::readAll(): So, i think i shall move NetworkCommander totally into the new thread?, Don't use a thread at all unless you have very big reaons to do so. I would guess you even call socket->connect() from the wrong thread and maybe others.

Hi, From a quick look, I think there's currently none. One thing you could to is port the module to Qt6.

Hi and welcome to devnet, On which OS are you experiencing this ? Which version of 6.10 do you have ?

How about getting the source code of tinyxml2 and building it on Windows. It is not hard, I guess. I build it for Android.

@Mbkerdellou said in What is the best way to show multiple pictures on a widget?: Is the best solution creating three QLabels, setting a pixmap to each, and setting QTile as their parent? I have tried using QPainter but it seems that for that I have to change the paintEvent function? You could do it this way, but it would be quite problematic to achieve: As @JonB says, QWidget objects have overhead, for example in memory and in the time it takes to distribute events (which is roughly linear in the amount of widgets you have in a window) QPixmap is a windowing system resource which Qt can't implicitly share for you, so each label would need a copy of the pixmap for the base texture etc - in general bad for memory (and on some operating system there is a limit to how many pixmaps can be allocated). Probably not a problem for the scale of your game, but still something to keep in mind. It is not sufficient to just have the title widget be the owner of the three labels - it needs to layout them (set their size and position). There is no built-in layout manager (a subclass of QLayout) that will quite fit the bill here - QStackedLayout is a starting point but it will not show the background label when showing a character label for example, which kind of defeats the purpose. The way I would implement this in Qt Widgets would be by creating a custom widget for representing the title by creating a class that inherits from QWidget and drawing it manually. This is indeed done by overriding the paintEvent method. In it I'd setup a QPainter and draw from the bottom layer up - first the background on the entire contentRect(), then the player/enemy/ladder/whatever texture, and then a life bar on top by filling a rectangle with a gradient brush. The textures can be kept as static QImage objects shared across all instances of the title widget. Though - Qt Widgets isn't ideal for this scenario, QML is much more appropriate. But that depends on the parameters given to you for your project of course.

I fixed this by replacing "%{ActiveProject:Name}" with just "%{Project:Name}". But how does one know the difference? In the list of variable replacements, they both resolve to "SBBL". Does this have to do with the "TEMPLATE=subdirs" setting?

Your picture still shows a black text. Please use a recent Qt version and provide a minimal, compilable example including style you use and the color value you expect and you got (however you read it out, maybe a screenshot and read out the value with an image editor like e.g. gimp)

@why_bother said in Set icon for top left title bar of all windows and taskbar: I've looked at https://doc.qt.io/qt-6/appicon.html that mentions setIcon() and I'm totally confused, as I don't understand what the difference between setIcon() and setWindowIcon() is, let alone which one I'm supposed to use. setIcon() is for QWindow, which we usually don't use directly. setWindowIcon() is for QApplication, it will call QWindow::setIcon() internally for every window. As for the linked documentation, it is actually for changing the icon of the executable file, so it need to be configured in the project file, instead of in the code, and need to be certain icon format, instead of any picture format. When the executable file icon is set successfully, it should become the default window icon for QApplication, so there would be no need to call QApplication::setWindowIcon() or QWindow::setIcon() if you only have one icon to show. (This is my experience on Windows, not sure if Linux is the same case.)

@DayatKun0 What error do I mean?! The error you are talking about in your inital post... You should have mentioned QML and Qt Design Studio as well...

@PR04 You can check in SquishIDE if object Exists with given set of properties. Frist you need to start AUT/connect to it, open Scripted Object Map and select your symbolic name (1. - on the screenshot) Later you press Check Existence (2. - on the screenshot) It will tell you if your list of properties in real name are OK and object can be found. Check out this screenshot from my SquishIDE: [image: 72637c04-cada-4bae-89ee-7fea5c28ee5e.png]