Qt DoubleSpin Box value changed slot has called twice

[Sowmiya R]

@raven-worx
ya, I have checked the stack traces.
both call has same traces

on_doublespinbox_valuechaged()
qt_static_metacall
qt_metacall

Thanks,
Sowmiya

[raven-worx]

@Sowmiya-R
then you probably have done the connection to the signal twice.

[Sowmiya R]

@raven-worx

I did't use any connect statement.
From Qtdoublespinbox right click option , I have clicked "Go to slot " and I selected value changed(QString) signal.
then it created slot function in CPP.

This is how I made the connection.

[raven-worx]

@Sowmiya-R
and no calls to QMetaObject::connectSlotsByName() for example?
I don't know if this is called implicitly. But you can try to rename the slot.

[Sowmiya R]

@raven-worx

Can you please elaborate your answer.

thanks,
Sowmiya

[raven-worx]

@Sowmiya-R
simply try to rename the on_doublespinbox_valuechaged() slot

[Sowmiya R]

@raven-worx

I have renamed the slot and connected in following way,

connect(ui->doubleSpinBox, SIGNAL(valueChanged(QString)), this, SLOT(doubleSpinBoxvalueChanged1(QString)));

Now also, the slot has called twice only if I click Qt doublespinbox up/down control.

If I press keyboard up/down key or mouse scroll up/down button, the slot has called once.

Thanks,
Sowmiya

[raven-worx]

@Sowmiya-R
there must be anything in your code causing this misbehavior.
Did you reimplement any event-handlers, event-filters, widgets, etc. in your application?

[mrjj]

Hi
Tried with 5.5.1 in default GUI project
Cannot reproduce.

[Sowmiya R]

I have created a sample application, it contains only QtdoubleSpinbox.
I have not overridden any methods.

below is my CPP code

#include "mainwindow.h"
#include "ui_mainwindow.h"
#include "qdebug.h"
#include <qspinbox.h>

MainWindow::MainWindow(QWidget *parent) :
    QMainWindow(parent),
    ui(new Ui::MainWindow)
{

    ui->setupUi(this);
    connect(ui->doubleSpinBox, SIGNAL(valueChanged(QString)), this, SLOT(on_doubleSpinBox_valueChanged1(QString)));
}

MainWindow::~MainWindow()
{
    delete ui;
}

void MainWindow::on_doubleSpinBox_valueChanged1(const QString &arg1)
{
    qDebug()<<"doubleSpinBox value changed: "<<arg1;
}

[mrjj]

@Sowmiya-R
Must be something in your Qt/compiler I guess ??
Can you try this test
https://www.dropbox.com/s/9eftxqghndn2bhw/myspinbox.zip?dl=0

[Vinod Kuntoji]

@Sowmiya-R ,
Hi,
You can use Qt::UniqueConnection in Connect statement.

[Sowmiya R]

@mrjj

I have tested your code.

I am able to reproduce the same in debug mode.
Can you please put a break point in slot function and run it in debug mode and see.

[mrjj]

@Sowmiya-R
Ahh, now i see.
Yes the debugger seems to interfere with event loop so it does indeed call it twice on one click
if u place break point there. Else Not.

void MainWindow::on_doubleSpinBox_valueChanged(const QString &arg1)
{
   static int hmm=0;
    qDebug() << arg1;
    hmm++;
    qDebug() << hmm;
}

"1,00"
1
"2,00"
2

I would guess that pausing it triggers the repeat feature and since it dont get an mouse release event its why.

[Sowmiya R]

I have developed a application using Qt, there regardless of debug mode or release mode value changed slot has called twice only on spinbox box up/down controls.
I try to reproduce the same in sample application, but its happening only in debug mode.

There is something missing in my application. I will check it out.
Thank you guys for you suggestions.

[mrjj]

@Sowmiya-R

But it ONLY happens for me if i set break point.
Never, ever else.

Do it happen for you if yo have NO break points ?

[Sowmiya R]

@mrjj

yeah!

Without break point also its calling twice.

[mrjj]

@Sowmiya-R
Ok, that does not happen for me.
Without break point it works correctly here.

I have no idea what could be wrong with your Qt.

Since you are using a clean project to test, i assume is something with your pc or Qt.

[Wael11]

The double call to slot happened in my case only with a breakpoint in the slot function, otherwise it is called once only. The second call was triggered by a timer event

[JonB]

@Wael11
For anyone reading this: This is known behaviour, which I stumbled across a long time ago and it was infuriating.

With a QSpinbox Qt Internal code uses a timer on clicks/presses. If you step through in debugger you exceed the timeout and get bad/double behaviour.

Simplest: change all connect() to QSpinbox click/key to pass Qt::QueuedConnection as last parameter for connection type, not default Qt::DirectConnection. Now you can use debugger breakpoints and all will be well. I wrote a method to connect all my spinboxes like this.