Hi Olaf, As soon as you say a scenario is rare, then it definitely shouldn't be baked into the base classes for PAYG reasons.
It occurs to me that for any component that implements IStrand (like UIBase), you could define a bead that goes on the strand that would generate an identifier. Or document the pattern that folks could use to add an identifier to a subclass of an existing bead (so you can swap out a bead instead of having to alter the app to inject an additional bead). Maybe you can write that up and contribute it. -Alex On 2/13/19, 1:36 AM, "Olaf Krueger" <[email protected]> wrote: Hi Alex, >I'd be interested in understanding the scenario where you create multiple instances with the exact same set of properties. Even if these scenarios are probably rare: One scenario is to display multiple instances of the same UI component at the same time. After initialization, they are all identical. Another scenario is when you create whatever other object instances dynamically at runtime it could occur, that you accidentally created more instances than needed (without knowing about this issue). With a unique identifier, such a thing could be more obvious. >For PAYG reasons, identifiers are not added to every object "just-in-case". If you need them, add them. > Import org.apache.royale.utils.UIDUtil; I already understood it and I am totally fine with this workaround! I don't want to complain, I just want to understand it entirely! ;-) Thanks for the help, Olaf -- Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C7477d3b48cb848232e3808d69196c7ba%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636856474114574690&sdata=9dhhyEPghMOxTTgw7Kdwec8GbGbD6fQS6UzCTg8Sn6Y%3D&reserved=0
