PythonQt.Qt.QAbstractSocket · declarations 001
Back to PythonQt.Qt.QAbstractSocket
aboutToClose
aboutToClose(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.aboutToClose; argument details are not documented.
bytesWritten
bytesWritten(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.bytesWritten; argument details are not documented.
channelBytesWritten
channelBytesWritten(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.channelBytesWritten; argument details are not documented.
channelReadyRead
channelReadyRead(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.channelReadyRead; argument details are not documented.
connected
connected(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.connected; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QAbstractSocket::connected()
This signal is emitted after connectToHost() has been called and a connection has been successfully established.
Note: On some operating systems the connected() signal may be directly emitted from the connectToHost() call for connections to the localhost.
See also connectToHost() and disconnected().
Source: https://doc.qt.io/archives/qt-5.15/qabstractsocket.html#connected
destroyed
destroyed(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.destroyed; argument details are not documented.
disconnected
disconnected(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.disconnected; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QAbstractSocket::disconnected()
This signal is emitted when the socket has been disconnected.
Warning: If you need to delete the sender() of this signal in a slot connected to it, use the deleteLater() function.
See also connectToHost(), disconnectFromHost(), and abort().
Source: https://doc.qt.io/archives/qt-5.15/qabstractsocket.html#disconnected
errorOccurred
errorOccurred(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.errorOccurred; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QAbstractSocket::errorOccurred(QAbstractSocket::SocketError socketError)
This signal is emitted after an error occurred. The socketError parameter describes the type of error that occurred.
When this signal is emitted, the socket may not be ready for a reconnect attempt. In that case, attempts to reconnect should be done from the event loop. For example, use a QTimer::singleShot() with 0 as the timeout.
QAbstractSocket::SocketError is not a registered metatype, so for queued connections, you will have to register it with Q_DECLARE_METATYPE() and qRegisterMetaType().
This function was introduced in Qt 5.15.
See also error(), errorString(), and Creating Custom Qt Types.
Source: https://doc.qt.io/archives/qt-5.15/qabstractsocket.html#errorOccurred
hostFound
hostFound(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.hostFound; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QAbstractSocket::hostFound()
This signal is emitted after connectToHost() has been called and the host lookup has succeeded.
Note: Since Qt 4.6.3 QAbstractSocket may emit hostFound() directly from the connectToHost() call since a DNS result could have been cached.
See also connected().
Source: https://doc.qt.io/archives/qt-5.15/qabstractsocket.html#hostFound
objectNameChanged
objectNameChanged(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.objectNameChanged; argument details are not documented.
proxyAuthenticationRequired
proxyAuthenticationRequired(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.proxyAuthenticationRequired; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QAbstractSocket::proxyAuthenticationRequired(const QNetworkProxy \&proxy, QAuthenticator *authenticator)
This signal can be emitted when a proxy that requires authentication is used. The authenticator object can then be filled in with the required details to allow authentication and continue the connection.
Note: It is not possible to use a QueuedConnection to connect to this signal, as the connection will fail if the authenticator has not been filled in with new information when the signal returns.
This function was introduced in Qt 4.3.
See also QAuthenticator and QNetworkProxy.
Source: https://doc.qt.io/archives/qt-5.15/qabstractsocket.html#proxyAuthenticationRequired
readChannelFinished
readChannelFinished(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.readChannelFinished; argument details are not documented.
readyRead
readyRead(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.readyRead; argument details are not documented.
stateChanged
stateChanged(*args: Any, **kwargs: Any) -> Any
Native PythonQt.Qt.QAbstractSocket.stateChanged; argument details are not documented.
Supplemental documentation: Qt 5 reference:
[signal] void QAbstractSocket::stateChanged(QAbstractSocket::SocketState socketState)
This signal is emitted whenever QAbstractSocket's state changes. The socketState parameter is the new state.
QAbstractSocket::SocketState is not a registered metatype, so for queued connections, you will have to register it with Q_DECLARE_METATYPE() and qRegisterMetaType().
See also state() and Creating Custom Qt Types.
Source: https://doc.qt.io/archives/qt-5.15/qabstractsocket.html#stateChanged