dsc at swcp.com
Mon May 5 17:20:39 EDT 2014
My suggestion was to take advantage of the property that was already there, text.
The checkbox is a nice way to introduce ‘if’ statements. However, the syntax causes MEGO. It introduces several new concepts.
I have to rearrange things, then, since responses are underwhelming.
Maybe a quick look at ‘is a number’ (which really is complicated) can work for ‘if’. Or better, a numeric comparison.
Both highlight and button can be introduced slowly. Checked is highlighted? A checkbox is a button?
Or I can just give them a checkedBox or boxIsChecked function and explain it to those who are ready but allow others to use it as is. .
On May 5, 2014, at 1:10 PM, Scott Rossi <scott at tactilemedia.com> wrote:
> Another problem with using control-specific property names to represent
> the (existing) hilite of a control is syntax-related.
> Using "selected" might be appropriate to describing that state of a
> checkbox, but how do you distinguish this from the "physically selected
> with the pointer tool" selected?
> I already have enough blood stains on the wall in my studio where my
> forehead has made contact numerous times.
> Scott Rossi
> Creative Director
> Tactile Media, UX/UI Design
> On 5/5/14 11:37 AM, "Mike Kerner" <MikeKerner at roadrunner.com> wrote:
>> So if, for single-state controls, you want to have a new property, then it
>> should be something that is appearance-agnostic, like, I don't know,
>> selected, perhaps, and I think it should be boolean and matter-of-fact
>> if the selected of myCheckbox
>> if myCheckbox is selected
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode