Ordering of tabbed panes is not intuitive when tabs must be shown on a more than one row
The tab layout policy currently used makes that when there is too many tabs to be displayed on a single row the next tabs are shown on top of the first ones. Therefore it looks like the top ones are the first ones, which is confusing (see image below).
Activity
mentioned in commit 37309001
Fixed.
All tabbed panes now are set with the SCROLL_TAB_LAYOUT so that tabs are on displayed on a sincle row with arrows to show the non visible tabs. This is the way most tabbed panes work in applications like web browsers for example.
All tabbed panes are created at a single place in the code (GraphicLib.createTabbedPane()) in order to ease maintenance.
- Code cleanup of the impacted java files.
From Ludovic: lorsque l'on charge un modèle avec bcp de tabs, le dernier tab est bien sélectionné, mais le haut du tab n'est poas visible, i.e. il faut cliquer sur les petites flèches en haut que tu as ajoutées pour se déplacer au bon endroit
This is fixed by Issue #62 (closed).
Edited by Dominique Blouinmentioned in commit 639c1377
