Hmm. I wasn't at my computer yet when I wrote this email. I really thought there was a controller for these to be consistent with other components and to allow different types of device events to be handled by controllers.
I will take a look at this today. Sorry for the confusion. ‹peter On 1/31/17, 9:03 AM, "Peter Ent" <p...@adobe.com> wrote: >I have not looked at the change yet, but the mouse events should be >handled in the controller for radio button. The idea is that a controller >(mouse, touch, keyboard) intercepts the "raw" event and dispatches a >universal event (change). This way you just switch the controller bead >based on the device used. > >Does that help? I'll look into this more closely in a little while. > >Peter > > >> On Jan 31, 2017, at 4:09 AM, Carlos Rovira <carlosrov...@apache.org> >>wrote: >> >> Alex, Peter, >> >> we're having some problems with MDL RadioButton click event. >> >> I implement RadioButton in mdl as a fork of the HTML one (they both >>share >> the same parent class and structure, so MDL does not extend RB HTML) >> >> As the rest of toggle components all has "change" and "click" events. >> Change use to work ok (no problem at all with that), but click use to >>give >> us problems. In Checkbox we had the problem that click was throwing two >> times so we make a workaround in the handler with preventDefault and >>manual >> selection/deselection. >> >> In RB Piotr could fix the issue deselecting all RBs in a group. so >>again we >> had to do manual. Maybe we could go with this implementation for now. >>but >> it motivated me to send this email. >> >> I think we don't understand the base in FlexJS and why is happening this >> issue with click event. For this reason we can't implement a solution >>that >> could be the best one, or one that does not look a bit "hacky" >> >> Hope you could give us some clue about what's happening here so we could >> understand and act accordingly >> >> >> Thanks! >> >> Carlos >> >> >> >> >> >> 2017-01-31 0:28 GMT+01:00 piotrz <piotrzarzyck...@gmail.com>: >> >>> Hi Carlos, >>> >>> I just pushed fixed for double click event on RadioButton, but it's not >>> ideal. With this fix our "selected" property won't work. >>> >>> My solution: >>> >>> - Getting all Radio buttons in group and deselect all radio (I'm using >>>java >>> script function not "selected" property - that's why in unselection >>>process >>> our selected property is untouched) - Look into the "unselectAll" >>>function >>> - >>> maybe you will have some other idea. >>> - I'm selecting clicked element >>> >>> >>> Here is what I see without my fix. Our event listener is fire two >>>times and >>> source of our event is from >>> >>> <http://apache-flex-development.2333347.n4.nabble. >>> com/file/n58814/radio_click.png> >>> >>> goog.events.handleBrowseEvent function inside events.js - This >>>function is >>> fire two times in our ElementWrapper - fireListenerOverride. - Not sure >>> why. >>> >>> Piotr >>> >>> >>> >>> >>> ----- >>> Apache Flex PMC >>> piotrzarzyck...@gmail.com >>> -- >>> View this message in context: http://apache-flex- >>> development.2333347.n4.nabble.com/FlexJS-RadioButton-click- >>> event-tp58731p58814.html >>> Sent from the Apache Flex Development mailing list archive at >>>Nabble.com. >>> >> >> >> >> -- >> Carlos Rovira >> http://about.me/carlosrovira
