From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Using AVRCP with current BlueZ
Date: Fri, 23 Nov 2007 14:32:37 +0200 [thread overview]
Message-ID: <7E3B31FF-53A2-443D-86DC-0F663B3F6D03@gmail.com> (raw)
In-Reply-To: <9a119b3c0711230400l2885eccei3b32efb152ddec0@mail.gmail.com>
On Nov 23, 2007, at 14:00, Csillag Krist=F3f wrote:
> One more question: what was the reason to use
>
> KEY_NEXT and KEY_PREVIOUS, instead of
> KEY_NEXTSONG and KEY_PREVIOUSSONG?
No special reason, except that the names of the key codes matched more =
precisely the AVRCP spec.
> The latter are below-256 keycodes (like KEY_PLAYPAUSE,
> which is used by BlueZ for pause) handled nicely by
> all applications (like keytouch), where the former, which
> are currently used, are extended codes, mostly unsupported
> in user-space.
If this improves interoperability with existing applications then it's =
probably a good idea to apply your patch. I'll commit it to CVS later =
today unless somebody has a good reason why it shouldn't be done.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-11-23 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 16:26 Using AVRCP with current BlueZ Csillag Kristóf
2007-11-22 17:13 ` [Bluez-users] " Johan Hedberg
2007-11-23 2:36 ` \x11
2007-11-23 12:00 ` Csillag Kristóf
2007-11-23 12:32 ` Johan Hedberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E3B31FF-53A2-443D-86DC-0F663B3F6D03@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox