# Access to bindable X and Y values on groups

**URL:** <https://forum.inductiveautomation.com/t/access-to-bindable-x-and-y-values-on-groups/3882>\
**Category:** Ignition\
**Created:** [January 19, 2012, 5:50pm UTC](https://forum.inductiveautomation.com/t/access-to-bindable-x-and-y-values-on-groups/3882 "2012-01-19T17:50:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg.Buehler](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg.Buehler](https://forum.inductiveautomation.com/u/Greg.Buehler)\
**Post date:** [January 19, 2012, 5:50pm UTC](https://forum.inductiveautomation.com/t/access-to-bindable-x-and-y-values-on-groups/3882/1 "2012-01-19T17:50:15Z")

</div>

It seems like you can only bind the X, Y values on groups made entirely of vector shapes… is there any way I can add a label to a group and still bind to the X and/or Y value?

---

<div class="post-metadata">

**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\
**Post date:** [January 19, 2012, 8:50pm UTC](https://forum.inductiveautomation.com/t/access-to-bindable-x-and-y-values-on-groups/3882/2 "2012-01-19T20:50:07Z")

</div>

Not in binding. However, through scripting you can use the:

system.gui.moveComponent  
system.gui.resizeComponent

functions to move containers with non-vector shapes.

---

<div class="post-metadata">

**Author:** ![Greg.Buehler](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg.Buehler](https://forum.inductiveautomation.com/u/Greg.Buehler)\
**Post date:** [January 19, 2012, 9:10pm UTC](https://forum.inductiveautomation.com/t/access-to-bindable-x-and-y-values-on-groups/3882/3 "2012-01-19T21:10:44Z")

</div>

[quote=“Travis.Cox”]Not in binding. However, through scripting you can use the:

system.gui.moveComponent  
system.gui.resizeComponent

functions to move containers with non-vector shapes.[/quote]

Yup, that’s what I ended up doing. It would be nice if the X and Y properties were exposed though.

Just for posterity:

```auto
# get component and x and y for later if you need it
theItem = event.source # or use the getComponent() function...
old_x = theItem.getX()
old_y = theItem.getY()

# do your operations
x = 123
y = 321

# call the move function
system.gui.moveComponent(theItem, x, y)
```