How can I get the application QmlEngine ?

kmarconi

What I do actually is passing a reference of the engine into my class of translation. But since I never create an engine, could it be the reason why it is not working ?

what's this supposed to be actually ?
qobject_cast<QQmlApplicationEngine*>(qmlEngine(this));

This is one of the way I found to get the engine.
The problem here I think is that in each example I see which are restranlating their apps, they are using only one cpp file and one qml file so they just simply create an engine in the main and load the qml in it. But for me, it's not possible because I have a lot of classes and since one of them is already using my "main.qml" file (its a class heriting from QQuickView which use the qml file with the function "SetSource"), I canno't create another engine to load the qml file because it is making my app crash. I'm pretty sure that what I just wrote is not clear so don't hesitate don't ask me whatever you want.

EDIT: If I try to qDebug my engine, I see : QObject(0x0) which means that my problem is with my way to get the engine.

Thanks for your quick answer !

J.Hilk

@kmarconi
true, I don't quite get it, do you have multiple QQmlEngines inside your Project ?

kmarconi

@J-Hilk Nop, sorry. I have for the moment none QQmlEngines inside my project. To display my app, I have a class heriting from QQuickView which is using OpenGL to display my app via the function myView.SetSources("qrc:/main.qml"). After some googling, every example I found for dynamic translation are done in three steps : remove the actual QTranslator, install the new one and then retranslate the app. But in each of these examples, they are doing this line : engine->load(QUrl("qrc:/main.qml")) at first. If i do this line, my app is immediatly crashing because the qml file is already in use in the class which display the app. Let's say this class's name is "myView", I also tried to get the engine by doing : QQmlEngine* engine = QQmlEngine::contextForObject(&myView)->engine(); but my app is directly crashing.

J.Hilk

@kmarconi ok I get it,

QQuickView has a getter for the internal QQmlEngine
https://doc.qt.io/qt-5/qquickview.html#engine

call that and simply call retranslate on that returned object, and you should be fine

kmarconi

@J-Hilk Wow I think you saved my life here, thanks ^^ My app is finally not crashing anymore but I have now an error from my main.qml file : QML StackView: Binding loop detected for property "button". Any idea on why this could happen ?

Big thanks.

J.Hilk

@kmarconi hard to tell without knowing your qml file content,

retranslate does not only reevaluate your text bindings, but all bindings
https://doc.qt.io/qt-5/qqmlengine.html#retranslate

Note: Due to a limitation in the implementation, this function refreshes all the engine's bindings, not only those that use strings marked for translation. This may be optimized in a future release.

so, the bug is probably there from the binging :D

kmarconi

Here is my main.qml file :

Item {
id:root
visible: true
width: 640
height: 480

property var mainMenu: Menu{rootStack: root}

StackView {
    anchors.fill: parent
    id: menuStack

    property var button: hmiclass.button
    initialItem: mainMenu

    onButtonChanged: {
        mainMenu.onButtonPushed(button)
    }
}

}

EDIT: I need to find where that loop is coming from.. Or to find a patch to refresh only the bindings which are in the translation file.

kmarconi

@kmarconi Last question : When I check the definition of the retranslate function, it says : Refreshes all binding expressions that use strings marked for translation. What is that "marked" thing and how to apply it ? Thanks

J.Hilk

@kmarconi
take a look here:
https://doc.qt.io/qt-5/qtquick-internationalization.html

kmarconi

@J-Hilk Yeah I already been there but every string which needs to be translated are already marked as qsTr so ...

J.Hilk

@kmarconi said in How can I get the application QmlEngine ?:

Yeah I already been there but every string which needs to be translated are already marked as qsTr so ...

so, you answered your own question

Refreshes all binding expressions that use strings marked for translation. What is that "marked" thing and how to apply it ? Thanks

😉

kmarconi

@J-Hilk Yeah but I thought that maybe there was another thing to do ... I'm stuck now so I'm trying everything I can Haha

KroMignon

@kmarconi said in How can I get the application QmlEngine ?:

Yeah I already been there but every string which needs to be translated are already marked as qsTr so ...

My way to ensure translation is the define a global Object which handle language changes.
This object is exposed to QML with engine->rootContext()->setContextProperty("translation", &myLocalesHandler).

This object has a property called emptyString:

    Q_PROPERTY(QString emptyString     READ emptyString     NOTIFY languageChanged)
....
    QString emptyString() const
    {
        return QString();
    }

On language change signal languageChanged() is emitted and in QML I have something like this:

Label {
    text: qsTr("This is a message") + translation.emptyString
}

Works great for me, hope this could also helps you.

fcarney

When I have objects that live in qml space such as a plain QObject, I will make it based upon QQuickItem in order to get the qml engine. I often do this for image providers that provide QImages to qml. I think any QQuick based object should be able to do this.

kmarconi

@KroMignon Thanks for your help, will try it now. I just have question on your translation class. Where do you emit the signal languageChanged and how do you link it to your function which retranslate the app with the engine ? Thanks !

J.Hilk

@kmarconi what @KroMignon described was the way you had to go before Qt 5.10

you can take a look at this blog post, I think its rather good:

https://retifrav.github.io/blog/2017/01/04/translating-qml-app/

kmarconi

@J-Hilk Yeah I've seen this post but it's kinda dirty way to retranslate the whole app I think ... I still will try it but I hope to find a way to use the retranslate function properly.

J.Hilk

@kmarconi
what would you consider a proper retranslate functionality ?

You can either,

call retranslate() on the QQmlEngine,
update the strings via the empty string property workaround
reload the qml file entirely

there are not other ways, at least that I know of

kmarconi

@J-Hilk Calling retranslate for me is the cleanest way. No need to add "+trans.emptyString" on each of my qsTr object and I have a lot. I need to figure out how to solve this infinite binding loop. Is reloading the whole qml a heavy task for the system ?

KroMignon

@kmarconi said in How can I get the application QmlEngine ?:

I still will try it but I hope to find a way to use the retranslate function properly.

I can not figure out what your problem is.
@J-Hilk have give you all information you need to do it.

If you are using Qt 5.10 and upper (which is not my case) simply follow documentation
That's not so complicated to follow, you could create a class which handle the locales, for example let it call LocalHandler, when you have install the new translator with QCoreApplication::installTranslator() then emit a signal for example called translationUpated().
Then in your main.cpp:

LocalHandler loc;

QObject::connect(&loc, &LocalHandler::translationUpated, engine, &QQmlEngine::retranslate);

Alternatively you can use a app->installEventFilter() to catch QEvent::LanguageChange and then trigger QQmlEngine::retranslate().

For prior version, you have to do more work ==> https://retifrav.github.io/blog/2017/01/04/translating-qml-app/