If this is a direct copy of your code there is a few typos..
id name needs to be id:name.
Also you cannot link your customrowlayout alias to the item reference which is outside your custom component..
"Unlike an ordinary property, an alias has the following restrictions:
It can only refer to an object, or the property of an object, that is within the scope of the type within which the alias is declared.
It cannot refer to objects declared outside of the scope of its type.
The alias reference is not optional, unlike the optional default value for an ordinary property; the alias reference must be provided when the alias is first declared.
It cannot refer to attached properties.
It cannot refer to properties inside a hierarchy with depth 3 or greater. "
Indeed it works !
I did 2 mistakes, I forgot ".item" after currentItem and I didn't changed currentIndex when I switch between pages because I use positionViewAtIndex. But positionViewAtIndex don't change currentIndex of the listView.
On QT part, we followed a lot of techniques mentioned in that post. Using Loaders for lazy loading, optimizing images, using qtquickcompiler. The major challenge is on the OS boot time that we are working on.
Just by loading one page and coming back, we can't make out the memory leak. Try multiple times like this. If you see a increase & no decrease then we can conclude memory leak. If you can send me the complete example, we can try as well.
I appreciate your response, it lead me to a lot of research on the topic! I figured out it was much easier to implement a tabview on the main view and then to connect the signals with the child objects which were themselves individual views.