Hi, I encountered some problems again.

What I am trying to do is to open a window and take care of information.

Right now I am using the dos.library-comand Read() to get
information on events from the GUI - this is not an arexx-script.
After I have created the GUI and opened it via "open", according to the
manual I must make a call to "continue" in order to read windowevents
continously after I have made a modify-call and changed for example a
button.

Quote:
;--

"WE do not want to modify anything at this time but we still need to send the
continue line so the pipe will stop looking for modify lines and send us
another event.
'continue'
The line read from the pipe should be
'ok'"

<snap>

You keep reading an event then sending modify commands until the end of file
is received. You could also close the pipe after the close event is read.

;--
End quote

However as I want my program to be non-halting (and Read() doesn't return
until data is available) I use a call to Seek() in order to see if there is
pending
data before calling FGets(). This seems to work fine but the problem is the
need for a call to "continue" after I have done a "modify" and the fact that the
pipe
now starts to wait for an event.

My GUI though needs to be "fed" from a standalone program which can send
"modify"-commands to it any time. This seems to cause a clog in the pipe.

So, in short, how can I let the program listen for both gui-events and send
"modify"-calls and NOT clog the pipe?

I hope you understood what I was rambling about :)

//Thor
--
Peter Thor