> Where is the read only cts property with a ctsChanged signal to monitor the input pin?
Nowhere. Again, there is a impossible have a cross-platform capabilities to notify about change of CTS pins. In principle, this feature is available only for Windows, but POSIX does not provide this. To obtain the status line uses the lines() method, where you can get CTS status. > OK, but it would be immediately clear to anyone who previously worked with serial ports what the API does. Ok, in principle, we can think about renamed from Rate to baudRate, it is can possible. Best regards, Denis 23.01.2013 22:17, shane.kea...@accenture.com пишет: >> As I repeated the above, it can not be done, at least cross-platform. >> On Windows there is a possibility, but not the fact that it is implemented >> correctly. > OK, that is a good reason to not include it. > >>> The UART has four control lines: RTS/CTS and DTR/DSR, two inputs and two >>> outputs. >>> >>> Your API only represents RTS and DTR, and seems to use them as both the >>> output - setRts(), and as the input - rts(), >>rtsChanged() >>> You have included these signal lines in the API so they can be used for out >>> of band signalling / GPIO as opposed to >>flow control which would be >>> handled at the device driver level. I think the input signals and output >>> signals need to >>be separated in the API. >> Why divide by Input / Output? >> So it is clear that you can only control the RTS and DTR, that goes without >> saying. >> Another thing, that also the OS for these outputs is provides interface to >> get their condition, >> so, why not use it? :) > 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. > >>> 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. > > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise private information. If you have received it in > error, please notify the sender immediately and delete the original. Any > other use of the e-mail by you is prohibited. > > Where allowed by local law, electronic communications with Accenture and its > affiliates, including e-mail and instant messaging (including content), may > be scanned by our systems for the purposes of information security and > assessment of internal compliance with Accenture policy. > > ______________________________________________________________________________________ > > www.accenture.com > _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development