| CMakeLists.txt |
|
1761 |
- |
| configure.cmake |
|
790 |
- |
| doc |
|
|
- |
| qserialport.cpp |
|
42167 |
- |
| qserialport.h |
|
7042 |
- |
| qserialport_p.h |
|
8050 |
- |
| qserialport_unix.cpp |
input mode flags |
33670 |
- |
| qserialport_win.cpp |
|
21007 |
- |
| qserialportglobal.h |
|
455 |
- |
| qserialportinfo.cpp |
!
\class QSerialPortInfo
\brief Provides information about existing serial ports.
\ingroup serialport-main
\inmodule QtSerialPort
\since 5.1
Use the static \l availablePorts() function to generate a list of
QSerialPortInfo objects. Each QSerialPortInfo object in the list represents
a single serial port and can be queried for the \l {portName}{port name},
\l {systemLocation}{system location}, \l description, \l manufacturer, and
some other hardware parameters. The QSerialPortInfo class can also be
used as an input parameter for the \l {QSerialPort::}{setPort()} method of
the QSerialPort class.
\section1 Example Usage
The example code enumerates all available serial ports and prints their
parameters to console:
\snippet doc_src_serialport.cpp enumerate_ports
\section1 Port enumeration on Linux
By default Linux uses \c {libudev} to enumerate the available serial ports.
If the library is not available, it falls back to reading files in the
\c {/sys/class/tty} directory.
It is known that some versions of \c {libudev} have a bug and incorrectly
report VID and PID of a USB hub instead of the actual device. In such cases,
define the \c {QT_SERIALPORT_SKIP_UDEV_LOOKUP} environment variable to skip
the \c {libudev} lookup and only use the information from the
\c {/sys/class/tty} directory.
\sa QSerialPort
|
7163 |
- |
| qserialportinfo.h |
|
1736 |
- |
| qserialportinfo_freebsd.cpp |
|
10678 |
- |
| qserialportinfo_osx.cpp |
|
7725 |
- |
| qserialportinfo_p.h |
|
1243 |
- |
| qserialportinfo_unix.cpp |
|
14429 |
- |
| qserialportinfo_win.cpp |
|
21880 |
- |
| qt_cmdline.cmake |
|
0 |
- |
| qtudev_p.h |
|
4383 |
- |
| qwinoverlappedionotifier.cpp |
!
\class QWinOverlappedIoNotifier
\inmodule QtCore
\brief The QWinOverlappedIoNotifier class provides support for overlapped I/O notifications on Windows.
\since 5.0
\internal
The QWinOverlappedIoNotifier class makes it possible to use efficient
overlapped (asynchronous) I/O notifications on Windows by using an
I/O completion port.
Once you have obtained a file handle, you can use setHandle() to get
notifications for I/O operations. Whenever an I/O operation completes,
the notified() signal is emitted which will pass the number of transferred
bytes, the operation's error code and a pointer to the operation's
OVERLAPPED object to the receiver.
Every handle that supports overlapped I/O can be used by
QWinOverlappedIoNotifier. That includes file handles, TCP sockets
and named pipes.
Note that you must not use ReadFileEx() and WriteFileEx() together
with QWinOverlappedIoNotifier. They are not supported as they use a
different I/O notification mechanism.
The hEvent member in the OVERLAPPED structure passed to ReadFile()
or WriteFile() is ignored and can be used for other purposes.
\warning This class is only available on Windows.
Due to peculiarities of the Windows I/O completion port API, users of
QWinOverlappedIoNotifier must pay attention to the following restrictions:
\list
\li File handles with a QWinOverlappedIoNotifer are assigned to an I/O
completion port until the handle is closed. It is impossible to
disassociate the file handle from the I/O completion port.
\li There can be only one QWinOverlappedIoNotifer per file handle. Creating
another QWinOverlappedIoNotifier for that file, even with a duplicated
handle, will fail.
\li Certain Windows API functions are unavailable for file handles that are
assigned to an I/O completion port. This includes the functions
\c{ReadFileEx} and \c{WriteFileEx}.
\endlist
See also the remarks in the MSDN documentation for the
\c{CreateIoCompletionPort} function.
|
13609 |
- |
| qwinoverlappedionotifier_p.h |
|
1484 |
- |
| removed_api.cpp |
|
505 |
- |