Closed NikkSaan closed 5 years ago
Can you post a Short, Self Contained, Correct Example that demonstrates the issue? Also, in Qt when calling signals, AFAIR it just "emits" the signal, so you have to connect something to the signal for it to work. In QML, see this: http://doc.qt.io/qt-5/qtqml-syntax-signals.html#connecting-signals-to-methods-and-signals
I'm running "test.qml" in a slightly modified "qmlscene"-kind of a program, more suited for my embedded platform. But the program just adds Pyotherside's import path to the QML Engine, and sets some QPA parameters. Also, Pyotherside is compiled against musl-libc.
Here is the test I ran, I can't make it more self-contained than that. I also tried using the "onCallSignal" handler, it still wouldn't work.
Result : https://pastebin.com/B3kBKgat
I'll assume it's a problem with my setup, and do without calling signals. I want to continue working on my project. I really just wanted to know If calling a signal was supported.
Sorry, I have to use Pastebin.
Thanks for that, the QMetaMethod::invoke()
failed on the signal, because we tried to do a direct connection, and that apparently doesn't work with signals. As signals don't have any return value, instead we use Qt::AutoConnection
for signals now, and only return true or false depending on whether it worked or now.
Wow, you're welcome! I didn't expect that this would result in a bug fix, and so quickly. Thank you!!!
Calling a regular method works, calling a signal doesn't. It prints: RuntimeError: QObject method call failed
Is this normal?