I had the unfortunate displeasure of trying to use a Texture Active. about zimjs HOT 1 OPEN

ZIM is a Framework. So globals can be quite handy for us. If you want to turn them off then use the NPM version or if using the CDN then set zns=true for requiring the ZIM namespace and avoiding adding ZIM classes to globals.

We mostly work with a single frame. This lets us assume this frame's stage as the default container. If there are other frames then their stage would need to be specified unless one decides to use setDefault() on that frame. This is a convenience and would not really call it a state but maybe.

We do have some three letter global functions that start with z - for ZIM. They are short such as zog(), a wrapper for console.log(). If we put a namespace in front of them like zim.log() then that is about the same as using console.log() making the wrapper less appealing. I would not call that bad naming, but rather clever naming to avoid conflict for short globals and to have some fun.

TextureActives() accepts a single TextureActive object or an array of TextureActive objects as it states in the docs https://zimjs.com/docs.html#TextureActives so this is not an unmaintained feature.

Sorry we got to this post late - hopefully you found your way into our Forum https://forum.zimjs.com or Discord https://zimjs.com/discord support - we would be happy to help you get it working. Since this time, we have added 35 examples found here https://zimjs.com/studio - that will perhaps help.

If you do make your way back here... we apologize for your unfortunate displeasure ;-). Join our forum, discuss globals, and let's make it better!

from zimjs.