# Renaming isn't... real? Problem with any component blocks **URL:** \ **Category:** Questions about Thunkable X\ **Tags:** design\ **Created:** [July 17, 2019, 1:46pm UTC](https://community.thunkable.com/t/renaming-isnt-real-problem-with-any-component-blocks/146234 "2019-07-17T13:46:13Z")\ **Posts on this page:** 1\ **Showing post:** 33
**Author:** ![Mark](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/mark/32/18133_2.png) [@Mark](https://community.thunkable.com/u/Mark)\ **Post date:** [July 18, 2019, 5:14pm UTC](https://community.thunkable.com/t/renaming-isnt-real-problem-with-any-component-blocks/146234/33 "2019-07-18T17:14:23Z")
> [@actech](#): > > You are right about the fact that it was much easier to work with the names of the components. Just so you know, you can specify the textual name of a component for any of the generic getters, setters, methods, events, etc. The one thing that is a bit confusing (and is a bug) is that you can use the textual name of a component in equality comparisons in some old projects, but not in others and not in new projects. Our intent was for those comparisons not to work, so please don’t use them, as they might stop working at some point. We do hope to add a block that allows you to get the name of a component, and at that point you’ll be able to do those comparisons safely. -Mark --- _[View the full topic](https://community.thunkable.com/t/renaming-isnt-real-problem-with-any-component-blocks/146234)._