Hello Daniel,
The solution with the "indexname" field certainly will do the trick.
But in my opinion, it also has drawbacks - one of it is, that it could
confuse level makers.
I'd prefer a solution which can disappear after lets say the 1.1
release or so. Meaning sometime past the 1.0 release, but not in some
early bugfixes.
One solution would be to have a map file, and rewrite the configfile
upon load using the map file. The map file can then disappear later.
That way, scores and level filename would be kept in sync, and the
problem will be gone sometime later (or will only affect people
upgrading from 0.90 to post-1.0 without ever running 1.0). Or people
downgrading, but thats okay.
yeah, this is probably more likely to fail, but if its working fine in
99% of cases its already good enough IMHO.
On a different note: system-wide highscores would be nice, too. At
least for unix.
best regards,
Erich Schubert
--
erich@(mucl.de|debian.org) -- GPG Key ID: 4B3A135C (o_
To understand recursion you first need to understand recursion. //\
Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt für V_/_
eine Stunde wie eine Heimat aus. --- Herrmann Hesse
_______________________________________________
Enigma-devel mailing list
Enigma-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/enigma-devel
