Re: widgets plan proposal

On Wednesday, April 2, 2003, at 11:29  AM, Andrew Kohlsmith wrote:
> _action = function() {
>     do_action_here();
>     focusable.lastfocused = focused;
>     }

This discussion is obviously abstract (the code isn't exact), but I can 
still see a possible problem with this.

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?

Wouldn't it be better if a clickable could be clicked without the focus 
ever moving? The copy simply happens, the the text field stays where it 
was.

> ... ain't widget design fun?  :-)

Like a stick in the eye.

I suppose the goal should be to come up with a model that specifically 
details how it handles each and every word we use (selected, focused, 
clicked, dragged, dropped, focusable, editable, etc), and then a 
document for each theme that details how we translate our language into 
the actions of the specific theme.

Sounds like a study project. You'd have to get a full design for each 
theme your implementing, and then map our design to it. This is the 
point I got to in the widget library when my patches started dropping 
off. I just didn't want to keep coding knowing that I should be 
creating this documentation, and my code was starting to go in circles.

d


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