On Sunday, Oct 3 1999, Hugh Senior wrote:
>>Seems like a property would be eaiser to deal with than a style. Perhaps
>>setting the "semiHiliteOn" property would enable semiHilite behavior.
>
> First, for platform consistency the 3 states should be True, False, Mixed.
> From HIG OS8 Guidelines p 28: "There is a mixed state for checkboxes, which
> shows that a selected range of items has some in the on state and some in
> the off state. For example, a text formatting checkbox for bold text would
> be in the mixed state if a text selection contained both bold and non-bold
> text."
>
> Second, we do not need a new property, just the third state. A checkbox can
> be _set_ to 3 hilite states, but the user does not choose "mixed" (in which
> case use radio btns). "Mixed" is an indicative, read-only state, for example:
>
> get the textStyle of fld 1
> if it is "bold" then set the hilite of me to true
> else if it is "plain" then set the hilite of me to false
> else set the hilite of me to mixed
>
> The only question is what "mixed" toggles to when clicked... selected or
> unselected. Personal preference would be to selected ("true") in order to
> indicate a positive rather than a negative decision.
I would agree with all of this. The user can't *set* the third state, that
must be done by script. Setting the hilite to true is correct. And setting
the hilite property like this won't break any existing scripts.
I think this state needs to be implemented for radio buttons as well as
checkboxes. It should work in exactly the same way.
Finally, you might want to consider a "mixedIcon" property for implementing
custom controls.
Regards,
Kevin
> /H
>
> Hugh Senior
> The Flexible Learning Company
> Consultant Programming
> Voice: +44 (0)1483.27 87 27
> Web: www.flexibleLearning.com
Kevin Miller <[EMAIL PROTECTED]> <http://www.xworlds.com/>
Cross Worlds Computing, MetaCard Distributors, Custom Development.
Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707.
