Question

How to write a callback method in delphi dll to a delphi client app

Asked by: ddideveloper

I am trying to write a delphi dll and a delphi client that will load the dll and have the dll call a method in the client. so far i have my client and dll are able to share data via a memory map without any problems. Now I want to write a method in the client that gets called by the dll if a certain event occurs.
I added a variable to my memory map structure to hold a pointer to the client method. The dll then checks to see if that variable is Assigned() then it calls it passing some variables. This is actually working so long as my client application never loses focus. If I ever click on another application, say windows explorer or something, then the dll stops working all together. By not working it does not appear to update the memory map or call the callback method either.
By the way I am using Delphi 7 and running on Windows XP.

code snippet from dll
------------
type
  TKeyboardEvent = procedure(Code: integer; wParam: integer; lParam: integer); stdcall ;
 
 PHookRec = ^THookRec;
 THookRec = packed record
   KeyboardEvent      : TKeyboardEvent ;
   TheHookHandle      : HHOOK;
   TheAppWinHandle    : HWND;
   TheCtrlWinHandle   : HWND;
   TheKeyCount        : DWORD;
   KeyChar            : Char ;
 end;
 
....
in one of the methods in dll i have thie following lines of code
 
 if Assigned(lpHookRec^.KeyboardEvent) then
  TKeyboardEvent(lpHookRec^.KeyboardEvent)(Code, wParam, lParam) ;
 
-------------------------------
code snippets from client
------------------------------
type
  TKeyboardEvent = procedure(Code: integer; wParam: integer; lParam: integer); stdcall ;
 
<more code here>
 
  procedure KeyboardEvent(Code: integer; wParam: integer; lParam: integer); stdcall ;
 
implementation
 
{$R *.DFM}
 
// The record type filled in by the dll
type THookRec = packed record
  KeyboardEvent     : TKeyboardEvent ;
  TheHookHandle     : HHOOK;
  TheAppWinHandle   : HWND;
  TheCtrlWinHandle  : HWND;
  TheKeyCount       : DWORD;
  KeyChar           : Char ;
end;
type PHookRec = ^THookRec;
 
<in my client after the dll is loaded and memory map established...>
         lpHookRec^.KeyboardEvent := @KeyboardEvent ;

                                  
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:

Select allOpen in new window

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

  • Plus...
  • 30 Day FREE access, no risk, no obligation
  • Collaborate with the world's top tech experts
  • Unlimited access to our exclusive solution database
  • Never be left without tech help again

Subscribe Now

Asked On
2009-08-27 at 16:54:44ID24688508
Tags

delphi dll callback method

Topics

Delphi Components

,

Delphi Programming

Participating Experts
1
Points
500
Comments
7

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

  • "The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
  • "Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
  • "Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Screenshot of Experts Exchange Knowledgebase

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Screenshot of an Article

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Screenshot of Experts Exchange Knowledgebase

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Related Solutions

  1. C++ DLL Callback conversion to Delphi 5.0
    Whew. I'm plowing through using functions in a C++ DLL in a Delphi 5.0 and, whilst making headway, I'm so NOT a C developer and need help! Here's the latest one: Some callbacks are needed to be set. I'm not to familiar with the whole concept of callbacks, which doesn't help ...
  2. Callback functions!
    My delphi program call a function from a Dll and pass as parameter a pointer to a callback function. The dll call that function.All works great until here but here i get with the problem. In that callback function i have to reffer to some global data of my delphi Program and ...
  3. How to implement a callback in a Delphi dll
    I have created a dll using Delphi. One of the functions in the dll accepts a callback function pointer. When I call it from VC++, passing in the address of the callback function, it crashes. Here's the relevant code: Delphi: ============== exports SetCallBack name ...
  4. Delphi callback to a c++ dll (Function pointers ?)
    I am a Java programmer that is writing a c++ dll wrapper for a delphi dll so I can use JNI. It is all pretty messed up and I have everything working except for a few functions that take a "procedure" as an argument and then callback this procedure. The Delphi docu...
  5. Using a C++ DLL with callback function in Delphi
    Hi I need some help in using a C++ DLL with a callback function in Delphi 6.0 and the details are: Here are the C prototypes and implementation examples: void (*type_MyCallBack) (bool, bool, unsigned long, char*, long ) bool InitialiseCallBack(type_myCallBack) An example o...
  6. Callback
    I am trying to call a routine from a dll. I can call the routine correctly, but one of the parameters is a callback and whenever the callback is triggered I get an error. The function in the dll is defined like: function LaunchPrdCallIrs(ThisHostInd:Integer; ThisEfin:PChar...

Free Tech Articles

  1. WARNING: 5 Reasons why you should NEVER fix a computer for free.
    It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
  2. SCCM OSD Basic troubleshooting
    SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
  3. Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
    This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
  4. Create a Win7 Gadget
    This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
  5. Outlook continually prompting for username and password
    There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
  6. Backup Exchange 2010 Information Store using Windows Backup
    There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

  1. Avoiding Bugs in Microsoft Access
    Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
  2. Top 10 Best New Features in Visio 2010
    Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
  3. IT Consultant Business Secrets Revealed
    Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
  4. Disaster Recovery and Business Continuity
    Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
  5. Organize Your Visio Diagrams with Containers and Lists
    Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
  6. How to Us Objects, Properties, Events and Methods in Microsoft Access
    Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

 

by: MvanderKooijPosted on 2009-08-28 at 01:51:05ID: 25205804

Hi ddideveloper,

Why are you using memorymapped files while you are in the same proces?
An other way is to add a callback setter to the dll:

DLL:
interface
procedure SetKeyboardEventCallback(event: TKeyboardEvent);

implementation

var
  gl_event: TKeyboardEvent;
exports
  SetKeyboardEventCallback;

procedure SetKeyboardEventCallback(event: TKeyboardEvent);
begin
  gl_event := event;
end;

Application:

interface
procedure SetKeyboardEventCallback(event: TKeyboardEvent);

implementation

function SetKeyboardEventCallback; external 'dllname.dll' name 'SetKeyboardEventCallback';

Now you can call SetKeyboardEventCallback from the application to start and stop the calling from the dll


 

by: ddideveloperPosted on 2009-08-28 at 08:53:32ID: 25208919

OK well after thinking about your reply it made me decide to rethink my problem. I am not sure what to do now because my original question is not really where the problem lies, the call back works unless I switch focus to another app, so I dont know if I need to close this question and start another one. But just incase you are familar enough with DLLs I will describe my real problem. I tried to attach my source files but EE wouldnt let me so I will paste it below.
I created a test DLL (KBHook.dll) to create a global keyboard hook and declare a TStringList to save keys to a text file C:\Temp\KeyList.txt. The client app just loads the dll, calls the method in dll to set the hook or unset the hook. Then the client app has a button to load the file that the dll writes into a memo control. Here is what I found. When I run the client app and load the dll and call the set hook method for the dll then I type "ABC" with my client app having focus, I can click the button on the client and "ABC" is loaded in from the file. But if I switch to NotePad and type "XYZ" then click back to the client app and load the file I get "XYZ" but the "ABC" is now missing so it is like another instance of the dll was loaded for each process. Also If I go back to my client app and type "HHH" then load the file into the memo I see "ABCHHH". I dont understand how multiple instances are being loaded into memory. I would have thought there would only ever be one instance and the string list would contain the keys from all apps into a single list. There is obviously multiple copies of the string list. This explains why I had my original problem because the variable that held the pointer to the callback method was a new variable when I switched to another app. Also after I close the client app then NotePad generates an error about unable to write memory. I was thinking maybe this is why I need to create a memory map file but not sure how it work with something like a string list.

code for dll
==========================
library KBHook;
 
uses
  ShareMem, Windows, Classes, Messages, SysUtils;
 
var
  HookHandle: HHOOK;
  KeyList: TStringList ;
 
function KeyBoardProc(Code: integer; wParam: integer; lParam: integer): integer; stdcall;
var
  KeyUp: boolean;
begin
  Result := 0;
 
  case Code of
    HC_ACTION:
      begin
        KeyUp := ((lParam AND (1 shl 31)) <> 0);
        if (KeyUp) then begin
          if (wParam >= 32) and (wParam <= 126) then begin
            KeyList.Text := KeyList.Text + Char(wParam) ;
            KeyList.SaveToFile('C:\Temp\KeyList.txt') ;
          end ;
        end;
        Result := 0;
      end;
    HC_NOREMOVE:
      begin
        Result := 0;
        Exit;
      end;
  end;
 
  if (Code < 0) then
    Result := CallNextHookEx(HookHandle, Code, wParam, lParam);
end;
 
procedure StartKeyBoardHook ; stdcall;
begin
  HookHandle := SetWindowsHookEx(WH_KEYBOARD, @KeyBoardProc, hInstance, 0);
end;
 
 
procedure StopKeyBoardHook ; stdcall;
begin
 if (HookHandle <> 0) then
   if UnHookWindowsHookEx(HookHandle) then
     HookHandle := 0;
end;
 
procedure DllEntryPoint(dwReason : DWORD);
begin
  case dwReason of
    Dll_Process_Attach:
      begin
        KeyList := TStringList.Create ;
      end;
    Dll_Process_Detach:
      begin
        KeyList.Free ;
      end;
  end;
end;
 
exports
 StartKeyBoardHook name 'STARTKEYBOARDHOOK',
 StopKeyBoardHook name 'STOPKEYBOARDHOOK';
 
begin
 DLLProc := @DllEntryPoint;
 DllEntryPoint(Dll_Process_Attach);
end.
==========================
 
client app code
 
================================
unit fmClientApp;
 
interface
 
uses
  Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
  Dialogs, StdCtrls;
 
type
  TStartKeyBoardHook = procedure stdcall;
  TStopKeyBoardHook = procedure stdcall;
 
  TfrmClientApp = class(TForm)
    btnSetHook: TButton;
    btnRemoveHook: TButton;
    Memo1: TMemo;
    btnLoadKeys: TButton;
    procedure btnSetHookClick(Sender: TObject);
    procedure FormCreate(Sender: TObject);
    procedure FormDestroy(Sender: TObject);
    procedure btnRemoveHookClick(Sender: TObject);
    procedure btnLoadKeysClick(Sender: TObject);
  private
    hDLL: THandle ;
    StartKeyBoardHook : TStartKeyBoardHook;
    StopKeyBoardHook : TStopKeyBoardHook;
  public
  end;
 
var
  frmClientApp: TfrmClientApp;
 
implementation
 
{$R *.dfm}
 
procedure TfrmClientApp.FormCreate(Sender: TObject);
begin
  hDLL := LoadLibrary('KBHook.DLL');
  if (hDLL <> 0) then begin
    @StartKeyBoardHook := GetProcAddress(hDLL, 'STARTKEYBOARDHOOK');
    @StopKeyBoardHook :=  GetProcAddress(hDLL, 'STOPKEYBOARDHOOK');
  end ;
end;
 
procedure TfrmClientApp.FormDestroy(Sender: TObject);
begin
  FreeLibrary(hDLL);
end;
 
procedure TfrmClientApp.btnSetHookClick(Sender: TObject);
begin
  StartKeyBoardHook;
end;
 
procedure TfrmClientApp.btnRemoveHookClick(Sender: TObject);
begin
  StopKeyBoardHook;
end;
 
procedure TfrmClientApp.btnLoadKeysClick(Sender: TObject);
begin
  Memo1.Lines.LoadFromFile('C:\Temp\KeyList.txt') ;
end;
 
end.
========================================

                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:

Select allOpen in new window

 

by: MvanderKooijPosted on 2009-08-28 at 14:10:27ID: 25211563

Well hooking works as follows:

An proces starts hooking, using a dll
This dll is then loaded into each process. But the instances do not share memory. As long as theproces that started the hooking is running the hook dll is used. When the 'start' proces stops it releases the hooks.

You could try to attach to the output file for each input. Just make sure that you output the text when an process looses focus.
just use writeln to an output file and open/close it as quickly as possible. That will probably work because the input from the keyboard will be handled by only one process at the time.

 

by: ddideveloperPosted on 2009-08-28 at 15:33:36ID: 25212067

so that explains why I could not do a call back then. if my client app passes a pointer to the client side method to the instance of the dll it loaded then all other instances of the dll has no pointer assigned to them. I would say for sure that is worth atleast some of the points but certainly there has to be a way to pass the call back pointer to all instances is there not? Plus I would then assume I should make the callback method thread safe.
And what is causing the other applications to through an exception when I disconnect the dll from the client app. I attached an error from window explorer but all other apps through the same error.

 

by: MvanderKooijPosted on 2009-08-28 at 16:01:03ID: 25212169

Passing pointers between dll's in multiple processes is not going to work. Each process can load a dll at a different locations into memory) Or at least the virtual memory adress is different, even if the actual dll is located at one place at a physical memory adress.

I think you have some options here:
- write each character, or serie of characters as quickly as you can to a file (and keep it locked as short as possible)
- use a memory mapped file for the storage of the text, make the process that writes the file responsible for writing it to a file. broadcast the new location in the memory mapped file to all other dll's
- use sendmessage to send the captured key to the main app. Create a way that each dll instance get's a windows handle of the hooking starting process and send the messages to it. Make the start process responsible for keeping track of the keys.

(i would go for the last option)

 

by: ddideveloperPosted on 2009-08-28 at 16:16:59ID: 25212244

I think you are onto something here.
If I use the last method and want to send messages back to the calling client app then how do I pass the windows handle of the client app to all the instances of the dll that get loaded.
Also I commented everything in the dll's KeyBoardProc method except the line "Result := 0" and it still causes all other apps to crash. They crash only if I load the dll and set the hook, then if I set focus to any other application and press at least one key. Then when I go back to the client app and unload the dll it generates that error. So until I figure that out no method of reporting the keys is going to work.

 

by: MvanderKooijPosted on 2009-08-29 at 02:53:39ID: 25213527

I have created a running example feel free to tweak :-)

It will send keys from all applications to the memo on the form.
A thing to optimize:
I've used a BroadcastSystemMessage to send the key to all windows, this could be a postmessage if you use enumwindows to find the form in the application

DLL:
------------------
library KBHook;
 
uses
  {ShareMem, }Windows, Classes, Messages, SysUtils;
 
var
  HookHandle: HHOOK;
  uiWM_CapturedKeyboardKey: UINT;
 
 
function KeyBoardProc(Code: integer; wParam: integer; lParam: integer): integer; stdcall;
var
  KeyUp: boolean;
  dwRecipients: DWORD;
begin
  Result := 0;
 
  case Code of
    HC_ACTION:
      begin
        KeyUp := ((lParam AND (1 shl 31)) <> 0);
        if (KeyUp) then begin
          dwRecipients := BSM_APPLICATIONS;
//          if (wParam >= 32) and (wParam <= 126) then begin
             BroadcastSystemMessage(BSF_POSTMESSAGE, @dwRecipients, uiWM_CapturedKeyboardKey, wParam, lParam);
//            KeyList.Text := KeyList.Text + Char(wParam) ;
//            KeyList.SaveToFile('C:\Temp\KeyList.txt') ;
//          end ;
        end;
        Result := 0;
      end;
    HC_NOREMOVE:
      begin
        Result := 0;
        Exit;
      end;
  end;
 
  if (Code < 0) then
    Result := CallNextHookEx(HookHandle, Code, wParam, lParam);
end;
 
procedure StartKeyBoardHook ; stdcall;
begin
  HookHandle := SetWindowsHookEx(WH_KEYBOARD, @KeyBoardProc, hInstance, 0);
end;
 
 
procedure StopKeyBoardHook ; stdcall;
begin
 if (HookHandle <> 0) then
   if UnHookWindowsHookEx(HookHandle) then
     HookHandle := 0;
end;
 
function IsKeyboardHooked: boolean; stdcall;
begin
  Result := HookHandle <> 0;
end;
 
procedure DllEntryPoint(dwReason : DWORD);
begin
  case dwReason of
    Dll_Process_Attach:
      begin
        uiWM_CapturedKeyboardKey := RegisterWindowMessage('KBHook_WM_CapturedKeyboardKey');
//        KeyList := TStringList.Create ;
      end;
    Dll_Process_Detach:
      begin
//        KeyList.Free ;
      end;
  end;
end;
 
exports
 StartKeyBoardHook name 'STARTKEYBOARDHOOK',
 StopKeyBoardHook name 'STOPKEYBOARDHOOK',
 IsKeyboardHooked name 'ISKEYBOARDHOOKED';
 
begin
 DLLProc := @DllEntryPoint;
 DllEntryPoint(Dll_Process_Attach);
end.
 
Application:
------------------
unit UfrmMain;
 
interface
 
uses
  Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
  Dialogs, StdCtrls;
 
type
  TStartKeyBoardHook = procedure stdcall;
  TStopKeyBoardHook = procedure stdcall;
  TIsKeyboardHooked = function: boolean stdcall;
 
  TfrmKBHookLoader = class(TForm)
    btnHook: TButton;
    btnUnHook: TButton;
    mmoKeys: TMemo;
    btnClose: TButton;
    procedure FormCreate(Sender: TObject);
    procedure FormDestroy(Sender: TObject);
    procedure btnHookClick(Sender: TObject);
    procedure btnUnHookClick(Sender: TObject);
    procedure FormShow(Sender: TObject);
    procedure btnCloseClick(Sender: TObject);
  private
    hDLL: THandle;
    StartKeyBoardHook: TStartKeyBoardHook;
    StopKeyBoardHook: TStopKeyBoardHook;
    IsKeyboardHooked: TIsKeyboardHooked;
    { Private declarations }
  protected
    procedure WndProc(var Message: TMessage); override;
  public
    procedure SetEnabledStates;
    { Public declarations }
  end;
 
var
  frmKBHookLoader: TfrmKBHookLoader;
  uiWM_CapturedKeyboardKey: UINT;
 
implementation
 
{$R *.dfm}
 
procedure TfrmKBHookLoader.btnCloseClick(Sender: TObject);
begin
  if Assigned(IsKeyboardHooked) then begin
    if IsKeyboardHooked() then begin
      if Assigned(StopKeyBoardHook) then begin
        StopKeyBoardHook();
      end;
    end;
  end;
  Close;
end;
 
procedure TfrmKBHookLoader.btnHookClick(Sender: TObject);
begin
  if Assigned(StartKeyBoardHook) then
    StartKeyBoardHook();
  SetEnabledStates;
end;
 
procedure TfrmKBHookLoader.btnUnHookClick(Sender: TObject);
begin
  if Assigned(StopKeyBoardHook) then
    StopKeyBoardHook();
  SetEnabledStates;
end;
 
procedure TfrmKBHookLoader.FormCreate(Sender: TObject);
begin
  hDLL := LoadLibrary('KBHook.DLL');
  if (hDLL <> 0) then begin
    @StartKeyBoardHook := GetProcAddress(hDLL, 'STARTKEYBOARDHOOK');
    @StopKeyBoardHook :=  GetProcAddress(hDLL, 'STOPKEYBOARDHOOK');
    @IsKeyboardHooked :=  GetProcAddress(hDLL, 'ISKEYBOARDHOOKED');
  end;
  uiWM_CapturedKeyboardKey := RegisterWindowMessage('KBHook_WM_CapturedKeyboardKey')
end;
 
procedure TfrmKBHookLoader.FormDestroy(Sender: TObject);
begin
  FreeLibrary(hDLL);
end;
 
procedure TfrmKBHookLoader.FormShow(Sender: TObject);
begin
  SetEnabledStates;
end;
 
procedure TfrmKBHookLoader.SetEnabledStates;
var
  blnIsHooked: boolean;
begin
  if Assigned(IsKeyboardHooked) then begin
    blnIsHooked := IsKeyboardHooked();
    btnHook.Enabled := not blnIsHooked;
    btnUnHook.Enabled := blnIsHooked;
  end else begin
    btnHook.Enabled := False;
    btnUnHook.Enabled := False;
  end;
end;
 
procedure TfrmKBHookLoader.WndProc(var Message: TMessage);
begin
  if Message.Msg = uiWM_CapturedKeyboardKey then begin
    if (Message.wParam >= 32) and (Message.wParam <= 126) then begin
      mmoKeys.Lines.Text := mmoKeys.Lines.Text + char(Message.wParam);
    end else if Message.wParam = 13 then begin
      mmoKeys.Lines.Text := mmoKeys.Lines.Text + #13;
    end;
  end else
    inherited;
end;
 
end.
                                              
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:

Select allOpen in new window

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...