I'm not sure anyone else has ever gone down this road, but I thought I'd at least ask. I've got a FLL which hooks into the active code window's messaging (by using the API calls SetWindowLong() in association with CallWindowProc()). The hook works just fine (meaning, my code is called, the text appears in the editor as I'm typing), but it seems to disable Intellisense, regardless of whether I actually do anything with the windows message or not (usually I'm just using CallWindowProc to pass the message on).

I've tried using CallWindowProc first, then continuing with my handling of the message and vice-versa (I'd much prefer VFP finish with all of it's handling before my code is called - in fact, I'm going to depend on it). In addition, it seems to effect the CR+LF which is normally added to each line (when my code is hooked in, the LF is missing).

Is there some special handling that is necessary to make this work?