Right now I am trying combinations of a number of lines in x amount of time...
My first test is actually running right now and I can compare the output to what is done in a terminal window. The send in time could be promising do you have a small sample? thanks, Glen On Wed, Mar 28, 2012 at 3:47 PM, Mike Bonner <bonnm...@gmail.com> wrote: > Could do a send in time to do the read loop, and I believe the form of read > you use will determine how blocking it is. if you read till end, eof, > number of bytes etc I believe it will block until the criteria is met. > Haven't done this much though so not positive. When I do, I tend to use the > "until empty" form. This way if theres nothing in the buffer it moves right > along and loops again and since its a send in time loop you can give enough > breathing space for the other stuff to happen. > > > > On Wed, Mar 28, 2012 at 3:39 PM, Glen Bojsza <gboj...@gmail.com> wrote: > > > The documentation seems slightly confusing (to me). > > > > On Linux I want to open a process for update, then write the command to > be > > executed and then read from the process and fill the output to a field. > > > > The command takes anywhere from 1 minute to 8 minutes to execute and > while > > it is running it outputs the various stages and results it currently has > > completed. > > > > In the terminal window if I just do the command line it produces anywhere > > between 20 to 100 lines of output where the final line has a unique > output > > acknowledging that it has completed. > > > > How should I be writing my read from process? > > > > I assume that this should be done inside a repeat forever loop where you > > can trap the mouseclick to exit or check for the unique output line from > > the read process to exit. > > > > I can't seem to any output from the read statement? > > > > Finally, is there a way to make this non blocking (ie let it run and > update > > the field while the user moves on to something else)? > > > > thanks, > > > > Glen > > _______________________________________________ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
