Planning ahead for threads and more interactivity in rev apps

[Xavier Bury]

The communications is what i didn't need. The 3 apps I made are a reporter
which pulls the info,
a bat generator - generates what needs to be launched and a monitor which
also kills zombie processes.

The bat generator creates the batches (never too many) and launches a bat
that runs alls batches.

I might do some db storage with it later but not planed or needed for the
moment.

The tricky part was to know which process is which that was hung or launched
by this process and that was resolved
by tracking the cmd's PID's with pstool from sysinternal.com. Nice and
easy...

On Nov 13, 2007 8:51 AM, Chipp Walters <chipp at chipp.com> wrote:

> Hey X,
>
> I had to do something like this quite awhile back on XP, and (if I
> remember
> correctly) I managed to either shell a .bat or use open process (can't
> remember which), which returned control immediately to Rev. Then I could
> watch a temp file and do stuff when it changes. The 'send in time' or
> 'wait
> with messages' seemed to work fine for me, no lost mouseclicks or
> anything.
>
> To me it seemed much simpler than actually writing multiple Rev apps which
> talk w/each other.
>
> -C
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>