From d85171d34a28e53d416609fb0e60129f570463cf Mon Sep 17 00:00:00 2001 From: Alex Blasche Date: Mon, 27 Jan 2014 17:23:47 +0100 Subject: Refine documentation for QBluetoothSocket::localXYZ() functions. Bluez never returns anything until the connection has been established. BlackBerry and the future Android port are much quicker. Change-Id: Ic465a9b68176e7fff5f0c88b4fb602f8665f7197 Reviewed-by: Fabian Bumberger --- src/bluetooth/qbluetoothsocket.cpp | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/src/bluetooth/qbluetoothsocket.cpp b/src/bluetooth/qbluetoothsocket.cpp index 9eaf6758..2f086d91 100644 --- a/src/bluetooth/qbluetoothsocket.cpp +++ b/src/bluetooth/qbluetoothsocket.cpp @@ -169,19 +169,30 @@ Q_DECLARE_LOGGING_CATEGORY(QT_BT_QNX) \fn QString QBluetoothSocket::localName() const Returns the name of the local device. + + Although some platforms may differ the socket must generally be connected to guarantee + the return of a valid name. In particular, this is true when dealing with platforms + that support multiple local Bluetooth adapters. */ /*! \fn QBluetoothAddress QBluetoothSocket::localAddress() const Returns the address of the local device. + + Although some platforms may differ the socket must generally be connected to guarantee + the return of a valid address. In particular, this is true when dealing with platforms + that support multiple local Bluetooth adapters. */ /*! \fn quint16 QBluetoothSocket::localPort() const Returns the port number of the local socket if available, otherwise returns 0. - On BlackBerry, this feature is not supported and returns 0. + Although some platforms may differ the socket must generally be connected to guarantee + the return of a valid port number. + + On BlackBerry, this feature is not supported at all and the function always returns 0. */ /*! -- cgit v1.2.3