# Give Components a Script at runtime

**URL:** <https://forum.inductiveautomation.com/t/give-components-a-script-at-runtime/80258>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [October 10, 2023, 7:44am UTC](https://forum.inductiveautomation.com/t/give-components-a-script-at-runtime/80258 "2023-10-10T07:44:51Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Tjark\_Sterk](https://avatars.discourse-cdn.com/v4/letter/t/ac91a4/32.png) [@Tjark\_Sterk](https://forum.inductiveautomation.com/u/Tjark_Sterk)\
**Post date:** [October 11, 2023, 7:19am UTC](https://forum.inductiveautomation.com/t/give-components-a-script-at-runtime/80258/5 "2023-10-11T07:19:24Z")

</div>

Yes I will thing about that approach. You actually gave me the information I was missing in another topic ([Dynamically getting a Component by clicking on it - Ignition - Inductive Automation Forum](https://forum.inductiveautomation.com/t/dynamically-getting-a-component-by-clicking-on-it/80256)) I posted Yesterday so thanks again. I find it really helpful to know how the stuff is handled in the backend.

---

_[View the full topic](https://forum.inductiveautomation.com/t/give-components-a-script-at-runtime/80258)._