> but if your new methods are used to generate the attributes() XMLList They aren’t.
> "is anybody using these new methods?” Besides me, I doubt it. But I don’t want to recklessly change things without at least mentioning the change... > On Nov 19, 2018, at 2:30 PM, Alex Harui <[email protected]> wrote: > > I haven't looked at the code, but if your new methods are used to generate > the attributes() XMLList, then I would think that migrating Flex users would > have to care. (and if not, I would want to know why it sounds like there are > two ways to build up the list of attributes) If these are truly new to > Royale, the better first question probably should have been "is anybody using > these new methods?" > > -Alex > > On 11/19/18, 11:26 AM, "Harbs" <[email protected]> wrote: > > Existing code doesn’t need to care. These methods are new and don’t exist > in Flash. > >> On Nov 19, 2018, at 2:23 PM, Alex Harui <[email protected]> wrote: >> >> >> On 11/19/18, 11:20 AM, "Harbs" <[email protected]> wrote: >> >> Trying to “delete” (or access) a specific element of the XMLList while >> manipulating the array is something that would need care. >> >> I think that's my point. I think existing code in migrating Flex apps >> didn't need to care, so they shouldn't have to care in Royale by default. >> But if you provide an option where they trade-off caring for speed, that >> seems fine to me. >> >> -Alex >> > > >
