C++ Gurus

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.

@AnneRanch said in Another "reuse" question:

**this message does not show anywhere**

auto pC = new Console; // Original class auto pSB = new QStatusBar; // Additional status bar auto layout = new QVBoxLayout; layout->addWidget(pC); layout->addWidget(pSB); auto consoleWithStatusBar = new QWidget; consoleWithStatusBar->setLayout(layout); consoleWithStatusBar->show(); pSB->showMessage(" TEST status bar message ");

@inglis-dl adding: also tried variations on -I and -L path names such as / or \ separators as well as adding paths to windows system PATH envar

@JonB said in TEMPLATE = lib ?:

that is not to do with you including or not including .h files in .cpp files.

That has been discussed and concluded TRUE.
Let's move on...

It is to do with your code actually calling a function in another .o file and that not being passed to the linker to resolve.

That is NOT the case - I have described how I use "add library"
to add it to subproject .pro file - who is using it.

Let's move on...

I suspect the link to .so IS THE issue...

@jdent
As @Christian-Ehrlicher says, who knows, behaviour may be compiler-specific and it does not claim to check everything, I think. My own guess is that the call to showing the dialog avoiding the detection may well be "coincidence", nothing to do with the specific call, many other things might cause it to skip.

Under Ubuntu, Qt 5, gcc and .pro file having

CONFIG+=sanitizer CONFIG+=sanitize_address

it does report a SIGABRT on code like yours, whether I put in a QDialog and/or exec() or not. I do not know whether you can use those CONFIG lines from Qt with MSVC or not.

One tiny thing: just in case MSVC is "optimizing out" your x code completely because it has no effect (e.g. gcc warns "unused variable"), add something which uses x after your code.

@AnneRanch UPDATE / GOTCHA
When reusing (C++ "feature") project in subproject one better change / rename "MainWindow" class name. .

I start with renaming the existing class header file. QtCreator gives an option to rename both .cpp and .ui
BUT you must start with renaming the header file FIRST.

Then you can rename the MainWindow class and that will change the "object" name in .ui file! l

Another "GOTCHA" - the #include ui_ file , generated from .ui file MUST be changed manually !

Good luck...