- Status Closed
- Percent Complete
- Task Type Bugs
- Category User Interface → Themes
- Assigned To No-one
- Operating System Another
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#11640 - Sansa Clip+ - scrolling text displays where its not suppose to
Tested on Rockbox for Sansa Clip+ r28090-100923.
I’ve coded my theme to display the volume temporarily for 2 seconds when the volume is changed using the %mv tag. However, if there is scrolling text on the same screen, that same scrolling text will display on the same line as the temporary volume text until the volume display time has elapsed.
The problem exists on the hardware, not the sim. To recreate the problem, load the attached theme and press the volume button when the title or artist text is scrolling. You will see the same scrolling text displayed on the same line as the volume text.
I am attaching the theme in question.
thanks.
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
I cant reproduce this with r28243, it was probably fixed in the last few days.. please try the latest build
i can reproduce this with attached wps on gigeabeat x, r28268.
workaround seems to increase glyph option (3rd parameter) of %Fl tag.
I thought the bug was the scrolling line wasnt where it should be? upping the glyph number means it isnt really a bug, more user error
the title of this task is: scrolling text *displays* where its *not* suppose to.
in case of the wps i attached, (part of) the scrolling line, QKCGVJSIND…, is somehow displayed on the line %pc qkcgvjsind.
Increasing the buffer fixed this.
This was my mistake. Please accept my apologies.