summaryrefslogtreecommitdiff
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--libopie2/opiebluez/obluetooth.cpp13
-rw-r--r--libopie2/opiebluez/obluetooth.h4
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
357 return QString( "%1:%2" ).arg( major ).arg( minor ); 357 return QString( "%1:%2" ).arg( major ).arg( minor );
358} 358}
359 359
360QString OBluetoothDevice::getName()
361{
362 /* FIXME: Uahhh, this gets ugly.
363 The BlueZ kernel interface seems to be very badly (if at all) documented.
364 All people are assuming that you use libbluetooth to talk to that stack.
365 However since libbluetooth is GPL, we can't do that :/
366 Guess, we are stuck here until someone finds time and/or motivation to look
367 into that and create some easy-to-understand examples for how to talk
368 directly to the BlueZ kernel interface.
369 */
370};
371
372
373} 360}
374} 361}
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
183 * @returns the class of device. 183 * @returns the class of device.
184 */ 184 */
185 QString deviceClass() const; 185 QString deviceClass() const;
186 /**
187 * @returns the device name.
188 */
189 QString getName();
190 186
191 private: 187 private:
192 class Private; 188 class Private;