Creating an app may not always happen before loading playcanvas-tween. In those cases, the integration of the library with the app does not happen, which is problematic. I am dealing with a project that has PlayCanvas for only a part of the full project, as it uses simple DOM UI on the outside before entering the game world. In that case, I run into this race condition.
It would be so nice if this tween library could automatically register itself on any new app when the app gets created, just like how PlayCanvas already does actions like this when things are available (asset loading, etc).
Alternatively, perhaps expose the integration in some way so I can trigger it myself?
Creating an app may not always happen before loading
playcanvas-tween. In those cases, the integration of the library with the app does not happen, which is problematic. I am dealing with a project that has PlayCanvas for only a part of the full project, as it uses simple DOM UI on the outside before entering the game world. In that case, I run into this race condition.It would be so nice if this tween library could automatically register itself on any new app when the app gets created, just like how PlayCanvas already does actions like this when things are available (asset loading, etc).
Alternatively, perhaps expose the integration in some way so I can trigger it myself?