Sorry your browser is not supported!

Sombody with authority and knowledge in the matter to answer this question please. (preferably lee )

lets say i create an object
i load an image
i texture an object in that image
i then delete that image.
as soon as it has been deleted the same file is reloaded into the same image number.

does dark basic like that
does it like having images currently in use as an bject texture to be deleted
if i load a diferent image in place ofthe old one will the objects be automatically textures.
its just ive written a program and nowher in my program does it state to chnage the obejct mesh. and yet i get some very very strange unwanted un expected bugs. anything from crashes to meshes being changed and its to do with images being deleted

please note im just that last statement was just to let you know y im asking. Do not reply to this post to state how much you hate me. how much you hate my posts how much you hate my avatar signature spelling. do not reply to comment on the bug im getting or wether it is related to images being mucked abomut with.
only reply if you KNOW wethere or not db minds images being loaded releoded deleted whilst in use.

I suggest that you put at least one SYNC in before you delete your image. Sometimes when I have tried to delete an image which was used as a texture, it crashed, waiting a loop or putting a SYNC in after TEXTURE OBJECT fixed the problem.

when ive deleted the image
and i reload the same image under the same number would i have to retexture it.

Sync if currently set to off. so i dont need the sync command ... do i?

When you texture the object, it appears to copy the image into a buffer somewhere, so you can happily delete the source image.