I spent quite a bit of time looking into this. I came to the conclusion that there likely needs to be beads with more interop for modifying data content, but I don’t think I need that for right now.
After finding my way through the classes, I realized that dataGroup.getItemRendererForIndex() has range checking, so there’s no reaosn for the view to do it’s own range checking. A simple null check on the results is enough (which the selected handler was already doing). So better safety with less code. An all-around win. :-) > On Jul 24, 2017, at 10:12 AM, piotrz <piotrzarzyck...@gmail.com> wrote: > > Hi Harbs, > > In such cases where you preventing from RTE I'm thinking that having bead > would be weird. PreventDataGroupFromRte? Cause you do not do anything more > adding such just-in-case code. Maybe this case is one of those when we > should have that code? > > Piotr > > > > ----- > Apache Flex PMC > piotrzarzyck...@gmail.com > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/FlexJS-PAYG-and-dataGroups-tp63496p63502.html > Sent from the Apache Flex Development mailing list archive at Nabble.com.
