# Vision Component Size restrictions

**URL:** <https://forum.inductiveautomation.com/t/vision-component-size-restrictions/83103>\
**Category:** Module Development\
**Tags:** vision\
**Created:** [December 13, 2023, 6:59pm UTC](https://forum.inductiveautomation.com/t/vision-component-size-restrictions/83103 "2023-12-13T18:59:40Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![Mathias\_Melling](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mathias_melling/32/67682_2.png) [@Mathias\_Melling](https://forum.inductiveautomation.com/u/Mathias_Melling)\
**Post date:** [September 23, 2024, 2:11pm UTC](https://forum.inductiveautomation.com/t/vision-component-size-restrictions/83103/31 "2024-09-23T14:11:55Z")

</div>

See reply over here:

> [@Error when saving Bounds2DComponent (serialization error)](https://forum.inductiveautomation.com/t/error-when-saving-bounds2dcomponent-serialization-error/96276/5):
>
> Hi Bohdan, I've been building my components by extending the AbstractVisionShape class, which itself is an extension of AbstractVisionComponent and it also implements the Bounds2DComponent interface. Maybe that's the way to go for you as well, instead of trying to implement Bounds2DComponent yourself. As to your question here: I add the boundingRect property just like any other property: addProp("boundingRect", "Bounds", "Bounding rectangle of the component.", CAT\_POSITION, HIDDEN\_M…

---

_[View the full topic](https://forum.inductiveautomation.com/t/vision-component-size-restrictions/83103)._