# 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:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 14, 2018, 5:18pm UTC](https://forum.inductiveautomation.com/t/binding-to-custom-component-methods/19245/2 "2018-08-14T17:18:07Z")

</div>

Yes, it is possible to use runScript with custom functions (in certain circumstances). Mirroring what was described in your first link, I added a text field that accepts `*args`, and just returns them as a string:

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/dd67723f519294ad6636ba1d3c46eee15f131872.png)  
Then, I added a runScript binding using `self`:  
`runScript("self.printArgs", 0, {Root Container.Text Field.text}, {Root Container.Text Field 1.text}, {Root Container.Text Field 2.text})`

---

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