C++ Gurus

@Bharath-kumar As @Christian-Ehrlicher has said. I don't understand: in your code you know how to produce a certain number of digits via QString formattedString = QString::number(doubleValue, 'e' , 4);, so why do you have QString dataString = data.toString(); earlier and expect that to produce a limited number of digits?

@JonB said in matherror issue: If the int _matherr (struct _exception *pexcept) appears in merr.c you need to trace from there to find out where it (_exception) is defined. Maybe it's a MinGW-only definition/file, I don't know. If I compile in Clang int err_ind = 0; int _matherr (struct _exception *pexcept) { err_ind = 1; } Compilation OK, but math exception doesn't work

If you want an integrated application (not the variant with QProcess that @SGaist suggested), the first step would be to separate your command line application: parse the command line parameters into variables and the actual functionality should then be refactored to a separate function, that takes these variables as function arguments. This ensures, that the same function can be called from your GUI application. Inside the GUI application you would then have input widgets for each variable and a button labeled "Run" (or similar). When "Run" is clicked, you collect all the different inputs and call your refactored function. If this takes longer to run, you should put it into a separate thread (and then the other solution "use a QProcess" is not too different to implement, though for the perfect solution threads should be used, but QProcess will be easier). Maybe for threading a simple QtConcurrent::run() will suffice. You will have some trouble if there is important console output (writing to stdout/stderr) of your existing application. How do you want to interact/signal errors? For a good solution this would require deeper changes into your existing application. With the QProcess approach the only thing you can do is to show the output to the user. Otherwise, you could use callback function for output. In the case of your command line application this can still write to the console by default, and for your GUI application you register a callback that shows a QMessageBox. Maybe the callback can even return a value (e.g. from the message box) to continue or abort.

@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 :)