Feature Request: in code construction of TexturePtr about amethyst HOT 5 CLOSED

It's not that easy :p we can't just construct a TexturePtr with our own texture, we need to poke around at a deeper level

from amethyst.

After thinking about it I think our best approach is to re-impl drawing textures on screen

from amethyst.

What did you think off?
How should it be reimpl and what should we make better?

from amethyst.

I'm making a few assumptions that drawImage is actually in charge of drawing a texture, we could just re-impl what it does but instead replace it pulling the texture from a TexturePtr to where-ever we want

from amethyst.

I'm making a few assumptions that drawImage is actually in charge of drawing a texture, we could just re-impl what it does but instead replace it pulling the texture from a TexturePtr to where-ever we want

Not so simple, the way textures are stored is aids. I'd suggest you try to construct a BedrockTexture using a cg::Image and then taking the shared BedrockTextureData inside of it and putting it into a TexturePtr

from amethyst.