Help with QTimer scope

[jsulm]

@Christianvs To add to @sierdzio : why do you allocate both timers on the heap? Why not just:

private:
    QTimer weightChangeTimer;
    QTimer changeWeightTimer;

[Christianvs]

@sierdzio @aha_1980 @jsulm

Thanks for the answers! I've tried following (i'm sorry about the messy code, in my attempt to get this working lines have been added, changed and commented out):

I am not sure if i get the new connect method right. In the case it should be the right way i connect it, i still seem to have the same problem as before.

@jsulm
I actually started out with initializing the Qtimers in the header file, but in my search for my mistake i tried allocating on the heap

[jsulm]

@Christianvs What is ROS_INFO_STREAM?
Can you try qDebug() instead to verify the slot is called?

[aha_1980]

@Christianvs Are you sure your debug output works? Can you set a breakpoint in the slot?

Beside the "mess" your code looks Ok.

If it still not works, you have to look if you somewhere block signals or if the event loop is not running etc.

[Christianvs]

@jsulm

The whole project is connected through ROS as it controls an AC motor. To be honest i'm not sure if qDebug works in my current setup.

None the less i got the timer to say it's active by running isActive() after i start the timer (what a stupid mistake!)

But that actually solves part of my problem as i now know the timer is actually active!

But it still does not execute the timerTest() function!

[jsulm]

@Christianvs said in Help with QTimer scope:

qDebug works in my current setup

std::cout should work.
And you can place a breakpoint inside the slot and start through debugger.

[Christianvs]

Could the problem be that my weightChanger object somehow needs to be initialized in another way? By using new ?

Above is where i actually initialize the object and it is within this object the QTimer is stored

[sierdzio]

@Christianvs said in Help with QTimer scope:

Could the problem be that my weightChanger object somehow needs to be initialized in another way? By using new ?

Yes! When this function ends, it will be destroyed (object goes out of scope).

[jsulm]

@sierdzio @Christianvs You can see this type of error very often here :-)

[Christianvs]

Yay! Now that i create it on the heap using new the timers work without any problems!

Thanks for the help all of you! :)

[sierdzio]

Just make sure it is cleaned up properly afterwards (either assign this as parent or call delete on it when you don't need it anymore).

[Pablo J. Rogina]

@Christianvs if your issue is solved, please don't forget to mark your post as such. Thanks.

[Christianvs]

@sierdzio
Is there any downside to just calling this as parent?

@Pablo-J-Rogina
I actually cannot find where to mark it as solved
EDIT: Done! :)

[sierdzio]

@Christianvs said in Help with QTimer scope:

Is there any downside to just calling this as parent?

No. The other solution is worse, because it is easy to forget about calling delete. If you use Qt's parent-child system, then Qt will automatically delete objects when their parent is deleted.

There is a possibility that it is not the behaviour you want, but that is not something we can determine from the code above.

Other options for managing object life:

• QSharedPointer
• stl pointers