QML and Qt Quick

My guess is you are stuck with using "var", if it will work.

@lemons thank you -- that seems to have solved it. I'm still learning when and where to use the various positioners. It always seems so clear after someone shows me how to do it right...

Hello Antonio, I am having the same issue. Did you find a solution? cheers, Tobias

If you only want to extend the "Text" item, why don't you use it as root item in your qml file? You don't have to wrap everything with an Item. // StaleDataModel.qml import QtQuick 2.0 // use Text als root item, so all default properties of Text will be available automatically Text { // define it somehow generic, so you can reuse the item with different settings property int fontSizeBreakPoint: 150 property int largeFontSize: 30 property int smallFontSize: 16 property color defaultColor: "#777777" color: defaultColor font.pointSize: parent.width < fontSizeBreakPoint ? largeFontSize : smallFontSize horizontalAlignment: Text.AlignRight verticalAlignment: Text.AlignTop } // SomeOther.qml StaleDataModel{ anchors.top: parent.top color: "#ff0000" text: "someText" }

Got it...property alias. Added a line to Navbar.qml: Item { id: bigPicture property alias tabIndex: navTabs.currentIndex // the new line Rectangle { id: navBar TabBar { id: navTabs ... And in main.qml: Navbar { id: navBar } Mainarea { currentIndex: navBar.tabIndex } Seems to work, but if someone knows of a better way, I'm open to suggestions. Thanks for looking...

Actually, it does seem to be working OK. Something in my StackLayout was screwing it up, so I disabled it, and am now seeing the expected color. Thanks!

@fcarney said in TabBar not displaying items other than TabButtons: I assume you are feeding the currentIndex into a stack view or something? You might have better control with a ListView. I will be. The only purpose for the tabs is to alter the contents of the main display. ListViews look like more work. I'll look into styling the TabBar.

@JoeCFD thanks for the link. I think there's something more at play here -- I've added a couple comments to the bug report you linked above, and will pursue this issue with that team. Marking this as closed. Thanks for the help.

What @JoeCFD said is what I have done to customise some built-in QML components but it depends whether everything that needs doing can be done at the QML level. For example, if extensions are needed at the underlying C++ level there is not really any support to do this. Probably you would need to copy the source of QQuickText to a new class and add the extensions to it.

@bwylegly There are many ways to do what you want. This one be too simplistic for your needs but in my experience, simplicity is beauty. I often create two or more of my screens as separate QML files (of type Item) and create an instance of all of them in the main window, with only the start-up one showing. Window { MasterView { id: masterView anchors.fill: parent visible: false } LogonScreen { id: logonScreen anchors.fill: parent } } I also like to play around with different styles, like having the logon screen be a dialog but have an opaque background so you can see the workspace behind but are unable to interact with them until you log on. This way does require the QML files to be loaded first and not dynamically as your question might allude to. Hope this helps.

@jsulm thanks you

@SiliconKiwi helps, thanks.

Work like charm thans to you @fcarney