Signal doubleClicked(QModelIndex) crashes application on next accepted() signal.

[adutzu89]

Put a breakpoint in each of the functions: ListaAng::rSelect(), void widget::tabelSql, widget::ferVizAng() and curatare().
Run your program in the debugger. Single step until it crashes then you will know what your program did to deserve it.

My money is on whatever you are hiding in curatare().
Really though, refreshing the content of the table should involve causing the QSqlQueryModel to requery the data, not stuffing around with new widgets and layouts.

// QSqlQueryModel *model;
 
model->setQuery(model->query());

// QSqlQueryModel *model;

model->setQuery(model->query());

To copy to clipboard, switch view to plain text mode 

curatare() contains the following:

QLayoutItem *child;
    while ((child = layoutCentral->takeAt(0)) != 0) {
        delete child->widget();
        delete child;
    }

QLayoutItem *child;
    while ((child = layoutCentral->takeAt(0)) != 0) {
        delete child->widget();
        delete child;
    }

To copy to clipboard, switch view to plain text mode 

Which removes any widgets that are in my central widget, but this is only called when I trigger menu actions and not when I refresh the table, I will try first your solution as is it now I am remaking the tableview entirely.
And it only cause my app to crash after calling rSelect(QModelIndex) from doubleClick, if I call it from shortcut(QKeySequence) it does not crash.


Update:

Solved the issue, thank you both.
I restructured my code, and now I am just resetting the query as you,ChrisW67, said; also as you both seen I was calling both tabelSql() and ferVizAng() from widget and when semnalAct(QString) signal was emited the app would do tabelSql()(trying to clean the central widget and remaking the whole table) all over again which here is where my app was crashing.

Now I moved the ferVizAng() slot inside table file and just reseting the query when I press the accept button.

Again thank you both for the assistance