# Perspective issue with users

**URL:** <https://forum.inductiveautomation.com/t/perspective-issue-with-users/76922>\
**Category:** Ignition\
**Tags:** ignition81, perspective, scripting\
**Created:** [July 26, 2023, 4:45am UTC](https://forum.inductiveautomation.com/t/perspective-issue-with-users/76922 "2023-07-26T04:45:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [July 26, 2023, 6:16am UTC](https://forum.inductiveautomation.com/t/perspective-issue-with-users/76922/3 "2023-07-26T06:16:24Z")

</div>

Regarding your code and component property references, you are creating a "brittle" application. If you move any of the conponents or wrap them inside another container then the application breaks as you are using absolute paths everywhere.

Have a look at my comments on [Trouble with 'if' statement, button event - #5 by Transistor](https://forum.inductiveautomation.com/t/trouble-with-if-statement-button-event/76892/5) where I explain how the application can be cleaned up by using a view's custom properties to hold the values of components using bidirectional bindings. Your code then just references `self.view.custom.xxxxx` and there are no absolute or relative paths. It brings great joy to you and to those who maintain your code in the future!

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-issue-with-users/76922)._