WM_ACTIVATEAPP and the IDE environment [resolved]

I finally got around to using a sample that someone posted back in May to trap the windows message WM_ACTIVATEAPP.

I remember being told that subclassing and using this in the IDE environment could be very, very bad.

I can't remember why.

I've also seen some posts before about "knowing" you are in the IDE environment in code and using that condition around code.

Any help would be greatly appreciated.

Found it:

Marty had this nice post:

Tell if you are in IDE

And my VB Guide to Win API told me that if I'm in BREAK mode in the IDE and the SetWindowLong function will be frozen as well and if it gets triggered it'll freeze the app or the system or cause a memory exception...