Re: default button behaviour & shortcuts

We can discuss this all we want, and still get no where:

I think we all agree on what a default button is, and what it should
look like. In my opinion, the disagreement seems to be when to use a
default button and when it should be activated.

Perhaps we should agree on that issue first?

So here's a new attempt on suggesting when to use a default button and
what it should do:
1. A meaningful, default action exists.
2. We want the ENTER button to activate a default action when nothing
else is selected.
3. Nothing else is selected by default.
4. A default button should look like one.
5. When a button looks like a default button it should behave like one.

If these 5 points make sense, then we can ask ourselves is there a
meaningful, default action in the commit dialog? If it is, why isn't
it the default action? If it isn't, why is there a default button?

--
Thomas
On 6/19/06, Steve Williams <stevewilliams@kromestudios.com> wrote:
> Thomas Eyde wrote:
> > Then what is the thicker border supposed to indicate? In most of the
> > dialogs I have encountered, the thicker border means "This happens
> > when you hit ENTER".
> >
>
> ...IF the currently focused control does not process the key press
> event.  The thick border on the button means it is the _default_
> button.  If you press Enter, and the currently focused control does not
> eat the key press event, then the default button will be pressed.  The
> edit control, which is the currently focused control, processes the
> Enter key press event before it gets to the default control.  The dotted
> line or flashing caret shows the focused control.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org