Best choice for you is define the Q_ENUM in C++ and expose the enumeration to QML. Use those enumeration. It should work as is.

@J.Hilk said in Property Alias and runtime loaded QML-Items: I'm however not sure what you mean with parameters dictionary. Oh sorry, wrong word :-) I've meant this from the link I provided: properties: a list of QML properties that should be assigned to the item upon push. These properties will be copied into the item when it is loaded (in case of a component or URL), or when it becomes the current item for the first time (normally upon push). Another possibility would be to use some global context property (added in C++) which your whole app can access. Then you don't need to worry about when and how elements are loaded. In this case, not jet. But I thought, If I'm basically learning a "new language" than I better avoid adopting bad habits, if I can. It is not necessarily a bad habit. It is a trade-off: you load all QML code at application startup - startup is longer (slightly - parsing QML is extremely fast), then all works fast at runtime (or possibly it instantiates components on push(). It definitely does that if you encapsulate ObjX in Component, I'm not sure if it also applies to the way you've done it) or you load by Loader / URL at runtime - startup is faster, but then you will need some time to load the QML file at runtime when user wants to access given stack page

ok. Let us look at like this. Instead of web view, put the Rectangle{} Try to show & hide the rectangle instead of web-view. Till me whether it works or not. Try something like this OffLine_Pages.qml Pane{ id: view property string local_url : "" property string pid : "" property alias vis: web.visible Rectangle{ id : web width: 200;height: 200;color: "red" visible: false } }

Hi, id is not a property but an attribute. See here Out of curiosity, why do you want to alias it ?

@marcosbontempo That's fine.. It happens all the time :)

Ahh, sure! Thanks :-) Didn't thought it was that easy ;-)