You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I originally used Qt5.9.6 LTS and updated the version to QT5.12.6LTS this year.
But it's embarrassing that QuickFlux doesn't seem to emit a signal. I've been using it well in version 5.9.
I don't know why. I can't show the detail code, but I will show you how the flow works
Appaction.qml
import qtquick 2.0
import quickflux 1.0
ActionCreator {
.....
......
....
signal a()
}
test1.qml
...
....
.....
function test()
{
Appaction.a();
}
Middleware {
....
.......
.....
function a() {
console.log("HERE") //No log is taken.
}
}
I want to be logged. However, the log which was removed in the previous 5.9.6 version is not recorded after updating to 5.12.6. That is, no signal is emitted.
I searched like this, because there is nothing to search.
I'm Korean and I use Google Translate. I would be very grateful if you understood the wrong English.
The text was updated successfully, but these errors were encountered:
Hello
I originally used Qt5.9.6 LTS and updated the version to QT5.12.6LTS this year.
But it's embarrassing that QuickFlux doesn't seem to emit a signal. I've been using it well in version 5.9.
I don't know why. I can't show the detail code, but I will show you how the flow works
Appaction.qml
import qtquick 2.0
import quickflux 1.0
ActionCreator {
.....
......
....
signal a()
}
test1.qml
...
....
.....
function test()
{
Appaction.a();
}
networkmiddleware.qml
import qtquick 2.0
import quickflux 1.1
import QtQuick.Dialogs 1.2
Middleware {
....
.......
.....
function a() {
console.log("HERE") //No log is taken.
}
}
I want to be logged. However, the log which was removed in the previous 5.9.6 version is not recorded after updating to 5.12.6. That is, no signal is emitted.
I searched like this, because there is nothing to search.
I'm Korean and I use Google Translate. I would be very grateful if you understood the wrong English.
The text was updated successfully, but these errors were encountered: