From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Dbus and RemoteDeviceFound API
Date: Tue, 30 May 2006 17:34:34 +0200 [thread overview]
Message-ID: <1149003274.11251.17.camel@localhost> (raw)
In-Reply-To: <447C62BA.4060301@palmsource.com>
Hi Frederic,
> I am trying to implement other values for minor classes :
>
> Minor classes access point
> fully, 1-17 percent, 17-33 percent, 33-50 percent, 50-67 percent,
> 67-83 percent, 83-99 percent, not available
>
> Minor classes audio video
> uncategorized, headset, handsfree, reserved1, microphone, loudspeaker,
> headphones, portable audio, car audio, set-top box, hifi audio, vcr,
> video camera, camcorder, video monitor, video display and loudspeaker,
> video conferencing, reserved2, gaming/toy
>
> Minor classes imaging
> display, camera, scanner, printer
>
> Minor classes wearable
> wrist watch, pager, jacket, helmet, glasses
>
> Minor classes toy
> robot, vehicle, doll, controller, game
>
> But I have a problem with peripheral class as its minor classes are divided in two parts :
>
> Minor classes peripheral
> uncategorized, keyboard, pointing, combo
>
> Minor classes peripheral 2
> uncategorized, joystick, gamepad, remote control, sensing,
> digitizer tablet, card reader
>
> A peripheral can set two minor classes (i.e. pointing and digitizer tablet) but GetRemoteMinorClass call can only return one string.
> Do you have an idea how this should be implemented to address this ?
So far, I would only return the first ones and simply ignore the others.
Basically you only wanna know if the remote device is a keyboard or
mouse or if it supports both.
> Are you OK with this list of constants ?
Looks good so far, except don't use reserved*. Simply call it unknown or
return an error.
However I leave this open for discussion, but at the end of the day we
need a complete list in the dbus-api.txt document.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-30 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 16:44 [Bluez-devel] Dbus and RemoteDeviceFound API Renaud Malaval
2006-05-17 16:54 ` Marcel Holtmann
2006-05-18 18:10 ` [Bluez-devel] how to measure RSSI with C ozkan gumus
2006-05-30 15:20 ` [Bluez-devel] Dbus and RemoteDeviceFound API Frederic Danis
2006-05-30 15:34 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 15:51 Renaud Malaval
2006-05-17 16:03 ` Marcel Holtmann
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=1149003274.11251.17.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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