Different skins for TBTabContainer

[swap15]

Now I can't create tab containers with different visual. Need support for skin attribute for tab container :)

[fruxo]

This should work today i think:
Give the TBTabContainer some special skin name, f.ex skin: "duck", "badger" for every new style.
Then in "TBTabContainer.rootlayout", "TBTabContainer.tablayout_x/y", "TBTabContainer.container" and "TBTabContainer.tab" you can use override (or strong-override) with a condition for ancestors with skin name "duck" or "badger" to specify the different versions. It would probably quickly get quite messy (and less efficient) if you have a lot of different visuals though.

Other possible solutions:
You can use the skin attribute under the "tabs" section (or any other attribute) and it will apply to the tabs layout. Adding the same possibility for "container" and "root" would be super simple and allow the skin attribute on those too.

A bug: I noticed TBTabLayout::OnChildAdded always override the skin for TBButton, so any attempt to set the skin attibute directly on a specific tab will currently fail.

[swap15]

Could you write a little example of skin for additional skin, please. For example I want to change background of layout and backgrounds of tab buttons.
Thank you!

[fruxo]

In your ui resource:

TBTabContainer: skin: "duck"

In your skin override (assuming you override the default skin):

TBTabContainer.tab_top
    strong-overrides
        element TBTabContainer.ducky_tab
            condition: target: ancestors, property: skin, value: duck
TBTabContainer.ducky_tab
    padding 10
    overrides
        element TBTabContainer.ducky_tab.pressed
            state pressed
TBTabContainer.ducky_tab.pressed
    padding 10
    background-color #fd0

This will add the strong-override section to the default "TBTabContainer.tab_top" skin so the TBTabContainer.ducky_tab skin will be used instead if any ancestor has skin "duck", which the TBTabContainer has.

There's some limitations for what you can change in an override skin, since they can only add to the override/strong-override/child/overlay lists (and not replace in them). So some things requires changing the base skin.

[fruxo]

The example won't look pretty, but at least it shows how conditions can be used :)

[swap15]

It working! Thank you!

[fruxo]

Great!
And now it's also possible to use the skin attribute on "content" and "root".

[swap15]

Cool! Thanks! :)