2006-12-06, 05:58
The problem with that is that the viewport is there for a reason: It's there for when we are scrolling (we want it to chop things off nicely).
While it would be fine for left/right (as they are not the issue in a vertical grouplist) any vertical border could be rather strange looking, with half-controls visible, or some parts showing up when scrolling but then disappearing when the scrolling ends.
For the panel, for instance, if you had no space between thumbs, and no label whatsoever, and then have the focused thumb larger (overlapping) then if you had a border, it would show the focused thumb fine no matter where you are, but if you scroll down (so icons all move up) the first row of icons would be displayed in the border area until the scroll completes, whereby they'd magically disappear. A starting offset or something would be the only way around that (so that partial thumbs are always displayed in the top/bottom border area). This makes things more complicated both code-wise and skin-wise. Ofcourse, if it's unavoidable, then so be it. The current stuff is quite elegant in it's simplicity - I don't want it to become another buttonscroller!
If any other ideas are coming I'd be more than happy to hear them!
Cheers
Jonathan
While it would be fine for left/right (as they are not the issue in a vertical grouplist) any vertical border could be rather strange looking, with half-controls visible, or some parts showing up when scrolling but then disappearing when the scrolling ends.
For the panel, for instance, if you had no space between thumbs, and no label whatsoever, and then have the focused thumb larger (overlapping) then if you had a border, it would show the focused thumb fine no matter where you are, but if you scroll down (so icons all move up) the first row of icons would be displayed in the border area until the scroll completes, whereby they'd magically disappear. A starting offset or something would be the only way around that (so that partial thumbs are always displayed in the top/bottom border area). This makes things more complicated both code-wise and skin-wise. Ofcourse, if it's unavoidable, then so be it. The current stuff is quite elegant in it's simplicity - I don't want it to become another buttonscroller!
If any other ideas are coming I'd be more than happy to hear them!
Cheers
Jonathan
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.
