注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

love3400wind的blog

like

 
 
 

日志

 
 
 
 

How to Hook the Mouse to Catch Events Outside of your application  

2013-01-12 17:20:39|  分类: IT |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |

Learn how to track the mouse activity even when your application is not active, sits in the Tray or does not have any UI at all.

By installing a system wide (or global) mouse hook you can monitor what the user is doing with the mouse and act accordingly.

Windows Hooks?

In short, a hook is a (callback) function you can create as part of a DLL (dynamic link library) or your application to monitor the 'goings on' inside the Windows operating system.
There are 2 types of hooks - global and local. A local hook monitors things happening only for a specific program (or thread). A global hook monitors the entire system (all threads).

The article "An introduction to hook procedures", states that to create a global hook you need 2 projects, 1 to make the executable file and 1 to make a DLL containing the hook procedure.
Working with keyboard hooks from Delphi explains how to intercept the keyboard input for controls that cannot receive the input focus (like TImage).

Let's Hook the Mouse ...

By design, the movement of the mouse is restricted by the size of your desktop screen (including the Windows Task Bar). When you move the mouse to the left/right/top/bottom edge, the mouse will "stop" - as expected (if you do not have more that one monitor).

Here's an idea for the system-wide mouse hook ....

If, for example, you want to move the mouse to the right side of the screen when it moves toward the left edge (and "touches" it), you might write a global mouse hook to reposition the mouse pointer.

You start by creating a dynamic link library project. The DLL should export two methods : "HookMouse" and "UnHookMouse".

The HookMouse procedure calls the SetWindowsHookEx API passing the "WH_MOUSE" for the first parameter - thus installing a hook procedure that monitors mouse messages. One of the parameters to the SetWindowsHookEx is your callback function Windows will call when there is a mouse message to be processed:

SetWindowsHookEx(WH_MOUSE, @HookProc, HInstance,0) ;

The last parameter (value = 0) in the SetWindowsHookEx defines we are registering a global hook.

The HookProc parses the mouse related messages and sends a custom message ("MouseHookMessage") to our test project:

 


function HookProc(nCode: Integer; MsgID: WParam; Data: LParam): LResult; stdcall;
var
  mousePoint: TPoint;
  notifyTestForm : boolean;
  MouseDirection : TMouseDirection;
begin
  mousePoint := PMouseHookStruct(Data)^.pt;

  notifyTestForm := false;

  if (mousePoint.X = 0) then
  begin
    Windows.SetCursorPos(-2 + Screen.Width, mousePoint.y);
    notifyTestForm := true;
    MouseDirection := mdRight;
  end;
  if (mousePoint.X = -1 + Screen.Width) then
  begin
    Windows.SetCursorPos(1, mousePoint.y);
    notifyTestForm := true;
    MouseDirection := mdLeft;
  end;
  if (mousePoint.Y = 0) then
  begin
    Windows.SetCursorPos(mousePoint.X, -2 + Screen.Height);
    notifyTestForm := true;
    MouseDirection := mdBottom;
  end;
  if (mousePoint.Y = -1 + Screen.Height) then
  begin
    Windows.SetCursorPos(mousePoint.X, 1);
    notifyTestForm := true;
    MouseDirection := mdTop;
  end;

  if notifyTestForm then
  begin
    PostMessage(FindWindow('TMainHookTestForm', nil), MouseHookMessage, MsgID, Integer(MouseDirection));
  end;

  Result := CallNextHookEx(Hook,nCode,MsgID,Data);
end;



Note 1: Read the Win32 SDK Help files to find out about the PMouseHookStruct record and the signature of the HookProc function.

Note 2: a hook function does not need to send anything anywhere - the PostMessage call is used only to indicate that the DLL can comunicate with the "outer" world.

Mouse Hook "Listener"

The "MouseHookMessage" message is posted to our test project - a form named "TMainHookTestForm". We override the WndProc method to get the message and act as needed:
 
procedure TMainHookTestForm.WndProc(var Message: TMessage);
begin
  inherited WndProc(Message);
  if Message.Msg = HookCommon.MouseHookMessage then
  begin
    Signal(TMouseDirection(Message.LParam));
  end;
end;

Of course, when the form is created (OnCreate) we call the HookMouse procedure from the DLL, when it gets closed (OnDestroy) we call the UnHookMouse procedure.

Download both projects to test and further explore the code.

Note: hooks tend to slow down the system because they increase the amount of processing the system must perform for each message. You should install a hook only when necessary, and remove it as soon as possible.
  评论这张
 
阅读(604)| 评论(0)
推荐 转载

历史上的今天

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017