Thus spake "Tim Byrne": > On 10/4/07, Joel Uckelman <[EMAIL PROTECTED]> wrote: > > > >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? > > Maybe a compromise option would be to check for unused images on saving > > a module, and prompt the designer for whether they should be retained > > if any are found? That way, it's semi-automatic, and we get the benefits > > of both methods. > > I would prefer Option A, but I suppose I could live with a "warning" > message when the module is saved. > > I store my images, buildFile, and help system separately so SVN can > deal with them and create the module from those. I would prefer the > option the invoke the check without having to save. > > I'm guessing that anyone who wants to store images in the module > (during development) would find a warning message quite irritating, as > it seems that many changes need a restart of vassal to test. So > during development a module may be open and saved many times over. > > I must admit that there are times that I add images to where my module > is build from before I add all the references in the buildFile. If > the warning was in effect I would probably just refrain from doing > that to avoid the annoyance of the message. > > -Tim >
It looks like we have two opposed use cases here. If we had a preference for toggling whether the user is prompted at savetime about whether to purge orphans, that would let those who want orphan removal to be automatic avoid the nag dialog. On the other hand, it would then become impossible to intentionally add orphans without turning on the nag dialog. I guess there should three settings in the preferences, then: * always purge orphans, don't ask * never purge orphans, don't ask * ask whether to purge orphans -- J.
