OK, thanks, guess I'd better make a destructor then.
Thing is I have a template type that the actual images are loaded into and all the other types just point their image pointers at the template type's images. Therefore when I free the non-template types, I don't need to free the images as they were only pointers. But I do need to free the template type images on exit (I suppose). I was just wondering if I call Delete TemplateType will blitz kill the images for me? In fact if I don't even call Delete TemplateType, will Blitz kill the type AND the images? Get it? I am just trying to be lazy and also to avert paranoia.
See I know that blitz kills images on exit but what if the pointers to them were part of a type that you have already deleted. Doesn't this leave the images without pointers, thus unfreeable, or does blitz keep track of images on its own?
Thing is I have a template type that the actual images are loaded into and all the other types just point their image pointers at the template type's images. Therefore when I free the non-template types, I don't need to free the images as they were only pointers. But I do need to free the template type images on exit (I suppose). I was just wondering if I call Delete TemplateType will blitz kill the images for me? In fact if I don't even call Delete TemplateType, will Blitz kill the type AND the images? Get it? I am just trying to be lazy and also to avert paranoia.
See I know that blitz kills images on exit but what if the pointers to them were part of a type that you have already deleted. Doesn't this leave the images without pointers, thus unfreeable, or does blitz keep track of images on its own?