The ID is hidden because we have garbage collection tied to your object. If you get the ID, but the Haxe object falls out of scope, the texture will be deleted
That said, I want to improve the interoperability with native APIs, not make it harder.
The abstracts could convert directly, or we could have an ID field, open to ideas. Thanks
Ok, thats understandable. But in certain cases this is needed if you say are mixing some c++ libs with haxe… and with knowing these limitations is its ok… so by using it the application will need to take care into how this is used, specifically regarding GC. … an open ID field would be preferable i think
yeah, boils down to how “hidden” this should be? By using the abstract you kind of have to know about this to use it… and you should perhaps be, in the first place… so maybe thats ok…