had one more thought to make it easier. go back to your original idea of
using a shell script but make the script have the format..
#!/bin/sh
[your command here]
echo "Command Complete"
That way, its easy to see when an individual command finishes.
In addition, if you use 3 separate files, 1
>
>
> great ideas from Mark Wieder, Mike Bonner, Warren Samples
>
>
And Glen Bojsza ! Thanks guys!
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
Thank you very much,
great ideas from Mark Wieder, Mike Bonner, Warren Samples
I will be working with these suggestions for the next couple of days and
report back to you guys.
sqb
--
Stephen Barncard - Sebastopol Ca. USA -
mixstream.org
On Sun, Dec 24, 2017 at 9:10 PM, Warren Samples via
On 12/24/2017 04:05 PM, Stephen Barncard via use-livecode wrote:
All of the commands work great by using the shell command in LC, except for
the fact that my app waits until some of the commands have finished.
If your concern is bypassing the blocking nature of shell(), then you
should be
IGnore the "with message" part, had a brain freeze. It would be -- open
process pdata for text read
And then do the -- send "monitorslave pData' to me in 50 millisec -- to
start the loop.
Just tested on linux. I can start a find process, grab the output of dmesg
and cat a file and direct output
Off the top of my head, untested (no mac available)
on executeProcess pData
put whereAmI() into a; set the defaultFolder to a
-- I'd bipass this
--get "file:xprocess.bat"
--put pData into URL it
open process "file:xprocess.bat" for text write
-- this part, if you want to use a
On 12/24/2017 02:05 PM, Stephen Barncard via use-livecode wrote:
Does someone out there have a clear example of what I am looking for,
using a UNIX executable through *open process *?
1.call the function with parameters
2. allow livecode scripts to continue
3. continuously
