When navigating through collections with a relatively low number of tables, the alphabetical pagination is not optimal, as the user basically moves from single table to single table like if he would use the 'single table' forward & backward buttons.
(e.g. going from A to B To C to D means going from AC/DC to Barracora to Cactus Canyon to Defender, ...) if there are only 4 tables with first letters being A, B, C and D.
It would be nice when the user could paginate in steps of 5 (this is the number of table being shown on screen at a time). Not sure though what would be a good threshold for this mode of pagination to be activated.
One option could be that when there are less than 3 or 4 tables with the same starting letter, the pagination uses a step of 5 tables, irrespective of the starting letter.
When navigating through collections with a relatively low number of tables, the alphabetical pagination is not optimal, as the user basically moves from single table to single table like if he would use the 'single table' forward & backward buttons. (e.g. going from A to B To C to D means going from AC/DC to Barracora to Cactus Canyon to Defender, ...) if there are only 4 tables with first letters being A, B, C and D. It would be nice when the user could paginate in steps of 5 (this is the number of table being shown on screen at a time). Not sure though what would be a good threshold for this mode of pagination to be activated. One option could be that when there are less than 3 or 4 tables with the same starting letter, the pagination uses a step of 5 tables, irrespective of the starting letter.