No, it is consistent, in my opinion, excellently so. You notice that the radio buttons change their data as soon as you click down on them, so they don't need two visual states at the moment (ie. simple)
If and when they are enhanced, or when somebody chooses to make their own, they can use the state attribute to control visual state, just as in the button style. This would mean that the user would have to click and release the mouse in the hit-region (just like MS radio buttons) to get the data change. Comprende? Regards, Anton. > Heh, RT could learn a good lesson from Microsoft VB here and > have a value > field for each data providing widget. This would aid in > consistency and > help develop a better standard :) > > rather than picked, state, data.. etc.. > > James. > > ----- Original Message ----- > From: "Gregg Irwin" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, December 21, 2001 8:50 AM > Subject: [REBOL] Re: What changes when a 'radio is "on"? > > > > Hi Alan, > > > > << What does change when a 'radio is "on" >> > > > > Looks like /data maybe. > > > > view layout [ > > r1: radio [print [r1/data r2/data]] > > r2: radio [print [r1/data r2/data]] > > ] > > > > --Gregg -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
