The most elegant way to encapsulate WinAPI callbacks inside a class [duplicate]

Answer 1

I doubt this is in any way elegant but, IMO, the easiest is to convert the address of a method of a class to a procedure address and pass it to the winapi. Sure, it's a hack, but the VCL does the very same with classes.MakeObjectInstance, if only for a specific construct.. See this question for a source for this kind of implementaion and some other, more OO ways to handle the situation.

Answer 2

You can use static keyword for that. But it's available only in new Delphi versions.

Like this:

type
  TMyThread = class
  private
    // ...

    class function ThreadProc(Param: Pointer): DWord; stdcall; static; // <- WinAPI call back

    function Execute: DWord; // <- actual callback
  public
    constructor Create;
    // ...
  end;

{ TMyThread }

constructor TMyThread.Create;
begin
  // ...
  FHandle := CreateThread(nil, 0, @ThreadProc, Self, 0, FID);
end;

class function TMyThread.ThreadProc(Param: Pointer): DWord;
begin
  Result := TMyThread(Param).Execute;
end;

function TMyThread.Execute: DWord;
begin
  MessageBox(0, 'Hello from thread', 'Information', MB_OK or MB_ICONINFORMATION);
  Result := 0;
end;

Here: ThreadProc is WinAPI callback routine. It requires to have some form of custom argument, where you can pass Self. It can not access instance members. That's why it's just a wrapper for real callback (Execute), which is part of class and can access its fields and methods.