Control.Invoke with ShowDialog

[Chris Dunaway]

I have a main form with a "lock" button. When the lock button is
clicked, another form is shown using ShowDialog(this ). The user must
enter their PIN on this form to close it and resume the main app.
Because it is showing using ShowDialog(this ), the main form in the back
cannot be used until the user clears the login form. A feature was
added to the app to automatically lock the app after a period of
inactivity. This uses a timer. If the lock routine is called from the
timer, then I get an illegal cross thread operation exception,
presumably because the lock form is shown on another thread and passing
in "this" causes the exception. Here is the code for the lock routine,
the button click, and the idle timer:

void _idleTimer_Elap sed(object sender,
System.Timers.E lapsedEventArgs e)
{
lockRegister();
_idleTimer.Star t();
}

private void btnLock_Click(o bject sender, EventArgs e)
{
_idleTimer.Stop ();
lockRegister();
_idleTimer.Star t();
}

private void lockProgram()
{
LoginForm frmLogin = new LoginForm(_user , "Program
Locked!", true);

frmLogin.StartP osition = FormStartPositi on.Manual;
frmLogin.Size = this.pnlDataEnt ry.Size;
frmLogin.Locati on = this.pnlDataEnt ry.Location;

frmLogin.ShowDi alog(this);
if (frmLogin.Dialo gResult == DialogResult.OK )
_user = frmLogin.Curren tUser;
else
this.Close();
}

To summarize:

1. If the program is locked using the Lock button, it works correctly.
2. If the timer elapses, I get the cross thread exception.

I know I can check the InvokeRequired to see if I need control invoke,
but how do I pass "this" to the ShowDialog method in that instance so
that the main form cannot be accessed until the dialog is closed?

Thanks,

Chris

[Tom Spink]

Chris Dunaway wrote:

I have a main form with a "lock" button. When the lock button is
clicked, another form is shown using ShowDialog(this ). The user must
enter their PIN on this form to close it and resume the main app.
Because it is showing using ShowDialog(this ), the main form in the back
cannot be used until the user clears the login form. A feature was
added to the app to automatically lock the app after a period of
inactivity. This uses a timer. If the lock routine is called from the
timer, then I get an illegal cross thread operation exception,
presumably because the lock form is shown on another thread and passing
in "this" causes the exception. Here is the code for the lock routine,
the button click, and the idle timer:

<snippedy-do-daah>

Hi Chris, change your _idleTimer_Elap sed function to this:

///
void _idleTimer_Elap sed ( object sender, System.Timers.E lapsedEventArgs e )
{
this.Invoke( new SafeLockRegiste rDelegate( SafeLockRegiste r ) );
_idleTimer.Star t();
}

private delegate void SafeLockRegiste rDelegate ( );
private void SafeLockRegiste r ( )
{
lockRegister();
}
///

That should do the trick!

--
Hope this helps,
Tom Spink

[Stoitcho Goutsev \(100\)]

Chris,

1. You can use System.Windows. Forms.Timer. It is not very accurate, but the
event handler is executed in the main UI thread and you won't run into this
threading probelms.

2. You can also use System.Timer.Ti mer also. Set the timer's
SynchronizingOb ject to reference one of your controls or the form itself and
then the timer will marshal its Elapsed event to the UI thread and you again
won't run to this problem. From what I see you use exactly this, just need
to set this property; no need of Control.Invoke in this case.
3. If you prefer to use ControlInvoke make sure that you

you create the PIN dialog form in the method that is marshaled using
Control.Invoke. The form needs to be created in the UI thread, it is not
only the ShowDialog that has to be to be called by the UI thread.
--
HTH
Stoitcho Goutsev (100)

"Chris Dunaway" <du******@gmail .com> wrote in message
news:11******** *************@r 2g2000cwb.googl egroups.com...

I have a main form with a "lock" button. When the lock button is
clicked, another form is shown using ShowDialog(this ). The user must
enter their PIN on this form to close it and resume the main app.
Because it is showing using ShowDialog(this ), the main form in the back
cannot be used until the user clears the login form. A feature was
added to the app to automatically lock the app after a period of
inactivity. This uses a timer. If the lock routine is called from the
timer, then I get an illegal cross thread operation exception,
presumably because the lock form is shown on another thread and passing
in "this" causes the exception. Here is the code for the lock routine,
the button click, and the idle timer:

void _idleTimer_Elap sed(object sender,
System.Timers.E lapsedEventArgs e)
{
lockRegister();
_idleTimer.Star t();
}

private void btnLock_Click(o bject sender, EventArgs e)
{
_idleTimer.Stop ();
lockRegister();
_idleTimer.Star t();
}

private void lockProgram()
{
LoginForm frmLogin = new LoginForm(_user , "Program
Locked!", true);

frmLogin.StartP osition = FormStartPositi on.Manual;
frmLogin.Size = this.pnlDataEnt ry.Size;
frmLogin.Locati on = this.pnlDataEnt ry.Location;

frmLogin.ShowDi alog(this);
if (frmLogin.Dialo gResult == DialogResult.OK )
_user = frmLogin.Curren tUser;
else
this.Close();
}

To summarize:

1. If the program is locked using the Lock button, it works correctly.
2. If the timer elapses, I get the cross thread exception.

I know I can check the InvokeRequired to see if I need control invoke,
but how do I pass "this" to the ShowDialog method in that instance so
that the main form cannot be accessed until the dialog is closed?

Thanks,

Chris

[Chris Dunaway]

Thanks Tom, Stoitcho for the suggestions.

What I ended up doing was using a delegate:

private delegate void lockdelegate();

I then changed my timer event as follows:

void _idleTimer_Elap sed(object sender,
System.Timers.E lapsedEventArgs e)
{
//marshal the call to the correct thread using a delegate
this.Invoke(new lockdelegate(lo ckRegister));
_idleTimer.Star t();
}

This way, the lock method is executed on the UI thread.

Thanks,

Chris

[Stoitcho Goutsev \(100\)]

Chris,

I want to say it one more time in case you missed it in my post. If you use
System.Timers.T imer class (component) you don't need to marshall the call by
your self. You can let the timer do it for you - just set the
SynchronizingOb ject property to reference a control on your UI.
--
HTH
Stoitcho Goutsev (100)
"Chris Dunaway" <du******@gmail .com> wrote in message
news:11******** **************@ m73g2000cwd.goo glegroups.com.. .

Thanks Tom, Stoitcho for the suggestions.

What I ended up doing was using a delegate:

private delegate void lockdelegate();

I then changed my timer event as follows:

void _idleTimer_Elap sed(object sender,
System.Timers.E lapsedEventArgs e)
{
//marshal the call to the correct thread using a delegate
this.Invoke(new lockdelegate(lo ckRegister));
_idleTimer.Star t();
}

This way, the lock method is executed on the UI thread.

Thanks,

Chris