# Strange system.gui.transform behavior with templated instances **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision, scripting\ **Created:** [July 15, 2025, 5:43pm UTC](https://forum.inductiveautomation.com/t/strange-system-gui-transform-behavior-with-templated-instances/108509 "2025-07-15T17:43:43Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [July 19, 2025, 3:47am UTC](https://forum.inductiveautomation.com/t/strange-system-gui-transform-behavior-with-templated-instances/108509/8 "2025-07-19T03:47:33Z")
It's possible that this forum post could be applicable to this use case: [How to transform a component inside of a vision template](https://forum.inductiveautomation.com/t/how-to-transform-a-component-inside-of-a-vision-template/80122) The problem is that the coordspace argument is always relative to the designer's window editor NOT the designer's template editor. As long as the template instance in the window is not stretched or squished when it's placed in the window, it will work fine, but if it has been resized after being dragged and dropped, then the transform will be off by that proportional amount. --- _[View the full topic](https://forum.inductiveautomation.com/t/strange-system-gui-transform-behavior-with-templated-instances/108509)._