OK, that is LOTS better. Not perfect, but many more messages are
coming through _when_ expected and not always two at a time.
Furthermore, all of the messages are arriving in the Read event -
nothing in the Error event anymore.
I'll need to do more testing to be sure I understand if it is
repeata
Hi Benoît, Bruce,
Yes, the READ and ERROR (and finally KILL) events are all raised as
expected, just not as often as I would want.
In another part of the program I use
JCap = Shell Command For Input Output As "Jack_Capture"
so that I can send it a gb.NewLine to control another mode of the
shell
Le 15/07/2012 01:54, Bruce a écrit :
> On Sun, 2012-07-15 at 00:36 +0100, RICHARD WALKER wrote:
>
>> JCap = Shell Command For Read As "Jack_Capture"
>>
>> My Jack_Capture_Read() procedure has used both
>
> Hi Richard,
>
> Sheer guess, but is "Jack_Capture" a legal name for an observer? Does
> Jack_
On Sun, 2012-07-15 at 00:36 +0100, RICHARD WALKER wrote:
> JCap = Shell Command For Read As "Jack_Capture"
>
> My Jack_Capture_Read() procedure has used both
Hi Richard,
Sheer guess, but is "Jack_Capture" a legal name for an observer? Does
Jack_Capture_Read() ever get invoked? I've always been
I am having difficulty reading the output from a shell command when it
is generated. Something somewhere seems to be storing the messages
until it is ready to give them to my READ and ERROR event handlers.
The command is invoked with:
JCap = Shell Command For Read As "Jack_Capture"
My Jack_Captu
