Thanks Dar. I tried the 'for neither' approach but it doesn't work, at
least for the Mac version of my helper app - it's a Unix executable.
However, shell() works fine for both starting and killing it. I don't
have the Windows version of this thing yet, but it'll be a DOS app. It's
a USB device interface app (for a specific device), using HID & low
level calls on the device side and sockets on the Rev side.
Phil Davis
Dar Scott wrote:
On May 27, 2005, at 3:14 PM, Phil Davis wrote:
To use Rev's 'kill' in this situation, I'll need to get the process
name from outside Rev (and then I'm not sure if it'll be what Rev is
looking for, but that's a different issue). That leads me back to
shell(), since my helper app doesn't show up in 'the openProcesses'.
Still, if I can find a way to get the PID at app start time and
preserve it until needed for 'kill', that would be preferable to
everything else. I'll keep working on it.
You can try 'open process ... for neither' to run it (no "start"
needed). And then 'close process'. I had trouble with 'open process'
in the olden days and don't use it, but 'for neither' might not have
those problems.
Dar
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
