# Binding to Custom Component Methods

**URL:** <https://forum.inductiveautomation.com/t/binding-to-custom-component-methods/19245>\
**Category:** Ignition\
**Tags:** scripting\
**Created:** [August 14, 2018, 4:58pm UTC](https://forum.inductiveautomation.com/t/binding-to-custom-component-methods/19245 "2018-08-14T16:58:24Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [August 16, 2018, 4:17am UTC](https://forum.inductiveautomation.com/t/binding-to-custom-component-methods/19245/8 "2018-08-16T04:17:47Z")

</div>

Personally, I would never use parameters of type UDTType, for all of the reasons in my post you linked to. Not sure if I understand your reference to the Python expression, but for the Window component bindings, you would use the expression language rather than Python to read the tag values, e.g.:  
tag({RootContainer.DevicePath} + ‘/Temperature/PV’)

I found this eliminated all of my performance issues, once I moved away from UDTType parameters and started using this method above instead.

Just my 2c

---

_[View the full topic](https://forum.inductiveautomation.com/t/binding-to-custom-component-methods/19245)._
