author | erik <erik> | 2007-04-20 21:27:48 (UTC) |
---|---|---|
committer | erik <erik> | 2007-04-20 21:27:48 (UTC) |
commit | 1edbb754d3c8cfccf1630e2ad1e531e907555cbd (patch) (side-by-side diff) | |
tree | c8f3048a913d51534408f5ae75f6f8e7ff73d144 /libopie2/opiebluez/obluetooth.cpp | |
parent | d07beba6b9351c6b575235522781e3ce8495e578 (diff) | |
download | opie-1edbb754d3c8cfccf1630e2ad1e531e907555cbd.zip opie-1edbb754d3c8cfccf1630e2ad1e531e907555cbd.tar.gz opie-1edbb754d3c8cfccf1630e2ad1e531e907555cbd.tar.bz2 |
removed unused member function
Diffstat (limited to 'libopie2/opiebluez/obluetooth.cpp') (more/less context) (ignore whitespace changes)
-rw-r--r-- | libopie2/opiebluez/obluetooth.cpp | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/libopie2/opiebluez/obluetooth.cpp b/libopie2/opiebluez/obluetooth.cpp index 80f4bfc..e8e6bb3 100644 --- a/libopie2/opiebluez/obluetooth.cpp +++ b/libopie2/opiebluez/obluetooth.cpp @@ -328,47 +328,34 @@ QString OBluetoothDevice::deviceClass() const case 13: minor = "Camcorder"; break; case 14: minor = "Video Monitor"; break; case 15: minor = "Video Display and Loudspeaker"; break; case 16: minor = "Video Conferencing"; break; case 17: minor = "Reserved(17)"; break; case 18: minor = "Gaming/Toy"; break; } break; case 5: major = "Peripheral"; switch ( min ) { case 16: minor = "Keyboard"; break; case 32: minor = "Pointing Device"; break; case 48: minor = "Keyboard and Pointing Device"; break; } break; case 6: major = "Imaging"; if (min & 4) minor = "Display"; else if (min & 8) minor = "Camera"; else if (min & 16) minor = "Scanner"; else if (min & 32) minor = "Printer"; break; case 63: major = "Uncategorized"; break; } return QString( "%1:%2" ).arg( major ).arg( minor ); } -QString OBluetoothDevice::getName() -{ - /* FIXME: Uahhh, this gets ugly. - The BlueZ kernel interface seems to be very badly (if at all) documented. - All people are assuming that you use libbluetooth to talk to that stack. - However since libbluetooth is GPL, we can't do that :/ - Guess, we are stuck here until someone finds time and/or motivation to look - into that and create some easy-to-understand examples for how to talk - directly to the BlueZ kernel interface. - */ -}; - - } } |