Is there anybody reading this that knows a little about the internals
of DXLink? Trying to track down a problem with the startupui, I found
that it appears under Windows that DXLink cannot queue DXL commands.
The guts of this show up in dxuilib/PacketIF.C and
dxuilib/DXLinkHandler.C. There is a bunch of code for performing
stalling operations to wait for things to finish.
For example under Unix, start the startupui "dx". Click on Samples.
Start Accumulate.net. Before it finishes, go back to the startupui
and click on another network. The new one will not start until the
old has finished.
This does not work correctly under windows. The "end execution" dxl
command works, but then the "close vpe" dxl command is lost.
Now a fix that is available is to set the DX_STALL environment
variable. Try this on your Unix box and it will work the same as on
windows. For example:
setenv DX_STALL 1
dx
Now run the sample shown above and watch how it just kills dx in the
middle of the Accumulate.net when the new net is selected. This works
properly under windows. Anybody have an idea? Who was responsible for
DXLink? Looking at the C++ code, and the nature of socketing--it is
very tough to debug.
David
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
