For PAYG reasons, identifiers are not added to every object "just-in-case". If you need them, add them.
I'd be interested in understanding the scenario where you create multiple instances with the exact same set of properties. I would think it would be better to share one instance in that case. It should be simple to add uid's where you need them unless I'm missing something: Import org.apache.royale.utils.UIDUtil; ... Private var _uid:String; Public function MyConstructor(){ _uid = UIDUtil(this); } HTH, -Alex On 2/12/19, 2:34 AM, "Olaf Krueger" <m...@olafkrueger.net> wrote: Thanks, Yishay... it really seems that StableObjectId is coming from Chrome. > You can use an object’s dimensions, className, etc. to make sure it’s the > one you need. > I do this all the time to break on specific values. Just to make sure that I got it right: What if we create a couple of instances of the same class, all objects are in the same initial state, all objects are total equal e.g.: var instance1:MySuperComponent = new MySuperComponent(); var instance2:MySuperComponent = new MySuperComponent(); var instance3:MySuperComponent = new MySuperComponent(); In Flex, the object id can be used to distinguish between those objects out of the box. Is my understanding right that in Royale, we have to modify or add an object property (e.g UUID) of/to each particular object in order to be able to distinguish between all instances. Thanks, 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%7Ce1eae98d87e3478b753308d690d59d34%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636855644507811920&sdata=5dFh2otgxkQXCoEN6ycomKZYSZorwCEhZyuDKfFQcAQ%3D&reserved=0