Re: widgets plan proposal

On April 2, 2003 8:14 am, Andrew Kohlsmith wrote:
> > This means whatever was focused (say, a text field) looses focus,
> > passes it to the unfocusable (a button in a toolbar), and then gets it
> > back. This unfocus/focus stage could cause a few problems with certain
> > widgets. Say you had a selection in the text, and you hit a copy
> > button. Is the text still selected when the copy action runs?
>
> Good point.  Charlie says that this is already done by setting the button
> as focusable=false for a temporary nonfocusable, or setting subfocusable if
> it's never to be focusable.
 Yep:

<button focusable="false"/>  will be a non-focusable button

Rod

_______________________________________________
http://lists.xwt.org/listinfo/dev