Results 1 to 2 of 2

Thread: WM_ACTIVATEAPP and the IDE environment [resolved]

  1. Jul 20th, 2004, 01:29 PM #1
    szlamany
    szlamany is offline

    Thread Starter
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263

    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.
    Last edited by szlamany; Jul 20th, 2004 at 02:21 PM.
    Reply With Quote Reply With Quote
  2. Jul 20th, 2004, 02:20 PM #2
    szlamany
    szlamany is offline

    Thread Starter
    MS SQL Powerposter szlamany's Avatar
    Join Date
    Mar 2004
    Location
    Connecticut
    Posts
    18,263
    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...
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width