Thanks Ewald - will follow this up - much appreciated
On 08/11/16 07:40, Ewald wrote:
On 06/11/16 23:50, Steve Gatenby wrote:
run wmctrl (or other) from the TProcess / RunCommand code
the TProcess instance returns the PID for the new process
read the relevant file under /proc/PID/status - it wi
On 06/11/16 23:50, Steve Gatenby wrote:
> run wmctrl (or other) from the TProcess / RunCommand code
> the TProcess instance returns the PID for the new process
> read the relevant file under /proc/PID/status - it will intermittently
> show the new process is actually a copy of the caller app.
> (me
Intermittantly (but consistantly), my app will run the wrong process
using either TAsyncProcess or RunCommand.
I understand it will be my bug, just looking for a clue :)
The 'Run' function is within a fpc library.
A loop calls the 'Run' function each second to run a system process (eg
ls or w
