Problem connecting Signals and Slots in a modal dialog

eschmo

Yes exactely, bu it was the right Dialog all the time but obviously just the appearance not the code.
I've also switched to the new connection syntax but debug shows true for the old way as well.

    qDebug() << "Tab Connect:" <<connect(ui->tabWidget,&QTabWidget::currentChanged,this,&H17T_Settings::onTabChanged);
    qDebug() << "Button Connect:" <<connect(ui->Btn_Save_Settings,&QPushButton::clicked,this,&H17T_Settings::close);

Tab Connect: true
Button Connect: true

mrjj

@eschmo
Hi
Super with the new syntax as then, we are very sure it's not the connect.

Try replace the close() with accept();
and see if it then closes.

btw does Settings::onTabChange gets called ?

If not I think its something else.

eschmo

@mrjj

no, nothing is called at all.

I've redone the connection for the "Save Button" with the designer and it worked straight afterwards.
I did it again in the cpp and it doesnt work. thats quite irritating.

mrjj

@eschmo
That is very odd.

You only create a H17T_Settings once place right ?

and if it works assigning a slot in Designer for the same dialog then it must work too
with manual connect as its much the same.

Just to be sure. You go to Designer and use the "go to slot" function to create a slot
for it and there you call close()

but if you don't do this and just have the manual connects it wont work ?

eschmo

@mrjj

yes exactely, i'Ve even put the connection for tabwidget currentChange() in the ui file by hand and it works with H17T_Settings close().

But it will not work in anyway with my connections over the cpp, even if they succeed to connect.

Thats quite strange...

mrjj

@eschmo

Yes its very strange as it should work when connect returns true and besides with the
new syntax, the compiler would tell if something fishy.

All seems fine with H17T_Settings soI cant I guess why onTabChanged() is not called.

J.Hilk

@eschmo said in Problem connecting Signals and Slots in a modal dialog:

Yes exactely, bu it was the right Dialog all the time but obviously just the appearance not the code.
I've also switched to the new connection syntax but debug shows true for the old way as well.

No it was not, It could not have been the correct dialog, when you instantiated a different dialog.

I think you have simply multiple dialogs instances ore something along that line.

can you post/link a minimal compellable example?

eschmo

@mrjj
yes i'm a little bit confused and lost about it.
anyway, thanks a lot for your help.

@J-Hilk

it has appeared exactly as the dialog i've prepared in the designer.
Thats for sure because of

frm_Settings.setupUi(SettingsForm);

and fits why not my overloaded constructor is in place but the standart one of QDialog.

I couldnt find any other instance in my code, but i dont see how this could affect the called dialog.

I've put the whole project to github if this could help.

https://github.com/eschmo/H17-Timing/tree/main/H17-Timing

Thanks a lot for your time!

J.Hilk

@eschmo
inside your h17t_main.h
your SettingsForm member pointer is this:

QDialog *SettingsForm

and it should be:

H17T_Settings *SettingsForm;

That should fix your issue, but from looking at the rest of your code:

You're going to leak memory with H17T_Settings instances.
You're set up to do threading stuff that apparently have access to GUI stuff

Both are a big nono... :D

mrjj

Hi
Also a note

You do

void H17T_Main::onSettings()
{
    SettingsForm = new H17T_Settings; // this also calls setupUI
...
    frm_Settings.setupUi(SettingsForm); <<< what is this for ? now you create all
     the widgets once more so the other ones that was connected in the constructor is no longer 
    the ones shown on screen. This should not be needed to call manually.
    SettingsForm->show();
}

That seems to be the reason as it works without that line :)
alt text

eschmo

@J-Hilk said in Problem connecting Signals and Slots in a modal dialog:

QDialog

Sorry, not sure why this was in the files i've uploaded but this was allready changed yesterday.

Finally thanks a lot, because the solution was your second tip.

I've removed it completely and everything is fine now!

Thanks a lot to both of you!!

J.Hilk

@eschmo said in Problem connecting Signals and Slots in a modal dialog:

I've removed it completely and everything is fine now!

I'm afraid that credit goes to @mrjj ;)

Sorry, not sure why this was in the files i've uploaded but this was allready changed yesterday.

I'm talking header, not cpp