Option A please
Usually keep original in another location besides module and use a naming convention for ease of file replacement if req'd Sometimes I place images in module for future use when I get to that part of the module or wish to reuse an image later that has been replaced by a file with a different name. Auto purging would negate that work _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Joel Uckelman Sent: Thursday, October 04, 2007 5:27 AM To: [email protected] Subject: Re: [vassalengine] Re: Bug/Undesired behaviour? All unwanted images remain in the compressed file. Thus spake "benw_h": > OK thanks - it was my brother that tested it, not me, and he said he > couldn't get them out. I'll check to see if he was just being lazy ;) Here's a question for module designers: Would you prefer (a) a selection in a menu in the editor which purges unused images, or (b) automatic purging of unused images when a module is saved? (b) could lead to data loss if someone neglected to keep the originals of images. On the other hand, you should *always* keep the originals anyway, and you'd have to remember to use (a) for it to be effective. Is it common practice for designers to store their sole copy of module art inside their modules? -- [Non-text portions of this message have been removed]
