Re: [Tile-dev] setting focus on button clicks: on purpose?

[Bryan O. <oa...@ba...>]

Brian Griffin wrote:
> Brian Griffin wrote:
> 
>> Bryan Oakley wrote:
>>
>>> Brian Griffin wrote:
>>>
>>>> Huh?  You don't want keyboard traversal for a radio button in a 
>>>> toolbar on the main window, and that's what -takefocus 0 gives you.  
>>>> So what's the problem?
>>>
>>>
>>> I *do* want keyboard traversal on a toolbar. I just don't want a 
>>> click to set the focus to the toolbar. Thus, I can't use "-takefocus 
>>> 0" because that removes the ability to use keyboard traversal.
>>
>>
>> But why?  That, to me, is non-standard.
> 
> 
> To me, there's no difference between <Key-Tab> and <Button-1> as far as 
> setting focus.

Ha! That's a great question. I hate it when people make me think, 
especially during the work day!

I guess my only response is "because I've always done it that way". I've 
(almost) always tried to make my apps such that it's possible to 
traverse to and through the toolbar. Come to think of it, that's not 
strictly necessary since toolbar buttons should correspond to menu 
items, and menu items are keyboard-traversable.

You raise a good point.

<surfin'...>

Hmmm. I think this quote from MSDN validates click-to-focus for buttons 
(not that I put a whole lot of stock in documented Microsoft policies 
since they violate them at will...):

"Display the input focus when the mouse button is pressed and the cursor 
is over a control"

(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwue/html/ch14c.asp)

Interesting. I guess I stand corrected. Maybe click-to-focus on by 
default, and "-takefocus 0" for toolbar controls is the Right Thing To Do.