Details
-
Suggestion
-
Resolution: Done
-
P2: Important
-
5.12
-
None
-
fd9b9c73ca60c66d01376ddbd6d36e9ea2dfa95c
Description
Right now we have two means to report errors during operation:
- print log messages with qCDebug/qCWarning
- call QCanBusDevice::setError(), which emits a signal
For now, different places handle errors in different ways, some only log the error, some only emit the signal.
The best solutions would IMHO be to do both, as it allows the end user to choose how to react to errors:
- connect to errorOccurred() and handle the problem in user code
- enable the logging to see errors in a log
- ignore errors by disabling logging and not connecting to the errorOccurred() signal
Attachments
For Gerrit Dashboard: QTBUG-70449 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
239298,11 | QCanBusDevice: More error codes and messages on failures | dev | qt/qtserialbus | Status: MERGED | +2 | 0 |