Hello Robert,
I don't know. Two years ago, I have had the same problem for Windows
95.
I wrote a small C-Wrapper around the Windows FindWindow API call.
At this time, I came from 16-Bit windows and there, a program was
allocated by its Windowname/Class. Then a timed loop may check
periodically if the program is still running.
Mail me if you want the routine.
32-bit Windows knows the concept of pid's and you get the pid back from
the exec but I don't know how to test if the program <PID> is still
running. Maybe use the cygnus Unix-for-Windows Tools and ps but I really
don't know.
Hope really this helps, Harald
On Fri, 25 Aug 2000, Bartis, Robert M (Bob) wrote:
> The problem with this is if you are using a GUI application and another
> window covers your appl or you desire the system to respond to an abort
> request. The lack of a & following the exec effectively locks the process
> and hence no updates on the event loop occur.
> Does anyone know how to get around this?
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/vtcl-user
