Whoops - yes, when I was describing what the code might be, I messed up and didn't include the object type. My bad.
But after looking at it again, I sort-of like not having to remind LC that it's a group, or a control, or a button, etc. On Mon, May 5, 2014 at 2:37 PM, Mike Kerner <mikeker...@roadrunner.com>wrote: > I don't like this idea. Every control then has to have some special > keyword for describing its state, even when the controls are compound, as > radio buttons and segmented controls, tables, etc. are on mobile. > Originally, a checkbox was for one state, and a radio button was for > multiple states. A segmented control, a table, etc. are all differing > visual representations of the same thing, but the way the behavior is > described can vary, and as we have seen with mobile, the appearance can > change, too. Checkboxes still check...for now, but Jony Ive, or the lead > designer from any other interface project can blow that paradigm up any > time they choose, and you can choose to follow or not. > > 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 > or > if myCheckbox is selected > > > For multi-state controls, again, the keyword should be appearance > agnostic, or perhaps the control ought to be a single unit with multiple > options instead of being independent controls > > if myRadioButtons is "one" then > or > if myListOfBundesligaSquads is "Bayer" then > > and the script of those controls should apply to every option in the > "group" (for lack of a better word), and it ought to be a single control > instead of several controls, like radio buttons are/tend-to-be. > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
