Global hooks

Some times I update the component and post the updated date and the assembly version number so it is recommended to check it once a while.
I created this project as a single utility to hook the mouse, keyboard and the clipboard system wide. It is a library file 'WindowsHookLib' dll that can be referenced into various projects. The mouse and keyboard hooks are low level so you can use the 'Handled' property of the 'WindowsHookLib.MouseEventArgs' or the 'WindowsHookLib.KeyEventArgs' to prevent the windows messages be passed to the other applications. Note you need to use the dll file not the classes in your projects; otherwise they might not work correctly.

Note, if you use any of these hooks than you MUST call their dispose methods when the application exits. The method will remove the hook and free the memory that is used by the hook component.

MOUSE HOOK

The 'LLMouseHook' class from 'WindowsHookLib' is designed to hook the mouse globally and fire some useful events. Since this hook is low level and low level mouse hook doesn't get MouseClick and MouseDoubleClick messages it simulates these events.
I provided the 'Handled' property to 'MouseDown', 'MouseUp', 'MouseWheel' and 'MouseMove' event handlers. If you decide to set the 'Handled' property in the 'MouseUp' event then it is recommended to set it in the 'MouseDown' event as well for the application performance.

Warning! If you set the 'Handled' property in the mentioned events unconditionally than you might not be able to use the mouse. You can check the 'WindowsHookLib Demo Project' examples to see how you can condition the mouse handled process.

Class methods:

• InstallHook – Installs the mouse hook globally (has no parameters).
• RemoveHook – Removes the mouse hook (has no parameters).
• Dispose – Unhooks the mouse (if it is hooked) and frees the memory used by the component (has no parameters).
• SynthesizeMouseDown - Synthesizes a mouse down event system wide.
• SynthesizeMouseUp - Synthesizes a mouse up event system wide.
• SynthesizeMouseWheel - Synthesizes a mouse wheel event system wide.
• SynthesizeMouseMove - Synthesizes a mouse move event system wide.

Class properties:

• State – Gets the hook state.

Class events:

• StateChanged – Fires the event if the mouse hook is installed/uninstalled.
• MouseDown – Fires the event if the mouse button is down.
• MouseMove – Fires the event if the mouse is moved.
• MouseUp – Fires the event if the mouse button is up.
• MouseWheel – Fires the event if the mouse vertical/horizontal wheels are rotated.
• MouseClick – Fires the event if the mouse is clicked.
• MouseDoubleClick – Fires the event if the mouse is double-clicked.

KEYBOARD HOOK

The 'LLKeyboardHook' class from 'WindowsHookLib' can be use to hook the keyboard globally.

Class methods:

• InstallHook – Installs the keyboard hook globally (has no parameters).
• RemoveHook – Removes the keyboard hook (has no parameters).
• Dispose – Unhooks the keyboard (if it is hooked) and frees the memory used by the component (has no parameters).

Class properties:

• State – Gets the hook state.
• AltKeyDown – Gets a Boolean value indicating if the ALT key is down.
• CtrlKeyDown – Gets a Boolean value indicating if the CTRL key is down.
• ShiftKeyDown– Gets a Boolean value indicating if the SHIFT key is down.

Class events:

• StateChanged – Fires the event if the keyboard hook is installed/uninstalled.
• KeyDown – Fires the event if a keyboard button is down.
• KeyUp – Fires the event if the keyboard button is up.

CLIPBOARD HOOK

The 'ClipboardHook' class from 'WindowsHookLib' can be use to add a window to the clipboard chain and fire clipboard changed event.

Class methods:

• InstallHook – Adds a window to the clipboard chain (has no parameters).
• RemoveHook – Removes the window from the clipboard chain (has no parameters).
• Dispose – Removes the window from the clipboard chain and frees the memory used by the component (has no parameters).

Class properties:

• State – Gets the hook state.
• HWnd – Gets the hooked window handle.

Class events:

• StateChanged – Fires the event if the clipboard hook is installed/uninstalled.
• ClipboardChanged– Fires the event when the clipboard contents is changed (redrawn).

The code examples are in the demo project with comments. You can run the project and test the hooks before you use them. If you need the methods' discriptions, than you need to copy the 'WindowsHookLib.xml' file into your project folder too.
By the way, the mouse hook and the clipboard hook are used in the Easy Screen Shot tool app. You can see the main use of mouse hook when you capture an object (window, control, windows shortcut menus etc.) images. The clipboard hook is used to enable the clipboard captur button.

Update History:

Assembly Version 1.1.0.7
File Version 1.0.0.1

• Some internal changes.
• The namespace WindowsHookLib is changed to WindowsHook.

Assembly Version 1.1.1.0
File Version 1.0.0.4

• Minor internal improvements.

Download the latest version here

Quote:

---

Originally Posted by VBDT

This class is designed to hook the mouse globally and fire some useful events. The class uses Api functions to hook the mouse. Since this hook is low level and low level mouse hook doesn’t get MouseClick and MouseDoubleClick messages the class simulates these events.

---

Why do you say low level mouse hook doesnt capture click events? Sure it does. Not only single and double clicks, but also the delta value for scroll wheel. Your class to simulate this is not needed.

Quote:

---

Originally Posted by Traps

Why do you say low level mouse hook doesnt capture click events? Sure it does. Not only single and double clicks, but also the delta value for scroll wheel. Your class to simulate this is not needed.

---

Because it doesn’t!
This is the only windows massages that the window gets when it hooked low level

Quote:

---

wParam
[in] Specifies the identifier of the mouse message. This parameter can be one of the following messages: WM_LBUTTONDOWN, WM_LBUTTONUP, WM_MOUSEMOVE, WM_MOUSEWHEEL, WM_RBUTTONDOWN, or WM_RBUTTONUP.

---

MSDN

Quote:

---

Originally Posted by VBDT

Because it doesn’t!
This is the only windows massages that the window gets when it hooked low level
MSDN

---

Just debugged my hook program and your right!!! Looks like I could remove those from my select case statement for checking mouse messages. Cant believe I didnt notice that when I wrote my program.


Sorry. Maybe a MOD can delete our posts. Dont mean to junk up your thread. :wave:

How can i see the difference if im rolling up or down with my mouse?

the e.Delta is the same when i roll up as down. (always 424)

The Delta value is the value that the window gets by the WM_MOUSEWHEEL message. The value should be the same except that if you roll up it is positive and when you roll down it is negative.
The value should be 120 or -120 roll up and down respectivly. Now, if you want to get the total rolled value you can have a class level variable and add the delta value to it in the MouseWheel event. Here is an example:

vb Code:

Imports WindowsHookLib
 
Public Class Form1
 
    Dim WithEvents gmh As New LLMouseHook
    Dim delta As Integer
 
    Private Sub Form1_FormClosing(ByVal sender As Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles Me.FormClosing
        'Dispose the object (it will uninstall the hook first)
        Me.gmh.Dispose()
    End Sub
 
    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        Try
            'Install the mouse hook
            Me.gmh.InstallHook()
        Catch ex As Exception
            MessageBox.Show(ex.Message)
        End Try
    End Sub
 
    Private Sub gmh_MouseWheel(ByVal sender As Object, ByVal e As WindowsHookLib.MouseEventArgs) Handles gmh.MouseWheel
        'Add the delta value to the variable
        Me.delta += e.Delta
        Console.WriteLine(Me.delta)
    End Sub
End Class

Thanks for the code, it works great, except that it seems to return the same sender handle regardless of what is actually clicked.

Any ideas?

Quote:

---

Originally Posted by slk486

Thanks for the code, it works great, except that it seems to return the same sender handle regardless of what is actually clicked.

Any ideas?

---

What kind of control is it? My guess is that it is a User Control that has some controls in it. In this case the sender has the handle of the User Control not the controls that it includes.

Thanks for your quick reply :)

The app uses normal VB forms and a context menu opened from a notfyicon in the tray.

Even when i Click elsewhere on the desktop, the sender handle is the same..

The main form is hidden and only the tray icon is visible. when the user clicks the tray icon a context menu appears and from the context menu the user can open a form. It doesn't matter if I click the menu, the icon, the form or in any other (other apps) window on the desktop.

Really, that sounds weird. In the class I use the ‘WindowFromPoint’ Api function to get the handle of the control. If it gives the same handle for everything you click then there must be some problem with your project or with Visual Studio I am not sure.
Have you tried the demo I have posted? Does it work as it spouse to?
Also I would suggest you to install the Screen Shot application in my signature and try to capture objects for a test. The app uses this class to capture controls and when you move the mouse, a red rectangle is being drawn around the controls which were passable to do with the Api function I mentioned above.

OK...

The demo gave me the window full of buttons that I could navigate with the keyboard and find the correct 2, to unlock the mouse (no mouse movement at first, then no mouse clicking) - i believe that is the intended functionality?

The Screen Shot app was rather weird. First time i couldn't click anything, then all of a sudden a red border appeared around a window and I could capture window images but not click anything in the Screen shot menu (i can click the images and they appear pressed, but nothing happens). Second time I could capture the windows I clicked on - no red border however, and I couldn't click anything in the Screen shot menu - not even cancel capture.

Had to kill the process.

Could this have anything to do with the fact that I'm using Windows XP x64 or dual monitors?

Quote:

---

Originally Posted by slk486

OK...

The demo gave me the window full of buttons that I could navigate with the keyboard and find the correct 2, to unlock the mouse (no mouse movement at first, then no mouse clicking) - i believe that is the intended functionality?

The Screen Shot app was rather weird. First time i couldn't click anything, then all of a sudden a red border appeared around a window and I could capture window images but not click anything in the Screen shot menu (i can click the images and they appear pressed, but nothing happens). Second time I could capture the windows I clicked on - no red border however, and I couldn't click anything in the Screen shot menu - not even cancel capture.

Had to kill the process.

Could this have anything to do with the fact that I'm using Windows XP x64 or dual monitors?

---

In the demo at least you should be able to move the mouse inside the form and be able to click some not all the buttons. If you can’t then there has to be some problems with the fact that you mentioned. I am using xp too so that shouldn't be problem but i am not sure about x64 and dual monitors!

The Screen Shot app works great in my computer and the others I tested. The problem you are having is effecting to Screen Shot too.

One more suggestion, in the event that the sender is giving the same handle fore windows and controls use the ‘GetLastApiError’ function of the ‘GlobalMouseHook’ class to retrieve the last error accrued in the Api dlls and see what it says if there is one.

One more thing! I posted the dll file 'WindowsHook' that is basicly the same code except the dll gets the module handl by reflection instead of Api wich in your case it may have giving a wrong one. Also the MS documentation states that it must be in the dll.

Hello VBDT

I have a question regarding to your last post, saying "One more thing! I posted the dll file 'WindowsHook' that is basicly the same code except the dll gets the module handl by reflection instead of Api wich in your case it may have giving a wrong one. Also the MS documentation states that it must be in the dll.";

Is this the reason I cannot produce a single assembly (without WindowsHookLib.dll)? I've copy/pasted the files in WindowsHookLib to Test folder but it throws an exception at ghk.InstallHook.

Or do I miss something else?

Quote:

---

Originally Posted by meraydin

Hello VBDT

I have a question regarding to your last post, saying "One more thing! I posted the dll file 'WindowsHook' that is basicly the same code except the dll gets the module handl by reflection instead of Api wich in your case it may have giving a wrong one. Also the MS documentation states that it must be in the dll.";

Is this the reason I cannot produce a single assembly (without WindowsHookLib.dll)? I've copy/pasted the files in WindowsHookLib to Test folder but it throws an exception at ghk.InstallHook.

Or do I miss something else?

---

I mentioned it in the introduction in #1 post

Quote:

---

"Note you need to use the dll not the classes in your projects; otherwise they might not work correctly."

---

All you need to do is to copy the two files (WindowsHookLib.dll & WindowsHookLib.xml) in the "WindowsHookLib.zip" in to your project folder and add reference to the "WindowsHookLib.dll" file from your project and add "Imports WindowsHookLib" on top of your class or form.

How would one get the raw wparam and lparam? I need to 'copy' a wm_mousewheel in order to send it elsewhere but reconstructing the parameters from e.X, e.Y, e.Button etc seems kind of tricky.

Hi VBDT,
I was in need of a keyboard hook procedure, and this class is superior to anything I would have been able to come up with myself. So firstly, thanks for posting it.

If I many ask a few questions:

1.) In this class, you use the WH_KEYBOARD_LL hook for the keyboard. This hook is available only as a global hook, whereas the WH_KEYBOARD hook is available as a thread specific, or global - so at first glance, it sounds like the latter is a more versatile version. The help docs don't offer any information (at least initially) as to the difference. Are there any advantages to the _LL version?

2.) The docs say to use global hooks only when necessary. Could two thread-specific hooks be used in place of one global hook if an app involves two separate processes? (mine is a cad-like app with separate procs for menu and window).

Thanks very much,
Danny

Hi 5applerush,
1) I would say the only advantage I see is that the LL hook gets a keyboard message before any window, where else none LL hook gets the message when the window got the message and will process it. Honestly, I don’t see any reason for creating thread specific hook since with framework 2 maybe in earlier versions you can set the form’s KeyPreview property which will fire when a key is down or up regardless what control has the focus, which is similar to the thread specific hook. But there is no way to get the keyboard messages regardless what app has the focus unless using LL keyboard hook.

2) Yes, they could, you can do it the way I described above or you can write thread specific keyboard hook but then there is no good reason for it.

VBDT :)

Ahhh, I think I understand. At first I couldn't quite see the difference after reading over the descriptions of each on MSDN. After your post I read them again, and noticed that the callback procedure for LL returns much more information in wParam and lParam - namely the KBDLLHOOKSTRUCT. Is this accurate?

I also have a noob question: The amount of code in your module is much more extensive than any other examples of hooks that I've found. Everything seems to be set up quite formally. Is this the type of code that one writes when they wish to "productionize" their code? I've always wondered because I often see working examples of concepts where the author throws in a disclaimer like, "This isn't production code, but it works..."

Thanks,
Danny

Yes, I forgot to mention that LL hook returns a structure with the info. My component is based on the info values and they are very accurate.

As why my code Is more then others, simply because I covered every possible angle, also you might noticed that the component fires to additional events “Mouse Click” and “Mouse DoubleClick” which I have never seen in any other mouse hook example. Also I added some attributes to the methods and classes to make the component more professional. I just tried to make the component close to .net components as much as it is possible.
Did I have to apply this attributes? No, but I wanted to do it so that you can see how it is done. And yes, if you want to make a professional component then you should apply attributes to your methods and classes to make the componen as close to .net components as it is posible. The reason is that most of the developers are familiar with the .Net classes and methods and I think that they like to see components that behave the same way as in .Net (this includes naming, applying attributs etc.)

Thanks for the help VBDT. I'm out of reputation right now, but I'll certainly pass some along when I can! And thanks again for posting this excellent code.

Danny

Wonderful! Thank you very much

Im trying to use this in a C# project. Works fine.

...Except my project is whining for a signed assembly.

IS there anyway you can compile and send me signed version.

TIA

Quote:

---

Originally Posted by cablehead

Im trying to use this in a C# project. Works fine.

...Except my project is whining for a signed assembly.

IS there anyway you can compile and send me signed version.

TIA

---

Hi, I updated the WindwosHookLib with a signed assembly version. :) Pleas let me know if it works.

I managed to compile a signed version. Works great.

Now I need to hunt down info on wheel "ticks"...

I need to hold off on the wheel event until I can procress how many wheel turns there are before setting a value.

Thanks

Thanks for library and simple demo.

I'm trying to do like that thing :

vb Code:

Private Sub MouseHook_(ByVal sender As System.IntPtr, ByVal e As WindowsHookLib.MouseEventArgs) Handles MouseHook.MouseDown, MouseHook.MouseClick, MouseHook.MouseUp
        If Handle = MouseHook.MouseDown Then
            TextBox1.Text &= "MouseDown" & vbCrLf
        ElseIf Handle = MouseHook.MouseClick Then
            TextBox1.Text &= "MouseClick" & vbCrLf
        ElseIf Handle = MouseHook.MouseUp Then
            TextBox1.Text &= "MouseUp" & vbCrLf
        End If
    End Sub

That code just explain what i want.
Will be like that thing too :

Private Sub MouseHook_(ByVal sender As System.IntPtr, ByVal e As WindowsHookLib.MouseEventArgs) Handles MouseHook.MouseDown, MouseHook.MouseClick, MouseHook.MouseUp
TextBox1.Text &= Handle & vbCrLf
End Sub

But i can't figure out how can i do.

I have discovered that if there is a long time operation during event keydown the ALT ( may be other control key ) seems pressed in the next keydown event .
Code sample is more easy I change the demo KeyDown event adding a time consuming on ALT F2 .
If I press ALT-F2 the next F2 comes with ALT also if press only F2 without ALT.
If I press ALT alone the situation reset normal.

Here the piece of code I change

Private Sub KeyboardHook_KeyDown(ByVal sender As Object, ByVal e As WindowsHookLib.KeyEventArgs) Handles KeyboardHook.KeyDown

'Set the key down Handled property
e.Handled = Me.HandleKeyboardCheckBox.Checked
If e.KeyCode = Keys.F2 And e.Alt Then
Me.DisplayTextBox.AppendText(Environment.NewLine)
Me.DisplayTextBox.AppendText("===================== Sleep 1000")
System.Threading.Thread.Sleep(1000)
End If
.
.
.
I hope I have well explanied .

Quote:

---

Originally Posted by Lionsitaly

I have discovered that if there is a long time operation during event keydown the ALT ( may be other control key ) seems pressed in the next keydown event .
Code sample is more easy I change the demo KeyDown event adding a time consuming on ALT F2 .
If I press ALT-F2 the next F2 comes with ALT also if press only F2 without ALT.
If I press ALT alone the situation reset normal.

Here the piece of code I change

Private Sub KeyboardHook_KeyDown(ByVal sender As Object, ByVal e As WindowsHookLib.KeyEventArgs) Handles KeyboardHook.KeyDown

'Set the key down Handled property
e.Handled = Me.HandleKeyboardCheckBox.Checked
If e.KeyCode = Keys.F2 And e.Alt Then
Me.DisplayTextBox.AppendText(Environment.NewLine)
Me.DisplayTextBox.AppendText("===================== Sleep 1000")
System.Threading.Thread.Sleep(1000)
End If
.
.
.
I hope I have well explanied .

---

Hi Lionsitaly,

According to MS the global hook subs should not have long time operations. If they do then according to them windows pass the message to the other applications without waiting to return from the sub. In this case the sub is the keydown event handler. Anyways, I like to examine the problem and want to ask you for the exact steps to produce the problem.
Thanks VBDT.

ok many thanks for support !
I try !
Open change the event keydown in this way

Code:

---

  Private Sub gkh_KeyDown(ByVal sender As Object, ByVal e As WindowsHookLib.KeyEventArgs) Handles gkh.KeyDown

        'Set the key down Handled property
        e.Handled = Me.HandleKeyboardCheckBox.Checked
       If e.KeyCode = Keys.F2 And e.Alt Then
            Me.DisplayTextBox.AppendText("===================== Sleep 1000")
            System.Threading.Thread.Sleep(1000)
        End If        'Print the key down data
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("===================== KeyDown")
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Handled: " & e.Handled)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("KeyCode: " & e.KeyCode.ToString)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("KeyValue: " & e.KeyValue)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("KeyData: " & e.KeyData.ToString)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Alt: " & e.Alt)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Control: " & e.Control)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Shift: " & e.Shift)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Modifiers: " & e.Modifiers.ToString)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("===================== End KeyDown")

    End Sub

---

Now run the demo press ALT-F2 and is ok after press ALT-F1 and ALT is lost in keydata.
I hope to be clear ...
You can also contact me on msn Lions_italyAThotmail.com and skype lionsitaly, many thanks for the library and support !
:wave: Ciao from italy

Firstly, I'd like to thank VBDT for an excellent piece of code.

But, I've discovered a slightly embarassing typing error:
In the ClickCheckBox object, the text says "Press sh***it + C to click me" (disregard the ***, I've written it this way to avoid the automatic replacement) instead of "Press Shift + C to click me".

Also, GroupBox1's text is missing an 'e' in 'mouse'.

Quote:

---

Originally Posted by obi1kenobi

Firstly, I'd like to thank VBDT for an excellent piece of code.

But, I've discovered a slightly embarassing typing error:
In the ClickCheckBox object, the text says "Press sh***it + C to click me" (disregard the ***, I've written it this way to avoid the automatic replacement) instead of "Press Shift + C to click me".

Also, GroupBox1's text is missing an 'e' in 'mouse'.

---

:D Corrected; thanks
VBDT

Something weird is happening in my application:

When the mouse is hooked, upon right-clicking on a control, its context menu shows up normally, however the MouseDown event of that control doesn't fire.

When the mouse is not hooked, the context menu shows normally, AND the MouseDown event is fired.

IMHO, it must be connected to the MouseHook in some way. What do I do to fix this?

Quote:

---

Originally Posted by obi1kenobi

Something weird is happening in my application:

When the mouse is hooked, upon right-clicking on a control, its context menu shows up normally, however the MouseDown event of that control doesn't fire.

When the mouse is not hooked, the context menu shows normally, AND the MouseDown event is fired.

IMHO, it must be connected to the MouseHook in some way. What do I do to fix this?

---

Hi obi1kenobi, I tested the hook and I couldn’t find any problems with it. In general when you right click on a form that has a ContextMenuStrip the right click is not fired; this is a normal windows behavior. :)

Quote:

---

Originally Posted by VBDT

Hi obi1kenobi, I tested the hook and I couldn’t find any problems with it. In general when you right click on a form that has a ContextMenuStrip the right click is not fired; this is a normal windows behavior. :)

---

Strange, I rebuilt the project and now both the ContextMenuStrip is shown and the right click is fired. I don't get it... But, since we're talking about a Microsoft product, everything is possible...:bigyello:

Hey there,

I'm trying to use your dll file in a Windows Mobile 5.0 VB application, but when I try to load the application, this is the error message it gives me. "File or assembly name 'System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089', or one of its dependencies, was not found."

could you shed some light on this, perhaps?
Thanks

Try adding a reference to System.Windows.Forms in your project. (I'm not sure whether the assembly exists in the CF version...) Right-click the project, then select Properties, then the References tab and then press Add and select the System.Windows.Forms assembly.

Quote:

---

Originally Posted by Lionsitaly

ok many thanks for support !
I try !
Open change the event keydown in this way

Code:

---

  Private Sub gkh_KeyDown(ByVal sender As Object, ByVal e As WindowsHookLib.KeyEventArgs) Handles gkh.KeyDown

        'Set the key down Handled property
        e.Handled = Me.HandleKeyboardCheckBox.Checked
       If e.KeyCode = Keys.F2 And e.Alt Then
            Me.DisplayTextBox.AppendText("===================== Sleep 1000")
            System.Threading.Thread.Sleep(1000)
        End If        'Print the key down data
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("===================== KeyDown")
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Handled: " & e.Handled)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("KeyCode: " & e.KeyCode.ToString)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("KeyValue: " & e.KeyValue)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("KeyData: " & e.KeyData.ToString)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Alt: " & e.Alt)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Control: " & e.Control)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Shift: " & e.Shift)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("Modifiers: " & e.Modifiers.ToString)
        Me.DisplayTextBox.AppendText(Environment.NewLine)
        Me.DisplayTextBox.AppendText("===================== End KeyDown")

    End Sub

---

Now run the demo press ALT-F2 and is ok after press ALT-F1 and ALT is lost in keydata.
I hope to be clear ...
You can also contact me on msn Lions_italyAThotmail.com and skype lionsitaly, many thanks for the library and support !
:wave: Ciao from italy

---

Hi, do not use Dialog boxes or Thread sleep in the hook event subs.

how would i go about recompiling your DLL so that the e.keycode.tostring of backspace is {backspace}? i also want to do this for all the other non alphanumeric keycodes.

Quote:

---

Originally Posted by bagstoper

how would i go about recompiling your DLL so that the e.keycode.tostring of backspace is {backspace}? i also want to do this for all the other non alphanumeric keycodes.

---

Hi, that is a custom string and the hook doesn’t return value with that format. The only way is to handle the key event and format the string according to the key value return by the "e.KeyCode".

Ok i was afraid that was what i would have to do. but thanks anyways for the good keyboard, mouse, and clipboard hook.

Hi VBDT,

WindowsHookLib doesn't support the "Windows Key" as a modifier. Is this viable? Do you intend to develop that?

Thanks.:)