On Thu, 27 Aug 2009 19:06:13 +0200, Peter Brouwer
<pb.maillists@xxxxxxxxxxxxxx> wrote:
After years of analyzing the existing code and receiving/merging patches
related to IR, and taking a looking at the current scenario, it is
clear to me
that something need to be done, in order to have some standard way to
map and
to give precise key meanings for each used media keycode found on
include/linux/input.h.
<snip>
Hi all,
Some end user thoughts, perhaps unwelcome but here it goes :)
I think that standardization of buttons is really needed that application
programmers can relly on, for example I see this like following:
I think that specific MCE compatible buttons need to be implemented that
are specific on most todays remotes. And I imagine a Linux Media Center
that works out-of-the-box. I plug in my Linux supported card, point my
remote and press Media center button which runs media center application.
Because it's standard and that's applications programers implemeted it as
key that triggers their app. If press Videos button on my remote, the app
switches to videos directory, because it's standard, and most remotes have
it, etc.
http://www.spinics.net/lists/linux-media/msg07705.html
And thinking of that, I have configuring nothing, it's already configured
because of standardization of buttons. And, if some advanced user doesn't
like this behavior, he can always tamper configuration files to suite his
need.
Forgive me if I'm missing something, as I don't know how it all works
together, but I think you've figured out the point of the meaning :).
I also welcome this effort.
Cheers,
Samuel
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
