This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#6854 - Add scrolling to the credits
Attached to Project:
Rockbox
Opened by Sylvain Fourmanoit (syfou) - Monday, 19 March 2007, 09:50 GMT+2
Last edited by Peter D'Hoye (petur) - Thursday, 30 August 2007, 21:57 GMT+2
Opened by Sylvain Fourmanoit (syfou) - Monday, 19 March 2007, 09:50 GMT+2
Last edited by Peter D'Hoye (petur) - Thursday, 30 August 2007, 21:57 GMT+2
|
DetailsWith more than 280 contributors to Rockbox so far, the credits plugin takes about two minutes to list everyone -- it seems to me it could benefit from some added interactivity; this patch adds simple scrolling capabilities to the credits plugin, so that the user can browse the list of contributors back and forth. Once applied:
- The original text sliding effect is kept intact. - As with most interactive plugins, there is only one button to quit the plugin (this is model-dependant) -- pressing any button is not good enough anymore. - The model-dependent up and down buttons can be used to scroll the list, one half of the screen at a time, so that every contributor gets listed at least once. - At the end of the list, the credits plugin exits if no manual scrolling occurred, and loop otherwise. There are many other improvements that could be incorporated to make it feel better (automated scrolling in the direction of last manual scroll for instance), but this is a simple, working solution that adds the scrolling feature with little changes to current tree. |
This task depends upon
Closed by Peter D'Hoye (petur)
Thursday, 30 August 2007, 21:57 GMT+2
Reason for closing: Accepted
Additional comments about closing: maybe the navigation isn't 100% fluid but it will do for now...
Thursday, 30 August 2007, 21:57 GMT+2
Reason for closing: Accepted
Additional comments about closing: maybe the navigation isn't 100% fluid but it will do for now...
could you either generate your patch from the root of the rockbox tree or state where to execute it (option one is preferred)
one more thing, the scrolling only starts working if the screen is filled... how's that for a task ;)
As for the part about scrolling only working once the screen is filled, it is just because I did want to have minimal impact on current code... Maybe I am just overly cautious, but I didn't fully understand the justification of a few timed operations in the plugin, and I do not have access to other real devices besides the Sansa e200 target.
just move up/sown a few times and then proceed down to the bottom. Once at the end you'll get a segmentation fault (probably a div by 0). I guess the scrollin code conflicts with the moving down, causing some index to go wrong?
too bad, I was going to commit after a final check.
If you intend to work on it it's fine
I did this because I found the credit browsing I implemented before hard to use and behaving in a counter-intuitive fashion: I think this is far better for the end-user. I tested in in the uisimulator for a while, and it seems stable this time.
Right now, it duplicates the content of 'credits.raw' in the final binary -- I guess this could be changed later if this proved to be a good idea -- there is nothing preventing to merge this into the original credits plugin either.
re-opened because OP will supply new patch. The "I just don't think this code should go in anymore..." was referring to the old patch.
I am not sure I got the USB states handling right though: on the simulator, I got a few hangs (rockbox not waking up once plugged, then unplugged when credits is running) I couldn't reproduce on my sansa e280. The bug, if any, eludes me... I seems to get it both with this patch applied or not.
Also doesn't handle USB well, it gets stuck in the listview.
What was wrong with the first way of working anyway, why couldn't you just fix the bug and be done with it?
> [...] What was wrong with the first way of working anyway?
Not intuitive? It's just a regular list. I showed initial first version to two people, how were clearly struggling with it (they both got lost with the controls a couple of times): that's the reason I reused rockbox pre-written, uniform interface instead of the custom effect.
Is there anything I can do to make it better (or to convince you it's better ;-D )?
>Also doesn't handle USB well, it gets stuck in the listview.
I know: I didn't understand how signaling is supposed to work... I read rockbox code a little more yesterday, and I think I got it now. I could fix this.
> Why couldn't you just fix the bug and be done with it?
I will post this one-liner next Monday (I travel for a few days) but I sure hope you'll reconsider. Thanks for your time once again.
- the indexing problem that caused a segmentation fault in previous version (appears stable on simulator).
- another slight display glitch due to incorrect refreshing on the title line on loop.