linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] DBUS API - Service Classes as ints?
Date: Tue, 18 Jul 2006 16:44:04 +1000	[thread overview]
Message-ID: <200607181644.05026.denis.kenzior@trolltech.com> (raw)

Marcel,

Is it a good idea/Are there any plans to extend the current DBUS API to enable 
Major/Minor/Service classes of the local Adapter to be available/settable in 
integer form? The string representations are nice and user-friendly, however 
we need to maintain internationalized versions of these, so doing conversion 
ourselves is much easier.  

This would also solve the problem of combination minor device numbers (e.g. in 
case of peripherals).  How would you set "Pointing device" + "Joystick" via 
the current API?  It would also bring the API closer in line with the 
RemoteDevice API which uses uint32 to represent the class.

Perhaps SetClass(uint32) and 
uint32 GetClass()?

If this is wanted, I can work on a patch.

-Denis


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2006-07-18  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18  6:44 Denis KENZIOR [this message]
2006-07-18 10:54 ` [Bluez-devel] DBUS API - Service Classes as ints? Marcel Holtmann
2006-07-21  5:02   ` Denis KENZIOR
2006-07-22 23:11     ` 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=200607181644.05026.denis.kenzior@trolltech.com \
    --to=denis.kenzior@trolltech.com \
    --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;
as well as URLs for NNTP newsgroup(s).