One method I have heard of is to redirect output to a text file, then open the file for read and read from the file every so often in a repeat loop. You still need to know when the process has ended so you can break out of the loop.
Bob On Mar 28, 2012, at 2:39 PM, Glen Bojsza 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 > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
