From 0ea12029c3d8883ba928d33e36a397657e6b1ae5 Mon Sep 17 00:00:00 2001 From: Andre Hartmann Date: Sat, 27 Jul 2019 21:45:31 +0200 Subject: QCanBusDevice: Rewrap documentation Change-Id: I615a9113db1fcc2f787950dac70847d852d06a1d Reviewed-by: Alex Blasche Reviewed-by: Denis Shienkov --- src/serialbus/qcanbusdevice.cpp | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'src') diff --git a/src/serialbus/qcanbusdevice.cpp b/src/serialbus/qcanbusdevice.cpp index af004d4..713dc52 100644 --- a/src/serialbus/qcanbusdevice.cpp +++ b/src/serialbus/qcanbusdevice.cpp @@ -790,9 +790,10 @@ QVector QCanBusDevice::readAllFrames() As per CAN bus specification, frames of type \l {QCanBusFrame::RemoteRequestFrame} {remote transfer request (RTR)} - do not have a payload, but a length from 0 to 8 (including). This length indicates - the expected response payload length from the remote party. Therefore when sending a RTR frame using - this function it may still be required to set an arbitrary payload on \a frame. The length of + do not have a payload, but a length from 0 to 8 (including). This length + indicates the expected response payload length from the remote party. + Therefore when sending a RTR frame using this function it may still + be required to set an arbitrary payload on \a frame. The length of the arbitrary payload is what is set as size expectation for the RTR frame. \sa QCanBusFrame::setPayload() -- cgit v1.2.3