Support and General Use > User Interface and Voice

Gigabeat - Button mapping standard?

(1/2) > >>

Firestorm ZERO:
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.

Chronon:
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. 

roolku:
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.

Chronon:
Thanks for the info, roolku.   :)

Firestorm ZERO:
Send you a PM roolku

Navigation

[0] Message Index

[#] Next page