Re: Time out in application - C# Discussion Boards

30-Nov-04 4:02

I need to implement a time-out feature in my Win 32 application developed in C#. I need to have some way that if there is not action on the application for say 10min it should ask for a re-login into the applications.

Help!!! how!!!!

Stefan Troschuetz30-Nov-04 4:45

30-Nov-04 4:45

At first you should declare a bool, which determines whether a re-login has to be done or not and gets checked at the beginning of each handling of user interaction.
Secondly start a timer, which switches the declared bool when elapsing, and reset it after each handling of an user interaction.
I think the Threading.Timer class will be suitable here.

A T I F1-Dec-04 23:53

1-Dec-04 23:53

This is not at all simple.. I have the application that has about 50 dialogs all over....and many many user interaction handlers.....Do you think I will have to add timer resetter in all the user interaction handlers....

Is there any way to block all messages going to an application....main window and all subwindows...

Stefan Troschuetz2-Dec-04 0:55

2-Dec-04 0:55

You could override the WndProc method of your main form or add a message filter to the message pump of your application by using Application.AddMessageFilter method.

A T I F2-Dec-04 19:48

2-Dec-04 19:48

I did exactly that. it works fine for the main application form but when ever there is a model dialog popup the filter does not work on that window.....any idea why

A T I F2-Dec-04 19:49

2-Dec-04 19:49

I did exactly that. it works fine for the main application form but when ever there is a model dialog popup the filter does not work on that window.....any idea why Confused | :confused:

Stefan Troschuetz2-Dec-04 21:34

2-Dec-04 21:34

Did you override the WndProc method or add a message filter?
Do you pass the instance of your main form to the model dialogs (ShowDialog(this))?

A T I F3-Dec-04 2:19

3-Dec-04 2:19

I used message filter.

I did not override the WndProc but I did override the PreProcessMessage of the main form and it is called before WndProc (but it seems specific to the form) - no luck . Cry | :((

I did use ShowDialog(this)) for the child dialog.

It seems that whenever we have a modal dialog other than the main form the events of the dialog goes directly to the dialog and not pass through the main form or application queue. Is this true? Confused | :confused:

Atif

Stefan Troschuetz3-Dec-04 2:35

3-Dec-04 2:35

I don't know exactly but here is my guess:
I read again the documentation for the Application.AddMessageFilter method and found the following: "Message filters are unique to a specific thread." So I maybe the modal dialog runs with its own UI thread and therefor its message aren't detected by the filter. In this case you'll have to add a filter for every dialog.
But as I said I'm not very sure about that, so open a new thread and gain from the knowledge of other CP's Smile | :)

A T I F5-Dec-04 19:55

5-Dec-04 19:55

I created another thread too...but it has not worked out yet...thanks a lot lot for all your help.

Stefan Troschuetz8-Dec-04 4:37

8-Dec-04 4:37

At first I want to apologize for the late answer.

In my previous post I didn't suggest that you create another thread, but rather that for the opened modal dialog a new UI thread is created. Today, I checked this theory and it's false. The number of threads of an application stays the same when you open a modal dialog.
So for me there is no obvious reason why the message filter didn't get notice of the messages for the modal dialog.
Maybe you open a new thread with this specific problem, as surely another CP is able to provide a solution Smile | :)

Re: System.Security.Cryptography.Xml

Stefan Troschuetz30-Nov-04 3:50

30-Nov-04 3:50

You should take a look at the MSDN topic for the type from the System.Security.Cryptography.Xml namespace that you want to use. At the bottom you find the information which dll contains this type. E.g. to use the System.Security.Cryptography.Xml.DataObject class you have to reference the System.Security.dll.