2 Nov
2015
2 Nov
'15
9:21 a.m.
On Mon, Nov 2, 2015 at 12:24 PM, Henri Verbeet <hverbeet(a)gmail.com> wrote:
I'm not sure how easy it would be at this point, but we'll probably just want resource ops on sub-resources to print an ERR(). E.g. ideally we'd never call resource_unload() on a surface, but only ever on a texture. But that then means not adding sub-resources to the device's resource list, etc.
I'll add this to my todo list.