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:

Rockbox Ports are now being developed for various digital audio players!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  User Interface and Voice
| | |-+  Gigabeat - Button mapping standard?
« previous next »
  • Print
Pages: [1]

Author Topic: Gigabeat - Button mapping standard?  (Read 2372 times)

Offline Firestorm ZERO

  • Member
  • *
  • Posts: 3
    • ZERO-TYPE
Gigabeat - Button mapping standard?
« on: July 11, 2008, 01:21:06 PM »
I recently upgraded from iRiver H120 to a Gigabeat F40. And just went through most of the plugins to check them out.

The one thing I noticed is that there is various different mappings. Like to quit a plugin, I see it either POWER, MENU or A (strange way to quit IMO).

The usual mapping I noticed is POWER to quit immediately (or quit+save immediately), MENU to provide a settings/options and the other buttons to provide plugin control (volume +/-, A, SELECT).

With the iRiver I never noticed this because all I play is Sudoku :P.

Just wondering is there a standard in the mapping? As I plan to eventually learn how to make a plugin.
Logged

Offline Chronon

  • Rockbox Expert
  • Member
  • *
  • Posts: 4379
Re: Gigabeat - Button mapping standard?
« Reply #1 on: July 11, 2008, 02:27:14 PM »
You are correct that there's not much of a standard for plugins at the moment.  I think from a usability standpoint this would be a good thing to strive for wherever possible.  Though, some plugins may want to reserve certain keys for special purposes. 
Logged
Sansa e280, Gigabeat F40, Gigabeat S60, Sansa Clip+, iPod Mini 2g

Offline roolku

  • Developer
  • Member
  • *
  • Posts: 350
Re: Gigabeat - Button mapping standard?
« Reply #2 on: July 11, 2008, 02:32:23 PM »
Using A to quit is a leftover from the global POWER-A switch. I thought I had weeded them out, but it seems there are still some left. If you want to make a list, it might motivate me to do the rest. ;)

As for menu/power: Apparently it is not possible for all targets (lack of buttons) to have a dedicated, consistent quit button so it was combined with the menu (even for the targets that have enough, which I personally find very annoying and have changed in my local build for some plugins that I often use ). Not all plugins have been changed though, hence the inconsistency.
Logged

Offline Chronon

  • Rockbox Expert
  • Member
  • *
  • Posts: 4379
Re: Gigabeat - Button mapping standard?
« Reply #3 on: July 11, 2008, 02:46:33 PM »
Thanks for the info, roolku.   :)
Logged
Sansa e280, Gigabeat F40, Gigabeat S60, Sansa Clip+, iPod Mini 2g

Offline Firestorm ZERO

  • Member
  • *
  • Posts: 3
    • ZERO-TYPE
Re: Gigabeat - Button mapping standard?
« Reply #4 on: July 18, 2008, 04:33:51 PM »
Send you a PM roolku
Logged

Offline roolku

  • Developer
  • Member
  • *
  • Posts: 350
Re: Gigabeat - Button mapping standard?
« Reply #5 on: July 20, 2008, 06:19:18 AM »
fixed now - I left fireworks alone, as it is like that for other targets as well
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  User Interface and Voice
| | |-+  Gigabeat - Button mapping standard?
 

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

Page created in 0.074 seconds with 15 queries.