You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 23, 2019. It is now read-only.
Currently, there's no way for libraries running callback functions or their own hooks to tell the programs using the instance if the instance has errored. This can be solved with library hooks, yes, but library hooks are called for all instances, and most cleanup code isn't applicable for more than a few instances. So an error callback in the context would be nice.
Ex. A SF Processor's instance registers a timer callback. The timer library only sees the instance and not the underlying entity, and has no way of triggering the Processor's clean up code (turning red and updating the overlay text).
The text was updated successfully, but these errors were encountered:
Currently, there's no way for libraries running callback functions or their own hooks to tell the programs using the instance if the instance has errored. This can be solved with library hooks, yes, but library hooks are called for all instances, and most cleanup code isn't applicable for more than a few instances. So an error callback in the context would be nice.
Ex. A SF Processor's instance registers a timer callback. The timer library only sees the instance and not the underlying entity, and has no way of triggering the Processor's clean up code (turning red and updating the overlay text).
The text was updated successfully, but these errors were encountered: