C++ Gurus

@JonB I think it's some kind of hint for the reader to understand the source code better without browsing the whole class. Like: in some class.h where someFunction(int a, int b, float c) is declared void someFunction(int a, int b, float c); and (if I'm correct) everywhere the function is used, on every call, the code browser adds the names from the header, so you know right away what this // some code // ... someFunction(42, 42, 13.37); // ... means. With the hint it looks like: ( imagine meaningful names there :D ) someFunction( [ a ]: 42, [ b ]: 42, [ c ]: 13.37); Therefore I don't think it's C++ :) Btw: I also like woboq to check Qt source code :)

@mzimmers inline might be more convenient. No need to define it in cpp file. inline static bool m_use24hourTime{ false };

I think you will have to use something like https://www.openldap.org/software/man.cgi?query=ldap

@J-Hilk said in Repost Parent / children / methods ? which way up ?: (Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship) Oh boy... Had to read this for my studies :D Pretty helpful and well structured "guide" on how (not) to write code.

@J-Hilk arrrrrrrrrrrrr

QAction *action = qobject_cast<QAction *>(pItemObject); Has been explained to you before.

I'm sorry that you have to read documentation if you want to learn something. Especially something such basic c++ stuff.

To access the grandparent use parent()->parent()

Dear @AnneRanch, you are not supposed to simply delete posts, if they have become irrelevant and/or solved. The rules in this forum are to mark them solved, when they are. This is because they are likely to be a reference for others with similar issues.

@Paul-Colby is hinting at something good. If you want to be able to cleanly test things, you should consider making a library with all your widgets and business logic and your application will be mainly a main.cpp file using that library. This will allow you to build a test suite for your library in a simpler fashion.

We can only guess, @AnneRanch, under more because you don’t tell us which type text is. We also don’t know what „doesn’t work“ means. Is the field empty, partly filled? addPlainText always adds a new paragraph. Maybe that’s related.

I would recommend to no longer use Q_FOREACH it is deprecated for a reason! Use the ranged based for loop the c++ standard offers for (auto &item : container) less error prone, less conflict with other libraries, faster compile times.

@kshegunov Thanks a lot :)

@SamiV123 , @JoeCFD @JonB @jsulm Thank you

i compiled it successfully using qmake.