Re: Understanding the new event model

David Crawshaw <[email protected]> writes:
> Having Keyboard events filter down to a target is very useful. The 
> problem is, the core doesn't have an initial target. Instead of some 
> ugly hack where we 'tell' the core what the initial target is, it just 
> makes it the same place as any other event.

The reasoning behind this is the "XWT without a theme should be
hideous-but-usable".  So you could only type in text boxes if the
mouse was in the box, but at least you'd be able to get stuff done.

  - a

> 
> xwt.theme.surface catches the Keyboard events the second they hit, and 
> redirects them to the currently focused widget.
> 
> It works really well. You can consider it a default 'focus follows 
> mouse' system.
> 
> d
> 
> 
> _______________________________________________
> widgets mailing list
> [email protected]
> http://lists.xwt.org/listinfo/widgets
> 

-- 
"If Darl McBride [the CEO of SCO, who claims the GPL 'destroys
 intellectual property'] was in charge, he'd probably make marriage
 unconstitutional too, since clearly it de-emphasizes the commercial
 nature of normal human interaction, and probably is a major
 impediment to the commercial growth of prostitution"

                                             -- Linus Torvalds