My problem is deeper and primarily concerns the lack of access to header files from the props file. You won't believe it, but I know what's going on, although it's a bit of a bummer. If I set my header file to a moc file, Qt suddenly doesn't see any include files. This happens with everything. moc files are treated as C/C++ headers and unfortunately don't have inherited paths from the props file. Any ideas on how to add these paths in the props file for moc as well? Currently, if I specify "local" at the very top of the paths window, it works – the moc file compiler sees these paths. But it doesn't want to respect the header file folders inherited from the moc file. How do I add an equivalent for QtMoc in the props file? I want the compiler to see the additional directories.

@Adla Thank you for sharing. GoogleMobileAds.framework in your Pods.zip works well. May I ask you how you generated this Pods.zip? I tried to generate it but it didn't work as yours. Here is my steps. Run Xcode Create an iOS app project with Interface: Storyboard Language: Objective-C pod init Edit Podfile pod 'Google-Mobile-Ads-SDK' pod install --repo-update But with the resulting GoogleMobileAds.framework, I got many errors, Undefined symbols for architecture arm64: "_$sBOWV", referenced from: $s15GoogleMobileAds24GADMarketplaceKitSignalsCMf in GoogleMobileAds(GADMarketplaceKitSignals.o) "$sScA15unownedExecutorScevgTj", referenced from: $sScTss5NeverORs_rlE8priority9operationScTyxABGScPSg_xyYaYAcntcfCyt_Tgmq5 in GoogleMobileAds(GADMarketplaceKitSignals.o) "$sScAMp", referenced from: _symbolic ______pSg ScA in GoogleMobileAds(GADMarketplaceKitSignals.o) ...

Hi and welcome to devnet Which version of Qt ? On which platform ? What if you use a QLabel like shown in the Qt documentation of QScrollArea ? Did you check the scroll bar policies ?

Hi, I have not checked the code of these readers but from a quick look at the QImagrReader::size documentation they might fall in the category of "needs to be fully read to get that information".

@J.Hilk said in I hear crickets chirping: @JonB since C++11 int main() has, as the only case in the whole standard, an implicit return value and not writing your own return 0 is completely valid. Do not flame on me, I do not agree with this decision Nor do I. Hidden or implicit actions are not a good thing. I wonder what would happen if you explicitly define void main() {} Since the startup code only cares about the symbol, not its type. c++ test.cc test.cc:15:1: error: ‘::main’ must return ‘int’ 15 | void main() { | ^~~~ Well, there you have it.

Hi, You don't need any intermediate widgets. When reimplementing createEditor, you can return a QColorDialog. You have an example in Python here.

@SGaist said in Connecting a QWebSocket to a given IPv6 address (no URL): What did you do that made things work ? It might be helpful to other people :-) There were two things: The QWebSocketServer was set to SecureMode, while on the client's side, the request URLs were all "ws://", so changing the QWebSocketServer to NonSecureMode helped a lot. When the lookup of QHostInfo is successful, the lookupId of is set to -1, and the errorString is then "Unknown error". So there really was no problem with this to begin with!

@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

Possible find real row like that: realRow: treeView.index(row, column).row

@Hanson @jsulm Thanks a lot!

@SMF-Qt cool :)

@SimonSchroeder I've read it out of curiosity now. But this doesn't influence how you can publish your Open-Source projects (with and without internet access) on something like GitHub, right? This only effects commercial software or really everything that is being published by "someone" within the EU?!

Thanks Ekkehard Gentz, I will check with this and let you know the results.

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.

@Iann29 Hi, I know this is a little late and I was running into the same issue but this is what fixed to for me. I went into the kit menu and I a kit for Desktp Qt 6.9.1 MinGW 64-bit (default) that had always come up as an unsupported/unavailable kit. However, all I had to do was clone it in the kit menu, see here. [image: 468b3f2d-cea4-4c50-bf91-0600151c6c1b.png] Then when I created a new project with Qt Quick Application for Python with PySide6, it let me select not only the python kit but also my desktop one that allows the designer to work.

The issue is likely due to the QDialog not properly mapping global to local coordinates. Use mapFromGlobal(QCursor::pos()) or ensure the dialog uses the correct coordinate system with event->pos() inside mouseMoveEvent().

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