| -rw-r--r-- | libopie2/opiebluez/obluetooth.cpp | 13 | ||||
| -rw-r--r-- | libopie2/opiebluez/obluetooth.h | 4 |
2 files changed, 0 insertions, 17 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 @@ -357,18 +357,5 @@ QString OBluetoothDevice::deviceClass() const 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. - */ -}; - - } } diff --git a/libopie2/opiebluez/obluetooth.h b/libopie2/opiebluez/obluetooth.h index fa3d2c1..4bcd964 100644 --- a/libopie2/opiebluez/obluetooth.h +++ b/libopie2/opiebluez/obluetooth.h @@ -183,10 +183,6 @@ class OBluetoothDevice : public QObject * @returns the class of device. */ QString deviceClass() const; - /** - * @returns the device name. - */ - QString getName(); private: class Private; |