That's good news, I much prefer having control over my images and the directory structure.
On Nov 18, 5:54 pm, Peter Bienstman <[email protected]> wrote: > > On Wed, Nov 18, 2009 at 07:06:48AM +0100, Peter Bienstman wrote: > > > 2.0 currently makes a copy of your picture files and stores it in its > > > own folder [...] [which] makes it easier for users to backup > > > their cards + media files if they are all in the same place. > > > Although I can live without it, I'd like to keep my images segregated > > into category sub-folders. Would it be convient for Mnemosyne to only > > copy images into .mnemosyne/<picture directory>/ if the images are > > currently outside .mnemosyne/? > > > For example, ~/foo.png would be copied into > > ~/.mnemosyne/<picture_directory> but > > ~/.mnemosyne/constellations/ursa_major.png would be left alone. > > Actually, turns out this is how it works, but I forgot about it as I > implemented it over the summer. So, subdirs inside the .mnemosyne dirs will > still be supported, contrary to what I said earlier. > > Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=.
