General and Desktop

@crystalidea Whats your XCode version ?

@clhallinan said in Qt Creator: How to access QLabel inserted by Ui Designer from MainWindow.cpp: I'm gaining competency w/ C++, but a beginner w/ Qt. Your question relates to general C++ programming rather than anything Qt. @Gerhard's reply above is correct. When you declare class methods or variables, you normally do not put static in from of them. This means they have to be accessed via an instance of the class, by one of instancePtr->method(); instance.method(); If however you have declared the method/variable with static then you do not access it via an instance. That is the time where you go ClassName::method(); so you are using the ::. That is what the error message was telling you. You might want to read up on the use of the static keyword in C++, for future reference.

I can choose the installed Qt version on the solution, but on the project everything is still disabled... I have sucessfully compiled a Qt project at home where I have VS 2017, here at work I have VS 2019. Anybody having issues on the 2019 integration?

Rebooting computer fixed. It was not enough to restart Qt Creator, I had to reboot. I might have been fixed if I just logged out, I don't know. Sounds like a X11 issue.

You're welcome ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so other forum users may know a solution has been found :-) Seems the cache hid the fact that you did everything already !

if (ui.ComboBox->count() == 0)

Maybe a dependency is missing so the dll can not be loaded -> use Dependency Walker to see what dependencies you're missing.

Hi @simozz, https://github.com/ohwgiles/quilte is a project that does this more or less - it's a terminal emulator written in Qt. It has dependencies however and will not work on Windows, if I get it right. But it should show you the principle. Regards

@JonB said in Problem with QWebView: But what happens when it's called first time and there is no "previous" application to close? Nothing. Based on the reference: https://doc.qt.io/qt-5/qcoreapplication.html#exit

@fT3g0 could it be possible that you start from scratch? :-) I mean, it seems from the files and filenames you posted that you're kind of misusing the capabilities of Designer and uic tool. If you create a simple project in Qt Creator, or a form class with Designer, you'll see that 3 files are created (let's say it's a dialog named MyClass): myclass.ui myclass.h myclass.cpp you see that there's no ui_myclass.h file (yet...) The idea is that you edit the form graphically with Designer (adding other widgets, buttons, labels, etc. to the dialog) and then you provide your dialog class implementation with the .h/.cpp (mainly the .cpp file). The ui_myclass.h file will be created at compile time by the uic tool and it'll serve as a bridge between the GUI you designed and any implementation code you may need to better suit your class. See more about using Designer and .ui files here.

@JonB Many thanks. That gives me plenty of thoughts! I had a rethink. The basic idea as follows: [image: 3706ffd6-9df3-43c4-a136-9ed1a0607cd3.JPG]

@jsulm Sorry by mistake i have posted that comment here that was for quickwidgets and that got resolved now thanku for your response and time

@JonB said in Yet another QSqlTableModel removeRows issue: @Mark81 And what @VRonin has written is certainly better then no test at all! However, to be clear, in a case like this where an operation could genuinely return false, you must/should not just do this, you must provide proper error handling. Otherwise it works fine in your own development tests, but silently fails and does not check when you send out your release code, and you/the user have no idea it did fail or why! You probably already know that, just saying for other readers.... Yes of course. As said I was a step before that - due to the doubts on the docs. Now, I've already connected a signal to show an error message to the user.

@hobbyProgrammer said in window closes after completing certain actions.: @JonB Hi, just a quick update. I think it does get there, but it prints this part before going executing the slot. It's really important for those who try to help you to give accurate description of what does/does not happen. Everyone was trying to figure how your connect() could not complete and get to the next line....

Issue closed. All done by my own. This examples demonstrating 3 version of releasing chained steps of application loading process independently of which type the object is or using threads.

Thanks @JonB . The problem seems gone when I remove these "process terminate" code.

@Mijaz said in > Makefile:68: recipe for target 'verifyspec' failed: I did not find any proper solution to my query. And you did not reply to the post from @SGaist