General and Desktop

@wasimIM I don't have a solution. Maybe try with more recent MS compiler if there is a newer version?

Hi @jsulm, I updated the main function to initialize the EventLoop it is working as expected. Thank you very much for your help, Pierre-Emmanuel de Robien

@Quvonchbek-Bobojonov What is your question?

@Christian-Ehrlicher Does exist a proper profiler for embedded arm?

@JoeCFD thank you

Thank you a lot! Using GCC 13.x solved the problem. It also solved the issue with WIN32_EXECUTABLE TRUE CMake target property causing the window to crash early. For anyone else encountering this issue, set the environment variable for the compiler path to point to Qt/Tools/.../bin directory to make sure that GCC 13.x is used instead of GCC 14.x

@Pl45m4 said in State of QPrivateSignal: I don't understand the struggle :) Event the suggested solutions here seem like overkill... It's not possible to connect to your private Q_SIGNAL from outside of the class. That's the requirement.

I suggest something simpler: check the Tetrix example. It's a fully explained example that implements what you want to do in details.

@JonB Thanks for your response. + I use built-in model. Yes it's clang I thought it's because of git. + So, i thought that QVector is more preferable than QList. Also i already used QVector in all other code. P.S. Why should i call explicitly QCommandLineParser in CommandLineParser? Isn't it called implicitly?

Thank you, that change does fix the window level problem! :-> Qt::Tool seems to at least do no harm on other platforms. I mostly develop and test on macOS, so I'd have to check on the other platforms to confirm for sure, but nobody has complained about that. :-> Anyhow, Qt::ApplicationModal solves the immediate problem, thanks!

Hi, I would check the implementation of QSqlRelationalDelegate, mimic it and add the filter there.

Well... if you want it done right do it yourself XD Obviously, Qt has it's pedigree and Qt Bindable Properties are impressive in their own right, and I would never claim to be better than a team of veteran professionals; but, in this one case this (and a few other) quirk(s) of Qt Bindable Properties ended up bothering me enough that I decided to go nuts and take a stab at them myself. Although my system doesn't have quite the same level of polish as Qt's, I'm very satisfied with how they turned out. So, if it happens that any one else: Doesn't need QML integration (i.e. C++ properties only) Doesn't need to access properties abstractly through the meta-object system and Wants their binding evaluations to only ever run once per-update and never read stale values, such that the evaluation of the above example is always: 1) pStruct 2) pEmpty 3) pHello with almost the same API, feel free to partake in my experiment :) Qx Bindable Properties There's an easier to follow example in the documentation for this above under "Advantages".

@JonB My service launches the client almost immediately after the user logs in; it seems this is determined using DBus. I tried running the client from the terminal, and everything works. Maybe I should change the method of launching the client, for example, using DBus?

First I would draw a circle of that size in a drawing program, and look if the actual size is 60mm across. Screen DPI is not always 100 % accurate, and the OS might also muddle up the waters. Have you checked the values in QScreen::logicalDotsPerInchX and logicalDotsPerInchY? On the graphic view side, you have multiple coordinate system transformations before you get to screen pixels: Item coordinates -> Scene coordinates -> View coordinates -> Screen coordinates. Any of these transformations could affect your outcome. So you need to check e.g. that the scene is displayed in the view at 100 %

Hi and welcome to devnet, I haven't used CLion yet but I found this tutorial from their documentation. Did you follow it ?

Sure is, I can only assume I've hit a combination of hardware/complier/toolchain that exposes a bug somewhere - I may follow this up with GNU on this issue, though reading their guidelines for bugs they may never look at it :-) I've added my PC spec as this may help others searching for similar issues in the future: OS Name -> Microsoft Windows 11 Pro Version -> 10.0.26100 Build 26100 System Model -> Precision 5690 Processor -> Intel(R) Core(TM) Ultra 7 165H, 3800 Mhz, 16 Core(s), 22 Logical Processor(s) Installed Physical Memory (RAM) -> 32.0 GB Drives size: -> 1.86 TB (2,045,443,567,616 bytes) gcc --version gcc.exe (Rev2, Built by MSYS2 project) 14.2.0

@JonB Good catch ! As for what I meant: the uic file is clearly for a class named MainWindow and not HolaMundo.

@gabello306 @ChrisW67's suggestion is indeed the simplest if you are willing to assign static tooltips to existing items in the list, and recommended if that is the case. However it will require some further work if you insert, delete or move items in your list. Do you need that, or is the list fixed? It also displays the information as a popup tooltip over each item rather than your original requested "Above a QListWidget I must display an index number" so depends whether you mind about that.