Problems with write-protected config files

Crystal tries to write to the config file in 2 situations:

1. When the user edits the configuration.
2. When crystal discovers some non-standard (but still parsable) XML.  

If the .conflictClient file is write protected, Crystal crashes and throws 
exceptions.  Instead, in case 1, Crystal should display a nice error message, 
and in case 2, Crystal should just ignore the error (log it) but not display 
any error and not throw any exceptions and not crash.  

Here is the users bug report:
"It's smart to make one's .conflictClient.xml file read-only, because
Crystal has an antisocial tendency to overwrite it if it has any syntax
error.  But, when Crystal tries to overwrite it, it crashes with a long
stacktrace because the file isn't writeable."

Original issue reported on code.google.com by yuriy.b...@gmail.com on 11 Aug 2011 at 11:06

brunyuriy / crystalvc

Problems with write-protected config files #31