Rockbox mail archive

• Next message: Paul van der Heu: "RE: user editable keys binding schemes wanted"
• Previous message: phil_at_x-phobie.de: "Re: user editable keys binding schemes wanted"
• In reply to: Nielsen Linus (ext): "RE: user editable keys binding schemes wanted"
• Next in thread: Paul van der Heu: "RE: user editable keys binding schemes wanted"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

On Tue, 1 Oct 2002 08:12:30 +0200, "Nielsen Linus (ext)"
<Linus.Nielsen_at_elema.siemens.se> wrote:
>It is not only a
>matter of assigning a function to a key, it is far more than that
>(key-down/key-up, key combinations, persistent quick-screens...).

The problems like Key-down / Key-up and combinations, including
repeat, double clicks and so on all can be killed by considering them
events. This is already done in button.c and it can be extended if
necessary. Then you may call it mapping events to functions. It's just
the same.

But what do you mean with persistent quick-screens? Like hitting F2
and the menu doesn't disappear unless another button has pressed? That
is a good example how a concept of assignable keys can help us. We
simply make a new key scheme that becomes valid while the quick-screen
is used and return to the wps key scheme when the selection is done.

Phil

• Next message: Paul van der Heu: "RE: user editable keys binding schemes wanted"
• Previous message: phil_at_x-phobie.de: "Re: user editable keys binding schemes wanted"
• In reply to: Nielsen Linus (ext): "RE: user editable keys binding schemes wanted"
• Next in thread: Paul van der Heu: "RE: user editable keys binding schemes wanted"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]