>*********** REPLY SEPARATOR *********** > >On 4/10/2007 at 12:26 PM Joel Uckelman wrote: >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?
Absolutely not! BTW, what I really wanted to do a year ago was to extend one of the low-level Buildable or Configurable classes to have a getImageNames() method. Same for counters. Then we could have proper image garbage collection. ____________________________________________________________ Brent Easton Analyst/Programmer University of Western Sydney Email: [EMAIL PROTECTED]
