@Christian-Ehrlicher Oh well, did not expect the solution to be that simple (if this is actually the case) Understanding the Qt Framework's library/module design is pain :D

@MEsc said in Accessing value of vector only once: I have another function MainWindow::on_start_clicked() When this Function get called (here via button), values should load in vec. QVector<QString> vec = loadfrom(); That looks like vec is a variable local to the slot attached to the button. You load it and then it is destroyed when the slot exits. If you want the vec object to have a longer lifetime then you need to arrange that. As @Christian-Ehrlicher says, making vec a private member variable of the MainWindow class is probably the right approach. So, class MainWindow: public QMainWindow { ... private: QVector<QString> m_vec }; void MainWindow::on_start_clicked() { ... m_vec = loadfrom(); ... } void MainWindow::on_answer_returned() { ... // do stuff with m_vec ... } This is basic C++ knowledge and not Qt specific.

Well, huh. I thought I tried that one with the bigger project before, but it does work with the test program here, so that must have been something else. Thank you for your assistance.

QHeaderView does not use delegates unfortunately. The solution I'd suggest is to have a QLineEdit widget spawn on top of the header to do the editing rather than spawning a dialog

You have to use the correct moc to your headers. When you install Qt you must also install the devel tools for this specific Qt versions. And you should fix your buildsystem to call moc. Those moc files do no belong to the sources.

@jars121 So please mark this thread as SOLVED now. Thanks.

"misc_common.h" is located in the "misc_common" folder, no ? That's the one you have to add to your project.

Hi @Michael-R-LegakoL-3com-com, I think a better approach, is to use a macro to apply the dllimport/export, and then enable that macro in the library only. For example, if you look at qmake's simple_dll test example, the simple.h header contains: #ifdef SIMPLEDLL_MAKEDLL # define SIMPLEDLL_EXPORT Q_DECL_EXPORT #else # define SIMPLEDLL_EXPORT Q_DECL_IMPORT #endif class SIMPLEDLL_EXPORT Simple { ... } Then the simple_dll.pro file contains: DEFINES += SIMPLEDLL_MAKEDLL So, this way, when the library is being built (via simple_dll.pro), then class is dllexport'ed. But when other code uses that same header (in doesn't define SIMPLEDLL_MAKEDLL) then that same class is dllimport'ed instead. Typically, you end up doing this sort of thing to many classes in a single library, so rather than having the #ifdef ... #define ... etc in each header file, it often ends up being written once in a "global" project header of some kind. For example, Q_CORE_EXPORT gets defined in qglobal.h, then used throughout all of the exported core Qt class headers. Also see: When creating a library with Qt/Windows and using it in an application, then there is a link error regarding symbols which are in the library Cheers.

@gabor53 I reinstalled Qt, I even switched back to 5.6 but the problem remained. Is it possible to mess up the Qt setting for the project or the code to trigger the disk full message? It not happen with other project. Thank you.

@egg.nut I met the same question,how do you solve it?

@Wieland No problem :)

No worries for that :) Since you have it working now, please mark the thread as solved using the "Topic Tool" button so that other forum users may know a solution has been found :)

@bsomervi Better is in the eyes of the beholder. Why keep track of something that the system keeps track of for you? I don't need this information immediately, just when a context menu item is selected. Thanks for the answer.

SOLUTION: ui->tableView->model()->setHeaderData(2,Qt::Horizontal,QFont("Arial",10,QFont::Bold),Qt::FontRole); Actually everything is stated in the Qt Help, - just need to know how to correctly use it :)

The solution was to explicitly call sort after the call to invalidate with setSortingEnabled set to false. Both invalidate and sort were necessary

@SGaist Hi, I resolved the issue. I was actually firing sendCustomRequest() api as I was using a specific url query in request which was needed in to fire via HEAD method. Before firing sendCustomRequest() api I was also creating & resetting my ssl configuration. So, instead I directly now use the head() api to fire my HEAD request. Now,finished signal by reply gets fired instantaneously & I am able to read my specific header value in response in no time. Thanks for your time..!! :)

My apologies, I will create a new thread. Thanks for all your help! (and putting up with my stuff :) )

@mrjj No, I didn't know that, thanks for pointing my errors out. :)