propertyChange event on componentRunning overhead

I’m curious when creating a propertyChange component script that is triggered from the “componentRunning” property, how often is this script executed and what are the possible ramifications from doing this when it comes to cpu and memory usage?

The script is executed twice, once when the component is displayed and once when it is removed. It uses very little CPU and memory.


Perfect thank you. I’ve been using it as a “component initialized” property to do certain tasks so this is the behavior I was hoping for.

Yes, I use it the same way.