Thanks @raven-worx and @Chris-Kawa for the quick answers.
@raven-worx said in Qt5 & invokeMethod:
the 2 methods behave the same.
I know that they seem to behave in the same way.
But creating an timer object, running & processing the timer/timeout and deleteing the object afterwards, feels like it should be more work than queing a function call via Q_Object-Macro-Magic. However the compiler may break it down to the same thing, after all.
@raven-worx said in Qt5 & invokeMethod:
You can check the return value of invokeMethod() and add an assertion.
That is actually a good idea, that way one would always get an immediate notification when the call becomes invalid due to changes made.
Still inconvenient, but much less so.
@Chris-Kawa said in Qt5 & invokeMethod:
In Qt 5.10 (currently in alpha) there's gonna be an overload taking pointer to function, so you'll be able to do:
YES, thanks for the info, I was not aware of that change.
Now I'm hyped for Qt 5.10 more so than previously!
With that said, I would consider my question answered.
Thanks everyone.