> I am trying subclass a window that belongs to another process

>and catch the WM_CLOSE message and update my process' user interface.

"Mattias Sjögren" <mattias.dont.want.spam@mvps.org> wrote in message
news:Ot6QwlxdEHA.3148@TK2MSFTNGP10.phx.gbl...
> Steven,
>
> > I am trying subclass a window that belongs to another process
>
> You can't do that with SetWindowLong. Catching messages in other
> processes either requires code injection (something like
> CreateRemoteThread) or a global message hook. Both are ugly and messy
> to implement.
>
>
> >and catch the WM_CLOSE message and update my process' user interface.
>
> Personally I'd go for a polling solution rather than rely on
> notifications. Perhaps periodically call EnumWinows or
> EnumProcesses/Process32First to enumerate windows or processes. This
> has the additional advantage of working even if the foreign app
> crashes and no WM_CLOSE message is sent.
>
>
>
> Mattias
>
> --
> Mattias Sjögren [MVP] mattias @ mvps.org
> http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
> Please reply only to the newsgroup.