Communicating between to standalones with "write to process"

[Dr. Hawkins]

I've attached a pair of trivial demo stacks here.

They assume that the standalones get compiled to the desktops in folders,
and probably need to be changed . . . I even added that they
are public domain at the top of the stack scripts . . .

Anyway, what they try to do is have "master" open "slave",  This much works.

It opens for "binary update".  "The result" is unchanged, so there is
apparently no error (but shouldn't it be set to empty on success?

The slave loops every second, watching standard input, and displaying that
in it's field.

But nothing happens . . .

I'm including these as I figure it would be useful to have a file pair that
actually works available on, uhm, wherever the sample files are these days.

I actually want to turn this back into a single executable, whose behavior
depends upon which name it was called under (so the visible slave file
would be a link to the master.

*really* nice would be for two livecode processes to be able to share a
SQLite :memory: database . . .




-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462