There’s no change in PAYG rules. My guideline was to not add anything significant to runtime cost or download size by enhancing the bead. I may have missed something, so if there’s a specific line number that you see which is adding to either of those please let me know.
We did have a concern regarding elements being swapped In runtime, but that is fixed in 95922ad776e39208e3d515bd7a484219779271d1. Thanks. From: Justin Mclean<mailto:justinmcl...@me.com> Sent: Friday, September 29, 2017 4:22 AM To: dev@flex.apache.org<mailto:dev@flex.apache.org> Subject: Re: [3/4] git commit: [flex-asjs] [refs/heads/develop] - Allow drag and drop item renderers to be more that simpkle labels. Hi, > Possibly. Which part adds overhead in your opinion? In that it a feature that not all users may use that's being implemented by conditional logic so it adds to both run time and possibly size cost. While that cost would be small in the past on the Flex list code similar to this has been called out as not PAYG and it’s been suggested to move it to a new class. It may however be that PAYG is now less strict and that adding new features in this way is now acceptable? Thanks, Justin
