If the number ( or size ) of all tab-handles in a tabbed pane exceeds the window size ( for example after resizing the window ) it could happen, that the tab-handles are displayed in a couple of lines of handles. It would be a better solution to provide a kind of scroll bar, which allows the user to have visible only the tabs/tab-handles needed at the moment. Note that I do not think about simply adding a JTabbedPane to a JScrollPane. A disirable solution would be a 'combined' control of JTabbedPane and JScrollPane ( some solutions already exist there on the market).

N/A

[aim 3/17/98]
This is a valid feature request as the multi-run tabs can be very
annoying to endusers (especially the UIs where the runs rotate around
so the selected tab is on the run closest to the content pane).

Don't do this, it's a really bad idea! Yes,
multi-run tabs are annoying, but not showing
all the options is even worse than moving them
about when you select them (as Windows does).
If you have so many tabs that you need multiple
rows or a scrollbar, you've gone wrong already
and should think about a different interface.

I disagree.  Sometimes you need a bunch of tabs.
Yes, it really shouldn't be done, but my app is
a foundation for others to use, and it's not for
me to tell them how to build their screens.
Having some random number of tab rows is very ugly,
and is really troublesome for making sure things
are of a certain size.

Is this still being considered for a future release?  I have some clients
(LARGE company) who would really like this functionality.  Anyone have a
workaround?

I have a component called TabSplitter 
(http://javadude.com/tools/tabsplitter) that uses a single 
run, but solves the potential scrolling problem easily:

Automatically add a popup-menu to the tabs -- the menu 
contains a list of all tabs so you can select the 
appropriate tab directly.

In any case, IMHO the single/multi-row should be an option 
so that programmers have a choice (and nice programmers 
will use a single row ;)

ALSO: In TabSplitter, I provide a +/- button like the 
notebook control in OS/2 -- they move you between panels, 
scrolling the tabs as needed. This way you can see panels 
and move at the same time.

it is very rare case, when the user will like to see only some 
of the tabs. Any way those users can also be not ignored. It 
is better if this is an optional part. In other word, if the user 
want that can change it dynamically in any application using 
swing components whether she/he like to see all the tabs or 
scrolled tabs