Suggest "max tab number per row" instead of "

Archived discussion about features (predating the use of Bugzilla as a bug and feature tracker)

Moderator: Moderators

cyberal
Posts: 360
Joined: 2003-05-16 10:42

Post by cyberal » 2003-10-03 10:12

just set max tabrows to 1 and the tab won't jump anywhere..
http://whyrar.omfg.se - Guide to RAR and DC behaviour!
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet

Gratch06
Posts: 141
Joined: 2003-05-25 06:48
Location: USA

Post by Gratch06 » 2003-10-03 14:27

I would personally like this as well. I was extremely happy when DC++ went to multiple tab rows, but this one problem of it jumping up and down does get on my nerves. I try to usually keep the number of tabs down to one row, simply because I like having more screen space, but I would much rather SEE the one item or two items on the second line than have them hidden away on the >> arrow (sorry cyberal). The problem appears when enough windows are bolded that there isn't room for the full final tab. When it jumps up, it doesn't adjust the text positioning in the mainchat or PM window, so you have to go up and manually adjust it so that the scrollbar is at the bottom again, rather than chopping off the last one or two lines.

Example from last night: I had a PM window open with a user that, when with no tabs bolded, was just short of breaking onto the new tab row. When any tab on the first row became bolded, it would bump the tab to the second row. Basically a really annoying yoyo.

Two solutions as I see it:
1. implement fenxiang's method of max tabs per row, but in addition to max tab rows.
2. shift back to the method taken when there was only one row of tabs: make the last tab only partially visible.

-Gratch06

Who is online

Users browsing this forum: Google [Bot] and 0 guests