Qt provides several ways to implement Inter-Process Communication (IPC) in Qt applications.
- D-Bus The QtDBus module is a Unix-only library you can use to implement IPC using the D-Bus protocol. It extends Qt's Signals and Slots mechanism to the IPC level, allowing a signal emitted by one process to be connected to a slot in another process. This Introduction to D-Bus page has detailed information on how to use the QtDBus module.
- TCP/IP The cross-platform QtNetwork module provides classes that make network programming portable and easy. It offers high-level classes (e.g. QHttp, QFtp) that implement specific application-level protocols, and lower-level classes (e.g. QTcpSocket, QTcpServer, QSslSocket) for implementing protocols.
- Shared Memory The cross-platfrom shared memory class (QSharedMemory) provides access to the operating system's shared memory implementation. It allows safe access to shared memory segments by multiple threads and processes.
- Qt COmmunications Protocol (QCOP) The QCopChannel class implements a protocol for transferring messages between client processes across named channels. QCopChannel is only available in Qt for Embedded Linux. Like the QtDBus module, QCOP extends Qt's Signals and Slots mechanism to the IPC level, allowing a signal emitted by one process to be connected to a slot in another process, but unlike QtDBus, QCOP does not depend on a 3rd party library.
1只能在linux上,4只能在Embedded上,3是数据共享,老老实实用2吧
要么你用这个
bool QWidget::winEvent ( MSG * message, long * result ) [virtual protected]
This special event handler can be reimplemented in a subclass to receive native Windows events which are passed in the message parameter.
In your reimplementation of this function, if you want to stop the event being handled by Qt, return true and set result to the value that the window procedure should return. If you return false, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
[ 此帖被都市无名者在2009-03-16 15:05重新编辑 ]