- Status Closed
- Percent Complete
- Task Type Bugs
- Category User Interface → Font/charset
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#10054 - some folders are not shown after scrolling down in a sub-directory
to reproduce:
1. go (in rockbox) to a directory with some folders in it (i had 11). you shouldnt have a scroll-line in this list of directories.
2. create a folder and make sure that it gets sorted at the end of the list (by renaming it)
3. create some folders in it ( i had 23), so that you have a scroll-line.
4. scroll down and go back to the parent directory.
you should see that only some folders, which were at the bottom of the list, are shown at the top of the screen. if you scroll up two times, everything is shown.
tested with r20511 (e200), i tested it in some previous builds and saw it also in r17500 (and some later versions).
linuxstb said in irc he didn’t understand it, but i don’t know exactly what he doesn’t understand, so if anything isn’t clear please ask . additionally i didn’t know the right category, sorry….
2009-11-01 14:41
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Should be fixed.
If not, ask to
reopen this task or create new one.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
if im understanding this right then this is a return of an old bug which we hoped was fixed :(
I think this is fixed in r23367. please check and report.