On Mon, 25 Aug 2003 12:00:12 +0200, WhiteRavenEye
<wh***********@hotmail.com> wrote:
<snip>
I must have missed that part of MSDN...
Looks like I'll have to write dll in Delphi...
Too bad it can't be written in VB... Damn ActiveX DLL...
Anyway thanks...
I may be wrong, but I believe that the SetWindowsHookEx is mainly
about 'snooping' - not really subclassing
<snip>
Chaining to the next hook procedure (that is, calling the
CallNextHookEx function) is optional. An application or library can
call the next hook procedure either before or after any processing in
its own hook procedure. Although chaining to the next hook is
optional, it is highly recommended; otherwise, the other applications
that have installed hooks will not receive hook notifications and may
behave incorrectly as a result
</snip>
However the Help Files are a bit unclear on all this