What do the yellow icons mean?

[pwabrahams]

I'm running Rockbox on a Sansa Clip+.  I've been looking in the User Manual for an explanation of the icons in the yellow display at the top of the screen but haven't been able to find one.  What do those icons mean?  And is there an explanation somewhere in the manual that I simply haven't been able to find?

[[Saint]]

No one can answer that without first knowing which theme you are using.


[St.]

[yapper]

http://download.rockbox.org/daily/manual/rockbox-sansaclipplus/rockbox-buildch4.html#x7-490004.3

[pwabrahams]

Interesting question -- how can I tell what theme I'm using?  Since I never set the theme, I got the default.  I see how to select a theme, but not how to determine which theme I have.

Section 4.3 of the manual says what information appears in the status bar:

Status bar: The Status bar shows Battery level, charger status, volume, play mode, repeat mode, shuffle mode and clock. In contrast to all other items, the status bar is always at the top of the screen.

But it doesn't indicate the actual icons associated with these items.

[[Saint]]

If you've never set it, the theme you have is called "cabbieV2" which is our default theme.

I am unsure if the manual section linked to is actually correct, as I a: Don't own the device, and b: Am pretty sure that there's an icon missing from that list (namely "Disk Access").


[St.]

[pwabrahams]

I'd suggest that the next time the manual is revised, labelled instances of all those icons be included.  Unexplained icons are all too common in the computing world, so Rockbox has plenty of company.

[Llorean]

Rockbox is a community project. A patch would be welcome if you'd like to see that change.

[bluebrother]

Section 4.3 of the manual says what information appears in the status bar:

Status bar: The Status bar shows Battery level, charger status, volume, play mode, repeat mode, shuffle mode and clock. In contrast to all other items, the status bar is always at the top of the screen.

But it doesn't indicate the actual icons associated with these items.

The icons are in the same order they are mentioned, from left to right. Is that so far-fetched?

[pwabrahams]

I'd suggest that the text be modified like this:

The Status Bar shows the battery level [battery icon], charger status [charge icon], volume [volume icon], play mode [play icon],  repeat mode [repeat icon],  shuffle mode [shuffle icon], and clock [clock icon].

For anyone not already involved in maintaining the documentation, any change, even an almost trivial one like this, is probably at least a full day's work: understanding the environment, finding the icon images, understanding the revision system and the related administrative conventions, negotiating access to the relevant files, etc.  For someone already involved and familiar with those things, I'd think the effort would be minimal.

By the way, the WPS only shows five icons but there are seven in that list.

[yapper]

By the way, the WPS only shows five icons but there are seven in that list.

Shuffle mode and Repeat mode are only shown if they are turned on.

[Llorean]

I always love the "you should do the work for me, because my logic suggests it's less work for you, and of course your time is less valuable to me than my time" reasoning for why people don't want to do the work themselves.

[pwabrahams]

I now have the answer to my question, so the improvement I suggested for the manual doesn't benefit me any more.  I haven 't done software development for quite a while, but when I did, I always welcomed suggestions, good or bad.   The good ones I used; the bad ones I simply passed over.   If my suggested change is an improvement, then the question would be, I'd think, whether the effort of implementing it is worth the benefit.  My willingness or unwillingness to do the work ought to be irrelevant.  And besides, would you want someone you don't know mucking with the code?

Suppose I offered to do the work.  Would the effort it would take to (a) verify my qualifications, and (b) verify that my code revisions were sound and had no bad side effects, be any less than the effort for someone active in the Rockbox project and its documentation to just make the change themselves?

I'm grateful to the people involved in the Rockbox project for the fine work they've done.  My suggestion was intended in a purely constructive spirit.

[Llorean]

It's open source. It's all about people we don't know mucking with the code and submitting patches. You seem to be mistaking this for a closed project.

[Chronon]

Suppose I offered to do the work.  Would the effort it would take to (a) verify my qualifications, and (b) verify that my code revisions were sound and had no bad side effects, be any less than the effort for someone active in the Rockbox project and its documentation to just make the change themselves?

Your qualifications aren't really relevant.  Any patch you submit would be reviewed and/or tested before being included in the source tree.

I'm grateful to the people involved in the Rockbox project for the fine work they've done.  My suggestion was intended in a purely constructive spirit.

I appreciate that but please don't feel that you can't contribute just because you haven't been active before now.  For those who are not familiar with LaTeX we also accept plain text submissions to the patch tracker that clearly indicate proposed changes.