• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 685
  • Last Modified:

What events are triggered during a 'logoff'

Hi

What events are triggered when a user logs off from windows 2000/xp etc?

I have tried a test using the events below, but none of them seem to get triggered.

Thanks
Pete

procedure TForm1.FormClose(Sender: TObject; var Action: TCloseAction);
begin
debugMSG ('formclose');
showmessage('formclose');
end;

procedure TForm1.FormDestroy(Sender: TObject);
begin
debugMSG ('formdestroy');
showmessage('formdestroy');
end;

procedure TForm1.WMENDSESSION(var Msg: TMessage);
begin
debugMSG ('wmendsession');
showmessage('wmendsession');
end;
procedure TForm1.WMQUERYENDSESSION(var Msg: TMessage);
begin
debugMSG ('WMQUERYENDSESSION');
showmessage('WMQUERYENDSESSION');
end;
procedure TForm1.FormCloseQuery(Sender: TObject; var CanClose: Boolean);
begin
debugMSG ('FormCloseQuery');
end;
0
PeteMulford
Asked:
PeteMulford
  • 2
  • 2
2 Solutions
 
atul_parmarCommented:
Hi,

When user logs off you will receive WM_QUERYENDSESSION message. But I think you can not cought it while IDE is running (the reason might be that the IDE will receive the same message and terminate its process or debugger). To test it run the application outside the IDE.

the message should look like

procedure OnLogOff(var Msg : TMessage); message WM_QUERYENDSESSION;

procedure TForm1.OnLogOff(var Msg: TMessage);
begin
  ShowMessage('End Session');
  Msg.Result := 0; // This will stop the log off
end;
0
 
pcsentinelCommented:
you do get the endsession

trap it by

type TForm1 = class(TForm)
*************
    procedure WndProc(var Msg: TMessage); override;
private
********
public
*******
end;

procedure TForm1.WndProc(var Msg: TMessage);
//traps incoming messages to check for close events
begin
if Msg.Msg=WM_QueryEndSession then //Send Disconnect And Close Event to Clients
      begin
         >>>>Dosomethinghere
        inherited WndProc(Msg);
      end
      else
        inherited WndProc(Msg);
end;
0
 
PeteMulfordAuthor Commented:
Hi

Thank you,  I tried your suggestion with a small demo project, but that event doesnt seem to get triggered either :( I'm testing it on a win 2000 client pc connected to a windows 2000 server based network. The pc I'm testing it on does not have the IDE installed. I also noticed that it 'logs off' very quickly, not sure if thats a network setting, but shall investigate.

My code is:

unit Unit1;

interface

uses
  Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms,
  Dialogs;

type
  TForm1 = class(TForm)
  private
    procedure OnLogOff(var Msg : TMessage); message WM_QUERYENDSESSION;
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form1: TForm1;

implementation

{$R *.dfm}
procedure debugMSG(msg:string);
const
  FileName = 'c:\closeEvents.txt';
var
  F: TextFile;
begin
  AssignFile(f,FileName);
 if FileExists(FileName) then Append(f)
 else
    Rewrite(f);
try  writeln(f,DateTimeToStr(Now)+':'+msg);
except windows.Beep(200,50);
end;
//  ShowMessage(DateTimeToStr(Now));
  CloseFile(f);
end;

procedure TForm1.OnLogOff(var Msg: TMessage);
begin
  debugMSG ('OnLogOff');
  ShowMessage('OnLogOff');
  Msg.Result := 0; // This will stop the log off
end;

end.
0
 
atul_parmarCommented:
Tested on XP. it created the 'c:\closeEvents.txt' file with following content and did not log off

26/06/2006 1:40:32 PM:OnLogOff
0
 
PeteMulfordAuthor Commented:
Many thanks to both of you. Both solutions actually work, seemingly equally well, it was another application causing my problems by forcing a loggoff.

Pete

 
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now