[Development] Proposal - QtSerialPort graduation from the Playground

Thiago A. CorrĂȘa thiago.correa at gmail.com
Wed Jan 23 19:37:14 CET 2013


Hi,

On Wed, Jan 23, 2013 at 4:17 PM,  <shane.kearns at accenture.com> wrote:
>
> Let me put it another way:
> Where is the read only cts property with a ctsChanged signal to monitor the input pin?
> I expect rts() to return the value we are currently sending on the RTS output, and cts() to return the value we are currently receiving on the CTS input.

Actually there is no signal for RTS, there is a bool rts() which is a
convenient way to do lines() & SerialPort::Rts.
All other signals are available from the lines() call.
IMHO adding all lines would clutter a bit. Also, those lines status
are usually pooled from the OS. It might not be possible to have it on
all platforms.

>
>>>For the rate property, what was the reason not to name it baudRate?
>>>That's probably a familiar term to people working with serial ports.
>
>>Besause baudRate is too long. :)
>
> OK, but it would be immediately clear to anyone who previously worked with serial ports what the API does.
>

Oh, I thought it was discussed previously, but since you mentioned,
baudRate would be nicer. My first impression was that it was supposed
to at least begin with baud, so finding rate took a few more minutes.



More information about the Development mailing list