# Pointers on React Component Designer Implementation

**URL:** <https://forum.inductiveautomation.com/t/pointers-on-react-component-designer-implementation/95044>\
**Category:** Module Development\
**Tags:** perspective\
**Created:** [August 22, 2024, 9:49pm UTC](https://forum.inductiveautomation.com/t/pointers-on-react-component-designer-implementation/95044 "2024-08-22T21:49:44Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [August 24, 2024, 10:36pm UTC](https://forum.inductiveautomation.com/t/pointers-on-react-component-designer-implementation/95044/21 "2024-08-24T22:36:14Z")

</div>

> [@bmusson](#):
>
> The `useState` setter is asynchronous, you won’t see the changes right away.

I know nothing about the diagramming library, but I think It’s reasonable to expect `setSchema` to behave similarly.

I’d suggest trying to get away from the diagramming library’s state management ideas and let the Perspective property tree be the single source of truth for your component’s state.

[Previous page](https://forum.inductiveautomation.com/t/pointers-on-react-component-designer-implementation/95044.md?page=1)