Disable the TQSocketNotifier<-->QSocketNotifier bridge and utilize

the builtin TQSocketNotifier code instead.

This fixes the DCOP server failure due to:
"tqsocketnotifiers are not being registered with the main tqeventloop (via TQApplication::eventLoop()->registerSocketNotifier( this )) (and for obvious reasons, they ***cannot*** be if the tqsocketnotifier<-->qsocketnotifier bridge is active)"
pull/1/head
Timothy Pearson 13 years ago
parent 808772afcd
commit ff009161ef

@ -48,7 +48,12 @@
#include <sys/types.h>
#endif
#ifdef USE_QT4
#if 0
//#ifdef USE_QT4
TQSocketNotifier::TQSocketNotifier( int socket, Type type, TQObject *tqparent, const char *name ) : QSocketNotifier(socket, type, tqparent) {
setObjectName(name);
}
#else // USE_QT4
@ -267,4 +272,4 @@ bool TQSocketNotifier::event( TQEvent *e )
return FALSE;
}
#endif // USE_QT4
#endif // USE_QT4

@ -47,20 +47,22 @@
#include "tqobject.h"
#endif // TQT_H
#ifdef USE_QT4
#if 0
//#ifdef USE_QT4
#include <Qt/qsocketnotifier.h>
#endif // USE_QT4
#ifdef USE_QT4
#if 0
//#ifdef USE_QT4
class TQ_EXPORT TQSocketNotifier : public QSocketNotifier
{
Q_OBJECT
TQ_OBJECT
public:
TQSocketNotifier( int socket, Type type, TQObject *tqparent=0, const char *name=0 ) : QSocketNotifier(socket, type, tqparent) { setObjectName(name); }
TQSocketNotifier( int socket, Type type, TQObject *tqparent=0, const char *name=0 );
};
#else // USE_QT4

Loading…
Cancel
Save