General and Desktop

@Khadeer Why do you need the Gnu compiler? Just recompile using clang from Android NDK.

@Zbigniew-Sch Thank you for your answer, I have solved my problem. I created custom MyWidget derived from QWidget and overwrited paintEvent method. Then called setGeometry in constructor method and called resize() when scaled. It works as I want.

@Christian-Ehrlicher Thank you very much !

@Qt6User https://doc.qt.io/qt-6/build-sources.html

Hi, Can you provide a minimal project that shows this issue ?

@Pl45m4 It was not intended ironically. It was like that when I last investigated, maybe copy/paste etc. is available now. I will check next time I am in Designer.

Jira ticket has been raised for Issue 1: QTBUG-138495

@snoriman said in How does AUTOMOC and CMake determine which sources toscan?: think there is more to it then that because how would adding include_directories() trigger automoc on an external dependency ( It does not.

@Nmatan said in How to scale columns evenly?: but is there no method to at least have an 'initial' size for the columns See https://doc.qt.io/qt-6/qheaderview.html#ResizeMode-enum

This might be the Qt Designer library from QtTools repo

@jamat13 Do not use signals/slots for either receiving an immediate reply from any attached slot(s) nor for "waiting" for something to happen as a consequence. That is not what they are intended for --- they are a "notify and continue" paradigm. If you want a "response" instead either use a direct function call or in the signaller emit the signal, save whatever state is necessary and continue to the Qt event loop, while the slot emits another signal when it is finished which the originally signalling side acts on in its own slot when it arrives. Use a QTimer at the signalling side if you need to know that the slot has not "replied" within a period of time. answered = false; emit action ("toolbar", "1whatpage"); QElapsedTimer timer; for (timer.start (); !timer.hasExpired (2000); ) { if (answered == true) { *dbg << "answered " << timer.elapsed () << "ms page " << page[1] << "\n"; dbg->flush (); answered = false; break; } Your loop is very "busy": it burns your CPU and completely blocks the thread it is in. Since it does not enter the Qt event loop it does not allow normal processing to continue. Behaviour of your code probably depends on whether attached slot(s) run in the same thread or a different one.

@SirMarcin I'm not sure how to deal with your situation :( but the <AdditionalIncludeDirectories> node in the props file is passed to the compiler to specify the directories to include header files, not to compile those directory files.

@snoriman hi, The aqtinstall project seems to fit the description: command line installation of Qt.

@JulsPower I understand you probably lack the motivation and time to do it, but it would be interesting to see the differences in the build between cmake generated makefile an qmake generated makfile. Obviously the two are building/linking differently. Smells like a build flag isn't the same in cmake debug

@Hanson @jsulm Thanks a lot!

Yes, this is Windows 11 but with dark theme (which is "fusion", the common style). With the default light Windows theme the indicator is on Top&HCenter, in that case my issue is not valid.

I found that the info.plist file is sometimes generated and sometimes not generated. I don't know why

@rparon said in uninitialized data passed to QStringList QCoreApplication::arguments(): Hi jeremy_k, that is an interesting point, The point seems to have been missed. Treating const data as non-const is undefined behavior, and the C++ standard allows a conforming implementation to do anything when UB is invoked. Command line arguments and historical usage are irrelevant.