Results 1 to 3 of 3

Thread: System Wide Hooking - Help

  1. #1

    Thread Starter
    Lively Member
    Join Date
    May 2004
    Location
    Home
    Posts
    85

    System Wide Hooking - Help

    Ok well I am trying to create a system wide hook where my application can be informed if a WM_CREATE message is BEING SENT to the window. I am trying to figure out how to properly set this Global/System Wide hook and intercept the message accordingly.

    I basically want to trash it (nullify) before it reaches the specific window that it is in progress to.
    Im sure this can be done with a driver (since i think everything can) but I am looking for something simple.
    I've noticed it is quite easy to monitor mesages but not intercept them. (RegisterWindowMessage)
    The SetWindowsHookEx seems to want a dll to set a global hook for anythign other than Mouse and Key hooking. (Which is very very annoying since I really hate dlls and how applications then requrie more files and have more dependencies and more crap to go wrong)

    I am wondering if this is possible without a dll (setting a global window message listening & managing hook)

    If not then I guess I will just have to deal with the damn dll.

    My main concern in this thread is... Can anyone post some examples window message interception with system hooks.
    I know they must be out there, because I know many applications implement them inorder to properly perform various window events effeciently without resource consumption.)

    So if you have any examples (preferably without dll usage, but if only way then I would like to see) please post. Thanks

  2. #2

  3. #3

    Thread Starter
    Lively Member
    Join Date
    May 2004
    Location
    Home
    Posts
    85

    Re: System Wide Hooking - Help

    because I would like to work with window manipulation and have some smoother functions to make windows not flicker.

    It looks better to just kill WS_VISIBLE being sent to a window and have it not show, opposed to having it become visible, waiting for it to finally show, and then hide it, making ur application kinda badly coded, to have to wait, and to have windows flicker if u need to do some function by use of another window.

Posting Permissions

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



Click Here to Expand Forum to Full Width