Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Thank You for your continued support and contributions!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  User Interface and Voice
| | |-+  changes to the Gigabeat button mappings

Poll

How would you like the buttons to be mapped?

other (don't choose this if you just want SELECT and A to be changed in the WPS)
3 (15%)
as they are now
15 (75%)
as they were before but A to shutdown
1 (5%)
other (don't choose this if you just want SELECT and A to be changed in the WPS)
1 (5%)

Total Members Voted: 20

« previous next »
  • Print
Pages: 1 [2]

Author Topic: changes to the Gigabeat button mappings  (Read 9891 times)

Offline AlexP

  • Global Moderator
  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: changes to the Gigabeat button mappings
« Reply #15 on: May 15, 2007, 10:09:09 AM »
I completely agree with Llorean.  In the past I argued for swapping power and select in the WPS to make it consistent between screens.  I'm not bothered which button is labelled what (i.e. say button 1 is play on iRiver and A on gigabeat, button 2 is A/B on iRiver and menu on gigabeat etc.), I just think that the usage of button 1 (and button 2 ...) should be consistent.

Now that power and A have essentially been swapped, select and A should be swapped in the WPS to have consistency between what each button does across different screens in rockbox.
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

Offline markun

  • Developer
  • Member
  • *
  • Posts: 462
Re: changes to the Gigabeat button mappings
« Reply #16 on: May 15, 2007, 10:39:51 AM »
The Archos Player (didn't check the other targets) has 1 button (the "on" button) to go from the WPS to the file browser and from the file browser back to the WPS. Should that be changed as well to make it more consistent with the rest?
Logged

Offline bascule

  • Rockbox Expert
  • Member
  • *
  • Posts: 1298
Re: changes to the Gigabeat button mappings
« Reply #17 on: May 15, 2007, 10:40:36 AM »
Llorean, I absolutely agree with your proposal. If my gigabeat was like my iriver, using the centre cross (joystick press on H1x0) to access the browser, I would get my fingers much less in a twist. The A button is just too low down for one-handed use.

Quote from: Llorean on May 15, 2007, 08:54:25 AM
...Getting back to the WPS is slightly harder (Hold left, then tap left once, then choose the Now Playing entry) than a single button press...

But wouldn't the A button (play/pause) take you back to the WPS as per other targets?
Logged
DataBase fanboy and author of the totally overhauled Rockbox Sync Tool

Offline Llorean

  • Member
  • *
  • Posts: 12931
Re: changes to the Gigabeat button mappings
« Reply #18 on: May 15, 2007, 10:51:20 AM »
Yeah, I personally have this general opinion on button maps:

1) Rockbox shouldn't ever go out of its way to match the other software beyond acknowledging that buttons are labelled, such as "Play", "Stop", "Menu", etc.

2) Rockbox should attempt, where the number of buttons permits, to respect Rockbox's own button mappings on other platforms, so that for example the button labelled "Menu" does the same thing on the same screen independent of which hardware you're holding. This way someone who's used Rockbox before can pick up a new target, and other than the positioning of the buttons, know what they'll do in any given screen once they've learned which button is which for any one screen.

That's my personal philosophy on pretty much the whole matter. :)
Logged

Offline AlexP

  • Global Moderator
  • Member
  • *
  • Posts: 3688
  • ex-BigBambi
Re: changes to the Gigabeat button mappings
« Reply #19 on: May 15, 2007, 11:29:29 AM »
Llorean has just put what I was trying to say much better.  I agree with him!
Logged
H140, F60, S120, e260, c240, Clip, Fuze v2, Connect, MP170, Meizu M3, Nano 1G, Android

Offline ilikedirt

  • Member
  • *
  • Posts: 30
Re: changes to the Gigabeat button mappings
« Reply #20 on: May 15, 2007, 05:33:31 PM »
I'm mostly interested in a as-good-as-possible one handed operation. So I'm all for iriver like navigation (select takes to browser).
Logged

Offline Llorean

  • Member
  • *
  • Posts: 12931
Re: changes to the Gigabeat button mappings
« Reply #21 on: May 16, 2007, 02:51:33 AM »
Yes, the A button would take you back to the WPS, I was just talking about within the context of one-handed, I think going to the "Now Playing" menu entry is slightly easier than hitting the A button (unless you're left handed like me).
Logged

Offline lights0ut

  • Artist
  • Member
  • *
  • Posts: 382
Re: changes to the Gigabeat button mappings
« Reply #22 on: May 19, 2007, 06:04:50 PM »
I wouldn't mind the switch of A and centre tap for going to the file browser.

I was thinking about the paged scrolling with the vol +/- buttons, I know paged scrolling is achieved by holding A, but it would be quite nice to use the vol. buttons because it would be quicker, and I now agree that the loss of the ability to change volume in the menu is not that big a deal.
Logged

  • Print
Pages: 1 [2]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  User Interface and Voice
| | |-+  changes to the Gigabeat button mappings
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.09 seconds with 19 queries.