# Global pre-beforeRender() and pre-render() hooks?

**URL:** <https://forum.electromage.com/t/global-pre-beforerender-and-pre-render-hooks/3190>\
**Category:** Feature Ideas + Requests\
**Created:** [September 24, 2023, 2:32pm UTC](https://forum.electromage.com/t/global-pre-beforerender-and-pre-render-hooks/3190 "2023-09-24T14:32:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ZacharyRD](https://forum.electromage.com/user_avatar/forum.electromage.com/zacharyrd/32/124_2.png) [@ZacharyRD](https://forum.electromage.com/u/ZacharyRD)\
**Post date:** [September 28, 2023, 4:51pm UTC](https://forum.electromage.com/t/global-pre-beforerender-and-pre-render-hooks/3190/3 "2023-09-28T16:51:32Z")

</div>

I’d also add a +1 for this – for Burning Man this year, I adopted a palette switcher functionality across many different patterns across many different PixelBlaze, and version control on it when a bug was found was… time consuming. See [Detailed Beginner Tutorial for Making Wearables with PixelBlaze](https://forum.electromage.com/t/detailed-beginner-tutorial-for-making-wearables-with-pixelblaze/3073) for more details on that.

---

_[View the full topic](https://forum.electromage.com/t/global-pre-beforerender-and-pre-render-hooks/3190)._