1. RE: Win32 ShellExecute
paulp at sugardog.com wrote:
> I am using the win32 ShellExecute function to run a win32 console
> program in a hidden window from a gui program the console program writes
>
> to a file when finished. I am currently using Euwingui
> with my own ShellExecute function because Euwingui does not have a
> hidden shell execute.
> This works correctly but the calling program does not know when the
> called program has finished. I am currently using a loop and the dir
> function which checks for the existance of the filename and a filesize
> greater than zero. I would like to have a better way to check if the
> called program has finished and exited. The loop method could possibly
> get stuck in an endless loop.
>
Why can't you send a windows message to the calling window
when the application completes or closes ?
Bernie
2. RE: Win32 ShellExecute
> Why can't you send a windows message to the calling window
> when the application completes or closes ?
>
> Bernie
>
Well you can, *if* the program you are calling is your own so you can
add this functionality to it. If you calling (for example) exw.exe from
an editor or internet explorer to display a help file, it becomes a
little harder. Cant just pop in there to modify those files eh? Heh.
Actually, I have been searching for a good and decent way of doing this
for awile now. I am convinced there are a couple of CBT (computer based
training) hooks that would be useful in this area, but I have not had
the time to look into it.
3. RE: Win32 ShellExecute
Don Phillips wrote:
> > Why can't you send a windows message to the calling window
> > when the application completes or closes ?
> >
> > Bernie
> >
>
> Well you can, *if* the program you are calling is your own so you can
> add this functionality to it. If you calling (for example) exw.exe from
>
> an editor or internet explorer to display a help file, it becomes a
> little harder. Cant just pop in there to modify those files eh? Heh.
> Actually, I have been searching for a good and decent way of doing this
> for awile now. I am convinced there are a couple of CBT (computer based
>
> training) hooks that would be useful in this area, but I have not had
> the time to look into it.
>
All you have to do is search for the calling windows
title which you probably will know at run-time.
Bernie
4. RE: Win32 ShellExecute
> All you have to do is search for the calling windows
> title which you probably will know at run-time.
>
> Bernie
Yes, I have done this in the past, but I consider this solution
substandard. It requires either a loop, or a timer to be checked
occationally. After I do some more research (some time in the future)
if I find a better solution I will post it...
Don
5. RE: Win32 ShellExecute
Don Phillips wrote:
> > All you have to do is search for the calling windows
> > title which you probably will know at run-time.
> >
> > Bernie
>
> Yes, I have done this in the past, but I consider this solution
> substandard. It requires either a loop, or a timer to be checked
> occationally. After I do some more research (some time in the future)
> if I find a better solution I will post it...
>
Don:
You don't need a timer just send a message using
onEvent when the window closes.
Bernie
