Hi Alex,

Thanks for your feedback! Some info on why I chose the approach I did:

* most config info really belongs to the program as a whole and not the 
database specifically. It would not make any sense surprise users with changing 
settings if he loads a different database.
* I do not remove the config file upon uninstall for the same obvious reason I 
do not remove the database files or Word does not remove your documents when 
you uninstall.

Really, in theory the current approach should be alright provided there are no 
bugs. However, since I've never seen this on any of my machines I'm dependent 
on other people answering the requests for feedback I asked. E.g.:

-what is the exact content of the error message? (it could be that your error 
is not related to the config file at all!)
-do you run from a USB key? (perhaps you remove it before doing 'safely remove 
hardware')
-what is the output of the debug version
-etc, etc...

Since that info did not arrive, I had no choice but to release 2.3...

Cheers,

Peter

> -----Original Message-----
> From: [email protected] [mailto:mnemosyne-
> [email protected]] On Behalf Of Alex .
> Sent: 03 May 2014 03:02
> To: [email protected]
> Cc: [email protected]; mnemosyne-proj-
> [email protected]
> Subject: [mnemosyne-proj-users] Re: Mnemosyne 2.3 released
> 
> Peter, these Traceback errors seem to be quite tenacious.
> Why are you  keeping the config in such a hard to find place and why is it not
> deleted on uninstall?  It is making it so that people who get the error are
> unable to fix it when they re install unless they know about the location of
> the hidden config.
> 
> Why not keep config information in the deck file instead of the program?
> stuff like card colors and fonts is something the person who creates the deck
> should be able to set, and the user can edit it if they want and overwrite the
> deck config with their changes.  Wouldn't this be a much better way to
> handle it?
> 
> At the very least please make sure when the User uninstalls the program
> they have the option in the uninstaller to remove EVERYTHING.  Its not polite
> to have the user think they have uninstalled when actually there are still
> configs in the roaming folder months after they uninstalled contributing to
> clogged up OS syndrome.  wouldnt you agree?
> 
> Keep up the good work
> 
> 
> On Thursday, April 24, 2014 2:55:35 AM UTC+9, Peter Bienstman wrote:
> 
>       http://mnemosyne-proj.org/download-mnemosyne.php
> <http://mnemosyne-proj.org/download-mnemosyne.php>
> 
>       Mnemosyne 2.3 : 2014-04-15
> 
>       (Note that for Windows users we recommend uninstalling the
> previous version
>       before installing the new one.)
> 
>       The sync protocol has changed in this version, so make sure you
> update both
>       the client and the server at the same time.
> 
>       -A quick-and-dirty Android client is available, where you can do
> reviews in
>        your mobile browser using a webserver which runs on your Android
> device.
>        This client has full support for the syncing protocol.
>       -The functionality of mnemosyne-webserver has now been merged
> into the main
>        program and can be activated through 'Configure Mnemosyne -
> servers'.
>       -Time to create backups has decreased, in some situations even by a
> factor
>        of 2 or more, speeding up syncing and program exit.
>       -Sped up all editing operations in the card browser.
>       -The name of the currently active saved set of cards is now listed in
> title
>        bar (requested by Silverbear).
>       -Added new statistic: number of new cards learned per day.
>       -Also sync relevant settings (e.g. fonts, colours, ...) during the 
> initial
>        sync.
>       -Improve the timeout handling of the sync protocol.
>       -New Ukranian, Swedish, Serbian, Catalan translation.
>       -Fix erroneous 'Wrong username or password' error.
>       -Rework error handling when trying to load a database which no
> longer exists
>        in its previous location.
>       -Keep the sort order in the card browser when editing cards
> (reported by
>        Gnome and Tristan).
>       -Added command line options --sync-server and --web-server which
> starts the
>        sync and the web server in headless mode (i.e. without a GUI)
> (useful to
>       run
>        e.g. on a NAS server).
>       -Fix more errors coming from loading config files (thanks to Alex
> Fevery for
>        reporting this).
>       -Added an extra popup to guide new people better through the
> learning
>       process
>        (feedback from Bjorn Maes).
>       -Fix crash when exporting to cards format when Latex was not
> installed
>        (reported by Gwern).
>       -Make card conversion more robust for badly formatted card
> (reported by
>       Gnome).
>       -When editing a card through the browser, make sure the correct set
> of tags
>       is
>        displayed if sister cards have different tags (requested by Scott
>       Youngman).
>       -Allow converting a Cloze card to a clone of a Cloze card through the
>       browser
>        (requested by Scott Youngman).
>       -Instruct people on the correct way to deal with '*.cards' files if they
> try
>        to open it as a separate database (Kensor0).
>       -Make it clearer what 'Find duplicates' does.
>       -Various cosmetic fixes when importing *.cards files (reported by
> Ansgar
>        Bohmann).
>       -Fix tag tree sometimes not updating correctly if the user adds a new
> tag.
>       -People writing e.g. Javascript card and needing access to the full
> path of
>        the media directory can now use db_media:///foo.png (requested
> by Gnome).
>       -Flash files are now synced as well (reported by heldtfisken).
>       -When editing a card where different sister cards have different tags,
> ask
>       if
>        the tags should be applied to the current card or to all sister cards.
>       -Fix Windows crash when using the card browser with cards imported
> from
>        Supermemo (reported by Piotr).
>       -Fix crash when renaming cloned card types through the card
> browser.
>       -Make Mnemosyne 1.x import more robust (reported by Jack Thro).
>       -Don't allow saving the database to a network drive under Windows
> to prevent
>        corruption (reported by Brendan Sinclair).
>       -Fix sync error that could occur when adding and immediately
> deleting
>       multiple
>        sister cards from the card browser.
>       -Fix latex / cloze interaction corner case (reported by Daniele Parisi).
>       -Fix corner case of overzealous introduction of media dir in expansion
>       (reported by Toni Alsford).
>       -Make sure latex images are always in sync when updating text.
>       -If adding an extra tag when importing a 'cards' file, don't keep the
> tag
>        'Untagged' (patch by crcmail0). If you were affected by this issue
> before,
>        'compact database' will solve this.
> 
> 
> 
> --
> You received this message because you are subscribed to the Google Groups
> "mnemosyne-proj-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to mnemosyne-proj-
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mnemosyne-proj-users/082587d1-
> 796d-4c6c-90de-bace984e353c%40googlegroups.com
> <https://groups.google.com/d/msgid/mnemosyne-proj-users/082587d1-
> 796d-4c6c-90de-
> bace984e353c%40googlegroups.com?utm_medium=email&utm_source=foo
> ter> .
> For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
"mnemosyne-proj-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mnemosyne-proj-users/004e01cf6692%24297c8b00%247c75a100%24%40UGent.be.
For more options, visit https://groups.google.com/d/optout.

Reply via email to