On Wed, 2003-03-26 at 10:05, Alan Scheinine wrote: > I would like to use DX inside of Qt (the GUI by Trolltech). I have never used DXLink with QT. It should work fine but I don't know about any special tricks.
You don't need DXLInitializeXMainLoop(). That's just a convenience for use with libXt and widgets. It's not even required if you're using libXt and widgets. DXLink just uses sockets, not X events. You have to make sure that message traffic between your app and dx is handled. (i.e. DXLHandlePendingMessages() is called) The purpose of DXLIitializeXMainLoop is to make sure that DXLHandlePendingMessages is called.) Sometimes using DXLSetMessageDebugging() can help. If you're wondering specifically about DXLSync() you could sandwich a call to DXLSync() between calls to activate then deactivate debug messages. (If that produces more than about 1/2 dozen messages to stdout, then maybe something else is wrong.) DXLIsMessagePending() is a little like DXLSync(). It doesn't block but also doesn't cause a round trip. You do not have to be concerned about the transmission of additional information from your app to dx causing a crash or loss of coherence. (The only loss of coherence your app has to handle is what the user expects if - let's say - a particular iso value is showing but has not been used by dx in an execution that puts the corresponding image onto the screen.) HTH
