d get tons of questions about it anyway.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of pondlife
Sent: Saturday, June 09, 2007 15:47
To: rockbox-dev@cool.haxx.se
Subject: Re: Configurable buttons; was: Re: button changes from devcon,
someone play evil dic
> As it's is necessary to compile Rockbox the feature would be for advanced
> users only (less questions on the mailing list).
If you are going to compile Rockbox, you can already edit the source
keymappings ;-)
--
Steve B
B. Keroack wrote:
> On Fri, 2007-06-08 at 10:33 +0300, Tapio Kelloniemi wrote:
> > MENU+UP = ...
> > ERROR: Invalid key combination, see Manual for details.
>
> If the hardware doesn't support the combination, there's no way to
> trigger an error message.
I understood the feature as a kind of keyma
On Fri, Jun 08, 2007 at 07:42:37AM -0400, B. Keroack wrote:
> On Fri, 2007-06-08 at 10:33 +0300, Tapio Kelloniemi wrote:
>
> > MENU+UP = ...
> > ERROR: Invalid key combination, see Manual for details.
>
> If the hardware doesn't support the combination, there's no way to
> trigger an error
On Fri, 2007-06-08 at 10:33 +0300, Tapio Kelloniemi wrote:
> MENU+UP = ...
> ERROR: Invalid key combination, see Manual for details.
If the hardware doesn't support the combination, there's no way to
trigger an error message.
On Thu, Jun 07, 2007 at 11:59:20PM +0200, Linus Nielsen Feltzing wrote:
> The file format is not the problem. The implementation in the Rockbox
> code is. And handling all the support questions from users who don't
> know how to use this feature.
>
> The most difficult problem is that not a
Tapio Kelloniemi wrote:
A file could look like this:
The file format is not the problem. The implementation in the Rockbox
code is. And handling all the support questions from users who don't
know how to use this feature.
The most difficult problem is that not all button combinations are
p
On Thu, Jun 07, 2007 at 08:42:41PM +0200, Peter D'Hoye wrote:
> > As I didn't attend DevCon I'm not aware of the discussion
> > you guys had there, but I see a lot of discussion everywhere
> > regarding keyboard mappings in different parts of Rockbox.
> > IMHO it would be fairly easy to ab
> As I didn't attend DevCon I'm not aware of the discussion
> you guys had there, but I see a lot of discussion everywhere
> regarding keyboard mappings in different parts of Rockbox.
> IMHO it would be fairly easy to abstract the buttons layer
> and use only "actions" everywhere in the code
> I think that devcon did agree to a level of configurability.
As I didn't attend DevCon I'm not aware of the discussion you guys had there,
but I see a lot of discussion everywhere regarding keyboard mappings in
different parts of Rockbox. IMHO it would be fairly easy to abstract the buttons
l
> I think that devcon did agree to a level of configurability.
> I personally really wouldn't object to letting the short
> press be semi-configurable (as long as it's a quite limited
> list of what it can do, such as that playlist/insert option,
> or most of the options in the main menu).
I'l
I think that devcon did agree to a level of configurability. I
personally really wouldn't object to letting the short press be
semi-configurable (as long as it's a quite limited list of what it can
do, such as that playlist/insert option, or most of the options in the
main menu).
But my personal
if we are really against a configurable rec button, I suggest this behavior:
- rec short is playlist viewer in wps, and insert track in file view
- rec long is recording screen, everywhere.
But, i thought that it was agreed on devcon that we want some kind of
configurability?
Rincewind
attached are two patches inspired by the devcon decisions for te left
button and rec button.
left_button.patch was discussed already but a decision never came
about. It checks for the BUTTON_LEFT code (simplest way to do it) in
the setting screen and accepts the new value if it gets it.
The part
14 matches
Mail list logo
