like this: http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/ktabbar.png Reproducible: Always
We're using a KTabWidget to display the tabs, this could potentially be solved by using a KTabBar instead. Unless KTabWidget is being used for a particular reason.
@Jussi I don't understand. Our text-ui looks exactly like that. What's the difference? @Rohan KTabBar/KTabWidget is the same as QTabBar/QTabWidget respectively, i.e, we use KTabBar. TabWidget just also provides the QStackedWidget underneath and connects everything.
Jussi, I am waiting for you to explain what's different. Marking as "waiting for info"
Hi, the picture actually doesn't explain as well as I hoped. Here is how to reproduce: 1. open a bunch of tabs, so that several of them are hidden to the left. 2. if you are lucky enough to have one sticking out, click it. 3. Then try to click the next tab to the left.... 4. you can't, because it doesn't stick out. So what I want is like in the picture, but to the left.
I still don't understand. Do you have a screenshot of tabs done right?
If I understand it correctly - basically never align the tab border with window border unless it's the last item (or first) and always "scroll" the tabbar so that the tabs on the edges are always partially visible, suggesting there are more tabs.
That makes sense. Jussi, can you confirm that's what you meant. If that is the case, it means deviating from the standard kdelibs tab bar. It's not easy to do, QTabBar does custom painting and event handling on the whole bar at once, basically we would need to rewrite the whole thing.
What Martin says is correct, with the additional part that those "stubs" are clickable, not just "suggesting" more.
We use the standard KDE widget for this, it's not in our interest to maintain our own tab bar, it's too much work and not our area of expertise. If you could follow this up with Qt, that would be great.