On 09/01/2024 10:49, Ulf Hermann via Development wrote:
So, to clarify this some more ... If:1. you use_multiple_ QML engines in the same process at the same time, 2. you have_different_ import paths, plugin paths, URL interceptors or network access managers for those engines, 3. you rely on those engines to produce_different results_ for the _same QML documents_ as a consequence, 4. this actually_works_, please let me know more about your use case!
I don't think it's a "use case" in the sense of "deliberate design choice", but more something that can naturally happen in big projects. In a big application one may have several libraries/plugins/modules/..., which have been developed independently.
These different parts may instantiate multiple QML engines -- maybe with the precise idea of being isolated from one another, setting their own import path, whatever; or maybe simply because they want to be self-contained so they instantiate what they need.
In such a setup, it wouldn't surprise me too much if two of such libraries have a name clash of some sorts.
My 2 c, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - Trusted Software Excellence
smime.p7s
Description: S/MIME Cryptographic Signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
