Why?

Cause

• As developer suppose QtQuickView to be able to load different component(s) (than the one that it initially loads) during its lifetime. Sometime the user passes additional import paths with loadComponent(). Each loading of additional components during the lifetime of QtQuickView instance, should also remove previous import paths from QQmlEngine.

Customer

• Customer?
• Customer with project having extra import paths in main.cpp these should be passed to QtQuickView

Cruft

• Quite a niche use case, needs two similarly named plugins

What?

Definition

• The overload of QtQuickView.loadComponent() should reset the import paths in QQmlEngine to its initial state before adding new import paths, passed by loadComponent()

Demarcation

Dependencies

• FF? 

How?

Effort - i.e  how easy or hard does it feel?

• One liner

Estimate - i.e. how big is the amount of work (in calendar time)?

Essential - i.e the add on value it brings? High

When?

Flex i.e. time-bound (like platform or feature freeze) or not is it?

• New API, so bound to FF (in Qt 6.11 early December)

Force i.e. labor (do we have enough people working on it) capacity?

Fit i.e. does it fit in (like Qt release)?

• Qt 6.11?