# \[Feature Request\] show full component path in title bar **URL:** \ **Category:** Ignition\ **Created:** [July 20, 2023, 4:01pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656 "2023-07-20T16:01:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [July 20, 2023, 4:01pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656/1 "2023-07-20T16:01:43Z")
sometimes i am seven levels deep in nested component hell and it would be nice to see the full path of the component i'm working on in the title bar. it would also be helpful when charting some of these deeply nested `parent.getChild().getChild().....` selectors in scripts. i know i can copy the path, but i don't want the extra hassle of dumping it to a text editor, console, or IDE just to see it and then forget when i move on to another component as i unscramble this spaghetti. at any rate, i think it would be a very useful feature that i've seen in other 'wares. ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [July 20, 2023, 4:28pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656/2 "2023-07-20T16:28:03Z")
While I'm not saying this wouldn't be useful, there's a somewhat elegant solution to your nested locator problem: move important values to the View level. Create custom properties at the View level and give them clear and unique names. Bind these custom properties against whichever component should drive them, OR use an onValueChange script to write to the View-level props when the relevant property changes. Now, you can bind against properties on the View instead of trying to locate non-sibling deeply-nested components. Alternatively, you could use Message Handlers to broadcast changes of values and allow other components to listen for those changes. This route has a bit of overhead which can be a drawback, but it's also very resilient to changes in the structure of your View. ---
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [July 20, 2023, 4:42pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656/3 "2023-07-20T16:42:38Z")
bruh. if you saw the gorrilla 💩, stream-of-consciousness-constructed, gong-show nightmare i'm working with right now, you'd see why i'm making the request. moving _forward_, yes, your strategy is actually what i am trying to promote. but cleaning mutant, irradiated alligators out of the swamp is not the same as building up from zero. ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [July 20, 2023, 5:53pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656/4 "2023-07-20T17:53:51Z")
Another note: cleaning "mutant, irradiated alligators" out of a swamp only works if you get the eggs as well; don't try quick fixes to bad old code as you'll be right back in that resource next year, angry at yourself for not moving the entire resource over to a better approach today. ---
**Author:** ![Tim\_Carlton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim_carlton/32/52835_2.png) [@Tim\_Carlton](https://forum.inductiveautomation.com/u/Tim_Carlton)\ **Post date:** [July 20, 2023, 6:01pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656/5 "2023-07-20T18:01:28Z")
Sounds like it is time for the "It is a good thing you brought be on board when you did. Now that I've had a chance to see what we are dealing with I have determined that it is much worse that we originally thought. I can fix it, but I am going to need XXX and YYY." meeting that you are supposed to have near the beginning of every engagement. Sometimes it's even true.... ---
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [July 24, 2023, 7:26pm UTC](https://forum.inductiveautomation.com/t/feature-request-show-full-component-path-in-title-bar/76656/6 "2023-07-24T19:26:50Z")
i think that's my every-other-morning update... 🥹 but, yeah. some stuff i've ripped out wholesale and re-authored from scratch. as @cmallonee said, those eggs have to go as well. but i'm slowly gaining ground... today i deployed a central script project and have started populating it with standardized scripts. i **will** have ice cream today!! 😃