# Resize factor of used template

**URL:** <https://forum.inductiveautomation.com/t/resize-factor-of-used-template/84177>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [January 12, 2024, 10:34am UTC](https://forum.inductiveautomation.com/t/resize-factor-of-used-template/84177 "2024-01-12T10:34:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [January 12, 2024, 12:31pm UTC](https://forum.inductiveautomation.com/t/resize-factor-of-used-template/84177/2 "2024-01-12T12:31:23Z")

</div>

Yes. I worked it out in this post:

> [@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/6):
>
> Nope. While groups definitely exhibit the same scaling behaviors as templates when you squish them or expand them, a simple transform still works as expected on a group's individual components because the components' bounds are still relative to their location within the window editor in the designer. That said, I've finally got my head around what I was observing. The bounds of the template are always relative to the template editor in the designer. Therefore, my erroneous expectation was for…

I've since used this approach successfully in multiple projects.

---

_[View the full topic](https://forum.inductiveautomation.com/t/resize-factor-of-used-template/84177)._