First is a question:
How to progmatically close MessageDlg ?
------------------------------------------------------------------------------------

Second is an observation / bug.

I provide a warning before logging out user. Whilst testing the functionality I just noticed that upon setting the timeout to the same value it was previously it does not work the second time.

procedure Tfrm1.AppOnIdleWarningEvent (Sender: TObject);
begin
ShowMessage('Ahhh!');
 Application.IdleTimeout := 6; //300;
 Application.OnIdle := AppOnIdleLogoutEvent;

 MessageDlg('You will be disconnected soon. Stay connected ?', 'Inactivity detected',
     mtConfirmation, [mbYes,mbNo], mbNo, TimeoutWarning, True);
end;

procedure Tfrm1.AppOnIdleLogoutEvent (Sender: TObject);
begin
ShowMessage('Hmmmmm!');
 LogoutNow;
end;

procedure Tfrm1.CheckTimeoutWarning(DlgResult: TModalResult);
begin
 if (DlgResult = mrNo) then
   LogoutNow
 else
   SetAppTimeout;
end;

procedure Tfrm1.SetAppTimeout;
begin
 Application.IdleTimeout := 5; //600;
 Application.OnIdle := AppOnIdleWarningEvent;
end;

<< How to progmatically close MessageDlg ? >>

You can't.  If you want that level of control, then you should create your own message dialog form (use TMessageDialog as the ancestor class instead of TForm).

<< I provide a warning before logging out user. Whilst testing the functionality I just noticed that upon setting the timeout to the same value it was previously it does not work the second time. >>

The OnIdle event is a one-shot deal. Once it fires, it won't fire again until any mouse/touch/keyboard events occur and it starts the countdown again.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> The OnIdle event is a one-shot deal. Once it fires, it won't fire
> again until any mouse/touch/keyboard events occur and it starts the
> countdown again.

That's a detail that might be worth putting in the manual as it could
be handy to know. It is sort of obvious, but also not.

--

Matthew Jones

<< The OnIdle event is a one-shot deal. Once it fires, it won't fire again until any mouse/touch/keyboard events occur and it starts the countdown again. >>

Tim:
In the sample code I gave above, both should be at '5' for example. However, the code works with different times set. So, when I change the second one to say '10' seconds, it works. I can live with that. Just wanted to point it out in case others came across this issue and were searching on it.

Matthew,

<< That's a detail that might be worth putting in the manual as it could be handy to know. It is sort of obvious, but also not. >>

I updated the docs to reflect this.

Tim Young
Elevate Software
www.elevatesoft.com