The Connection::ErrorDetails class represents the details of a connection error.
It contains detailed information about the reason for the connection going invalidated().
Some services may provide additional error information in the ConnectionError D-Bus signal, when a Connection is disconnected / has become unusable. If the service didn't provide any, or has not been invalidated yet, the instance will be invalid, as returned by isValid().
The information provided by invalidationReason() and this class should always be used in error handling in preference to statusReason(). The status reason can be used as a fallback, however, if the client doesn't understand what a particular value returned by invalidationReason() means, as it may be domain-specific with some services.
Connection::errorDetails() can be used to return the instance containing the details for invalidating that connection after invalidated() has been emitted.
| bool Tp::Connection::ErrorDetails::hasDebugMessage |
( |
| ) |
const |
|
inline |
Return whether or not the details specify a debug message.
If present, the debug message will likely be the same string as the one returned by invalidationMessage().
The debug message is purely informational, offered for display for bug reporting purposes, and should not be attempted to be parsed.
- Returns
true if debug message is present, false otherwise.
- See also
- debugMessage()
| QString Tp::Connection::ErrorDetails::debugMessage |
( |
| ) |
const |
|
inline |
Return the debug message specified by the details, if any.
If present, the debug message will likely be the same string as the one returned by invalidationMessage().
The debug message is purely informational, offered for display for bug reporting purposes, and should not be attempted to be parsed.
- Returns
- The debug message, or an empty string if there is none.
- See also
- hasDebugMessage()