[Feature Request] Keep minimum tab width in horizontal mode

[squirrel-bat]

Issue:

Currently, when using the tab style text or text and icon with tab layout set to horizontal, the tab bar will only ever start being scrollable when all tabs are shrunk to their minium width.
It looks like this is currently defined to be the width of an icon, but applies to all modes.
In extreme cases, this leads to a tab bar with only single letters (and sometimes even worse: Not even a letter) when using tab style text:

Feature Request:

Set the minimum width for tabs based on their children so they don't get cropped, so the tab bar behaves the same as in icon mode:

[PiCode9560]

So you want the tab to just show the full text?

The reason that it was cropped is so that you can see as many tabs as possible. It doesn't really work too well. But it might be better to just remove the cropping and just show the full text. Maybe if people want to see more tabs, they can just use the icon mode. What do you think?

[squirrel-bat]

So you want the tab to just show the full text?

Yupp! :)

The reason that it was cropped is so that you can see as many tabs as possible. It doesn't really work too well. But it might be better to just remove the cropping and just show the full text. Maybe if people want to see more tabs, they can just use the icon mode. What do you think?

Hm, I think making the current behaviour optional, calling it something like "Crop Tab Text", would make sense, so users can choose to have it either crop or force the tab bar into scrolling.

[PiCode9560]

I think we should just remove the clip text functionality because it doesn't work too well. Ideally, would be nice if tabbar have its own clip text functionality godotengine/godot-proposals#13004

[squirrel-bat]

I think we should just remove the clip text functionality because it doesn't work too well. Ideally, would be nice if tabbar have its own clip text functionality godotengine/godot-proposals#13004

I wonder: Should I close this issue, as this is basically a WONTFIX and we're waiting for your proposal to gain traction instead?

[PiCode9560]

I guess we can just leave this open to show that this is an issue that this plugin has, even tho it will probably not be fixed anytime soon.

[rethyria]

Personally, I'm not a fan of scrolling tab bars in the first place so multi-row tabs would be preferable imo (paired with the full text always being displayed on each tab).

As an aside, I've only just downloaded the add-on and it's really great, thank you for making it!

[PiCode9560]

I feel like we should just ditch the built-in tab bar, and make our own tab bar. So that we can make it have a better vertical tab, and also clip text and multi-row tabs.

[rethyria]

I was playing around with it last night and split the classes and categories into two separate tab bars. It's not perfectly functional and I didn't bother to make it work with the vertical bar or jump scroll - there are probably a ton of edges cases that break it too haha - but as an idea I think it works pretty well.

[squirrel-bat]

I was playing around with it last night and split the classes and categories into two separate tab bars. It's not perfectly functional and I didn't bother to make it work with the vertical bar or jump scroll - there are probably a ton of edges cases that break it too haha - but as an idea I think it works pretty well.

Interesting, I understood your proposal as "simple" multiline tabs, meaning they're just breaking lines whenever they become too many to show in one. Some might like that behaviour, so having it as an option would be nice, I think.

Looking at your mockup now, I think this is an interesting addition, as it's basically doing the same thing the plugin already does, but twice, by nesting the navigation of the properties one additional layer.
I'm not so sure about the trade-off between amount of clicks and navigation needed to get to the property you want VS the additional layer of organization with the tabs, but that can be up to each user to decide if that new feature will be optional, like the rest of the plugin.

[rethyria]

I was playing around with it last night and split the classes and categories into two separate tab bars. It's not perfectly functional and I didn't bother to make it work with the vertical bar or jump scroll - there are probably a ton of edges cases that break it too haha - but as an idea I think it works pretty well.

Interesting, I understood your proposal as "simple" multiline tabs, meaning they're just breaking lines whenever they become too many to show in one. Some might like that behaviour, so having it as an option would be nice, I think.

Looking at your mockup now, I think this is an interesting addition, as it's basically doing the same thing the plugin already does, but twice, by nesting the navigation of the properties one additional layer. I'm not so sure about the trade-off between amount of clicks and navigation needed to get to the property you want VS the additional layer of organization with the tabs, but that can be up to each user to decide if that new feature will be optional, like the rest of the plugin.

The original proposal was "simple" multiline tabs, but creating a new tab bar to support that was a little too much effort for a night of tinkering, so I had the idea of splitting the two.

You can't see it in the images as Node doesn't have any categories but if you have both "All" tabs selected, it should show every category tab in the bottom bar. Which introduces the same clipping issue, so the multiline tabs are still relevant in any case.

[PiCode9560]

Working on a custom TabBar...

InspectorTabsFlow.mp4