🚀 go-pugleaf

> > I think it doesn't matter.
>
> Well, it does, because the coding is different depending on which approach
> you take.

Maybe I picked the wrong english term.
What I wanted to say is that I have no preference
which route to go.

> What I do in that situation is to modify the service's WinMain() function
> directly.  When I want to run as a service, I let the default service code
> execute.  When I want to run as a normal application, I simply bypass the
> default code and run my normal code instead.  For example:
<snip>

Thank's very much for the example.
I will give it a try.

> > AFAIK TThreads create one for synchronisation
> > with the main thread.
>
> That is not true, TThread does not have a window handle at all.  It merely
> posts a message to the TApplication's Handle instead, and then

Looking at the source tells me something different at least for BCB5.
IIRC this has changed for BCB6.

procedure AddThread;
  function AllocateWindow: HWND;
  var
    TempClass: TWndClass;
    ClassRegistered: Boolean;
  begin
    ThreadWindowClass.hInstance := HInstance;
    ClassRegistered := GetClassInfo(HInstance,
ThreadWindowClass.lpszClassName,
      TempClass);
    if not ClassRegistered or (TempClass.lpfnWndProc <> @ThreadWndProc) then
    begin
      if ClassRegistered then
        Windows.UnregisterClass(ThreadWindowClass.lpszClassName, HInstance);
      Windows.RegisterClass(ThreadWindowClass);
    end;
    Result := CreateWindow(ThreadWindowClass.lpszClassName, '', 0,
      0, 0, 0, 0, 0, 0, HInstance, nil);
  end;

procedure TThread.Synchronize(Method: TThreadMethod);
begin
  FSynchronizeException := nil;
  FMethod := Method;
  SendMessage(ThreadWindow, CM_EXECPROC, 0, Longint(Self));
  if Assigned(FSynchronizeException) then raise FSynchronizeException;
end;

Regards,
Frank.