spine-c and _spAtlasPage_createTexture

puzzler

We need some custom data at _spAtlasPage_createTexture. We build wrapper for spine-c for our engine, and we need to pass additional data while creating atlas (references to our internal image library). Now we use globals for this, but this is not thread safe.

Nate, is there any chance you add some void* field into _spAtlasPage_createTexture ?

puzzler

Nate

You are the second person to ask for a void* with _spAtlasPage_createTexture, so I guess something should be done. Would it be sufficient for spAtlas to have void* rendererObject and _spAtlasPage_createTexture would get an additional parameter that is the spAtlas*?

puzzler

The call order we have now:

fill global value with library reference
call spAtlas_readAtlasFile -> spAtlas_readAtlas
_spAtlasPage_createTexture is called from spAtlas_readAtlas
now we use our global reference inside custom _spAtlasPage_createTexture to find image by name in our library

Global reference is not thread safe (need to use locks), so we need to pass additional parameter with userData at spAtlas_readAtlasFile to catch it at _spAtlasPage_createTexture

Or at some userData at spAtlas_readAtlas

Nate

Right. Give this a try:
https://github.com/EsotericSoftware/spi ... 11fcf3368b
I did it this way because it seemed better than passing the void* to _spAtlasPage_createTexture and _AtlasPage_disposeTexture (especially _AtlasPage_disposeTexture, since the void* isn't otherwise easily available there).

puzzler

Thanks, I'll give it a try. Looks like it should works.

Nate

It is allocated outside spAtlas so it is presumed you dispose it outside spAtlas.