Tab and focus rectangle question

[john ciriello]

I created a form and put a button and a label on it. I set the tabstops to
false. When I first run it I can click the button and there is no focus
rectangle. Which is what I want. However, if I press the tab key nothing
initially seems to happen, I know nothing should because I set the tabstop
to false, but to my surprise, when I then click the button again a focus
rectangle appears. This I do not want. Any Ideas on how to stop this
behaviour? Here's some code I tried. I also do not want the focus to stay on
the button during or after I click it which is why I set the focus to the
label. But the rectangles stays. Ugly...
Thanks for the help. John.

namespace WindowsFormsApp lication3

{

public partial class Form1 : Form

{

public Form1()

{

InitializeCompo nent();

}

private void button1_Click(o bject sender, EventArgs e)

{

label1.Focus();

}

private void button1_MouseUp (object sender, MouseEventArgs e)

{

label1.Focus();

}

}

}

[Peter Duniho]

On Fri, 18 Jul 2008 14:35:47 -0700, john ciriello <j.********@com cast.net>
wrote:

I created a form and put a button and a label on it. I set the tabstops
to
false. When I first run it I can click the button and there is no focus
rectangle. Which is what I want. However, if I press the tab key nothing
initially seems to happen, I know nothing should because I set the
tabstop
to false, but to my surprise, when I then click the button again a focus
rectangle appears. This I do not want. Any Ideas on how to stop this
behaviour?

Assuming the Label instance was enabled, you should be able to force the
focus to it by handling the Enter event on the Button instance and calling
label1.Focus(). Handling the Click and MouseUp events isn't the correct
way, because that's not precisely where focus is set.

That said, if what you want is specifically a button that won't accept
focus, IMHO a better way to do it is to create your own Button sub-class
in which you set the ControlStyles.S electable style to "false". Then the
button will never receive focus in the first place.

All that said, I question your decision to make the button so that it
won't receive focus. Focus is a very important part of allowing a Windows
application to be accessible by alternative means of input. You cannot
assume that the user has access or the ability to use a mouse. Windows
provides some surrogate input methods for dealing with applications that
are rude enough to require a mouse for input, but it's better for your
application to simply not require a mouse in the first place.

Pete