Whatever works for your situation! At least one of my jobs, which runs a few
times a week (pulling data from an internal system, generating and emailing a
PDF report) has to launch fresh each time because of a bug in the graph widget
which displays wrong if the script runs twice!
There are others where the LC qpp is part of a dance in which other systems
run before and after, so a batch script invoking each in turn is the thing
that's scheduled.
But of course there are contexts in which the best solution is an LC app
waiting for a time or a command at which to leap into action.
On 12/07/2022 22:56, Bob Sneidar via use-livecode wrote:
Hmmm. Ok, but it seems having the LC app running invisibly all the time,
listening for a command, something the cron service could do through the
terminal easily enough, you could make it much more efficient. Just methods and
madness I suppose.
Bob S
On Jul 12, 2022, at 13:15 , Ben Rubinstein via use-livecode
<use-livecode@lists.runrev.com> wrote:
I think I may not have been very clear.
This isn't LiveCode doing anything special; just a standalone LiveCode app that
either does something immediately on launch (and then quits), or inspects the
command line parameters to decide what to do (and then quits).
_______________________________________________
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
