Object name

[osrf-migration]

Original report (archived issue) by Nate Koenig (Bitbucket: Nathan Koenig).

---

The name of objects (Object::Name) is used by the GUI, but the Name is not user friendly. For example, the name has a number in order to guarantee uniqueness.

Maybe an Object can support a "user-friendly" name as well.

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

Also worth pointing out that the API already supports an id per object, so the names shouldn't need to carry the random sequence of numbers.

[osrf-migration]

Original comment by Shane Loretz (Bitbucket: Shane Loretz, GitHub: sloretz).

---

If it already has an id, do objects in the rendering library need a name at all? Maybe the name concept only needs to exist on the GUI.

[osrf-migration]

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).

---

That's a valid point, I think rendering could get rid of names.

The only things I can think of them being useful for is debugging or if eventually rendering starts communicating using ign-transport and has to handle topic names.

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

Names are useful for introspection, and debugging.

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

agreed that names should not need to be unique. There're currently places in ign-rendering that assume unique names, will looking changing that logic

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

• Edited issue description