aRts audio server
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

106 lines
2.8 KiB

Copyright (C) 1999-2001 Stefan Westerfeld
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
Library General Public License for more details.
You should have received a copy of the GNU Library General Public License
along with this library; see the file COPYING.LIB. If not, write to
the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
Boston, MA 02110-1301, USA.
* BC - Status (2002-03-08): QIOManager.
* QIOManager is kept binary compatible.
#include "iomanager.h"
#include <tqobject.h>
#include <tqtimer.h>
#include <tqsocketnotifier.h>
#include <list>
#include "arts_export.h"
namespace Arts {
class QIOWatch;
class QTimeWatch;
* QIOManager performs MCOP I/O inside the Qt event loop. This way, you will
* be able to receive requests and notifications inside Qt application. The
* usual way to set it up is:
* <pre>
* TDEApplication app(argc, argv); // as usual
* Arts::QIOManager qiomanager;
* Arts::Dispatcher dispatcher(&qiomanager);
* ...
* return app.exec(); // as usual
* </pre>
class ARTS_EXPORT QIOManager : public IOManager {
friend class QIOWatch;
friend class QTimeWatch;
std::list<QIOWatch *> fdList;
std::list<QTimeWatch *> timeList;
void dispatch(QIOWatch *ioWatch);
void dispatch(QTimeWatch *timeWatch);
void processOneEvent(bool blocking);
void run();
void terminate();
void watchFD(int fd, int types, IONotify *notify);
void remove(IONotify *notify, int types);
void addTimer(int milliseconds, TimeNotify *notify);
void removeTimer(TimeNotify *notify);
* This controls what QIOManager will do while waiting for the result
* of an MCOP request, the possibilities are:
* @li block until the request is completed (true)
* @li open a local event loop (false)
* It is much easier to write working and reliable code with blocking
* enabled, so this is the default. If you disable blocking, you have
* to deal with the fact that timers, user interaction and similar
* "unpredictable" things will possibly influence your code in all
* places where you make a remote MCOP call (which is quite often in
* MCOP applications).
void setBlocking(bool blocking);
* Query whether blocking is enabled.
bool blocking();