However, if I just change the extension manually and click on export,
everything works.
Is there anything in the error log?
Sometimes strange things happen under Windows, and then it helps uninstalling
the program, and reinstalling it.
Peter
--
------------------------------------------------
Peter Bienstman
Ghent University, Dept. of Information Technology
Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium
tel: +32 9 264 34 46, fax: +32 9 264 35 93
WWW: http://photonics.intec.UGent.be
email: Peter.B...@UGent.be
------------------------------------------------
> BTW: I have verified that MS can always find the current "config.py"
> file by searching upwards from the location of the current database.
This is unsupported. If you want to place your data directory in a different
place, the only supported way to do so is by adding the command line option '-
d <my desired path>' when you start Mnemosyne.
You can automate this by creating a desktop shortcut with as location
"C:\Program Files\Mnemosyne\mnemosyne.exe" -d C:\whatever
Otherwise, you will run into troubles by mixing data from the default location
and your desired location, as you found out.
Peter
> BTW: What's the purpose of the dot in front of the ".mnemosyne" ?
So that it's a hidden directory under Linux. Common practice on that platform.
Peter
Oh, BTW, that is NOT how you are supposed to do this. You should use the -d
option in the 'target' field as I explained, otherwise it won't work.
Peter
It's only when starting from a 'virgin' installation that the location
defaults to the current datadir.
Peter
Virgin install is the state you have after just installing the program and
when you haven't touched it yet.
The datadir is the .mnemosyne directory.
When I read your recipe, the following has happened internally:
* The first time you started .mnemosyne, you did not use the -d option, the
datadir got created in its default location in C:\Documents and
settings\oldgrantonian\.mnemosyne. The default directory for exports also got
initialised to that directory.
* if you move your datadir to a new place and start with the correct -d
option, internally, the export directory still points to C:\Documents and
settings\oldgrantonian\.mnemosyne, so that in your scenario, you try to export
to a path which no longer exists. Mnemosyne silently fails in this case, as
opposed to giving an error. I will make this more robust in a future release
* However, the workaround is easy, just browse to the correct dir the first
time, and afterwards Mnemosyne will remember that location.
If you start Mnemosyne the first time with the -d option, then this issue will
not occur.
Hopefully this clarifies the situation somewhat.
Thanks for the feedback!
Peter