Aseprite is now based on haxe.io.Bytes and no longer tied to Heaps resource system
Added separate resource class: aseprite.AsepriteRes
USAGE
var myAseprite = hxd.Res.myFile.toAseprite(); // previously: hxd.Res.myFile
The only downside is that you have to let the user take care of hot-reloading stuff (ie. file watching). But IMHO that's safer actually, as swapping the texture without notifying the user on file change will lead to issues on runtime anyway 🤔
It's still possible to "refresh" a Aseprite instance using the public myAseprite.fromBytes( bytes:haxe.io.Bytes ) method 👍
Aseprite is now based on
haxe.io.Bytesand no longer tied to Heaps resource systemAdded separate resource class:
aseprite.AsepriteResUSAGE
The only downside is that you have to let the user take care of hot-reloading stuff (ie. file watching). But IMHO that's safer actually, as swapping the texture without notifying the user on file change will lead to issues on runtime anyway 🤔
It's still possible to "refresh" a Aseprite instance using the public
myAseprite.fromBytes( bytes:haxe.io.Bytes )method 👍