Re: [Interest] How to fix qml unqualified access warning for setContextProperty

2024-10-24 Thread ekke
Am 24.10.24 um 12:11 schrieb Nuno Santos via Interest: Federico, Thanks for your reply. I will investigate. yep - setContextProperty is outdated see HowTo switch to QML_SINGLETON: https://t1p.de/ekkeQML_SINGLETON ciao ekke Best regards, Nuno On 24 Oct 2024, at 11:08, Federico Ferri

Re: [Interest] How to fix qml unqualified access warning for setContextProperty

2024-10-24 Thread Nuno Santos via Interest
Federico, Thanks for your reply. I will investigate. Best regards, Nuno > On 24 Oct 2024, at 11:08, Federico Ferri wrote: > > Have you considered the option of making your "controller" object a QML > Singleton? That should help with type checking. > > On Thu, 24 Oct 2024 at 12:06, Nuno San

Re: [Interest] How to fix qml unqualified access warning for setContextProperty

2024-10-24 Thread Federico Ferri
Have you considered the option of making your "controller" object a QML Singleton? That should help with type checking. On Thu, 24 Oct 2024 at 12:06, Nuno Santos via Interest < interest@qt-project.org> wrote: > Hi, > > In my applications I usually register a main controller for the whole > applic

[Interest] How to fix qml unqualified access warning for setContextProperty

2024-10-24 Thread Nuno Santos via Interest
Hi, In my applications I usually register a main controller for the whole application right at startup: QQmlApplicationEngine* engine = new QQmlApplicationEngine(); engine->rootContext()->setContextProperty("controller", controller); However, with the most recent QtCreator I have the following