Re: Last call on the selectable naming issue

Charles Goodwin wrote:
> 4.  markable and selectable

This should answer a few potential queries:
[16:53] <hotrod> charlieg: in option #4: selected=bool not marked=bool
[16:53] <hotrod> not sure what that means
[16:54] <charlieg> hotrod: preapply markable but then you don't put 
marked=true/false
[16:54] <charlieg> you're putting selected=true/false
[16:54] <charlieg> so it could be construed as a little misleading
[16:54] <charlieg> right?
[16:54] <hotrod> ah
[16:54] <hotrod> yes
[16:54] <hotrod> i don't like that
[16:54] <charlieg> but
[16:55] <charlieg> markable is semantically perfect
[16:55] <charlieg> and really
[16:55] <charlieg> it would be better if it was marked=true/false
[16:55] <charlieg> :)
[16:55] <charlieg> and selected returned an array of the selected widgets
[16:55] <charlieg> but that's deviating too much from the norm
[16:55] <hotrod> i was just about to ask why we couldn't use marked 
instead of selected

- Charlie