New Cropper forgets settings


Don't know if it is specific to my system (XP SP2), but the new version of cropper forgets my preferences whenever I reboot or start cropper from scratch... The old version did not.
Once Cropper is open and in my tray, there are no problems and it works great. I'm just trying to figure out why the preferences keep getting wiped.
Closed Jul 18, 2013 at 11:44 PM by TerryHughes
If there still remains a problem with settings not being saved, please open a new issue.


chiacomo wrote Dec 16, 2007 at 3:35 AM

I never used cropper before, but I notice the same issue. It appears to remember where I want to save the captured images, but it forgets the format (JPG) and always comes up with BMP selected... Great app, thanks!

wrote Jan 11, 2008 at 9:22 AM

wrote Jan 13, 2008 at 11:42 AM

cyx7 wrote Jan 13, 2008 at 11:50 AM

Same issue here w/ v1.9.1.89.
Not a single setting is saved between sessions.
I tried editing the .config files to no avail.
Oh well, more billable hours for me :)

fearthecowboy wrote Jun 10, 2008 at 2:58 PM

This happens when there is a plugin that is misbehaving on saving the configuration data.

I removed the 'S3' plugin and my problem went away.


bradleach wrote Oct 23, 2008 at 1:44 PM

I just started using Cropper and see the same issue. I always want to save PNG's to my Desktop. I always have to set these things when I start Cropper. Also, I noticed that Help->About doesn't work. Otherwise, the tool works well.

wrote Oct 23, 2008 at 1:49 PM

wrote May 27, 2009 at 1:13 PM

wrote Jul 10, 2009 at 4:55 PM

wrote Aug 6, 2009 at 12:20 PM

TerryHughes wrote Nov 20, 2009 at 4:14 AM

The Help->About issue was corrected in Change Set 29275

wrote Nov 13, 2010 at 10:26 PM

Cheeso wrote Dec 17, 2010 at 1:45 PM

A common cause of this issue, is a faulty plugin. When a plugin generates an exception upon trying to serialize its settings, none of the cropper settings get saved.
This was happening with the S3 plugin, for example. It was also a problem with the email plugin. When those plugins would throw exceptions during serialization, Cropper silently swallows the exceptions. (There are a couple of code snips that read "catch (Exception ex1) {}" in the persistence layer.) Because the save of cropper.config was just a write, and not a write+copy, an exception in any plugin resulted in cropper.config being interrupted, and illegal XML. At the next start Cropper would try to read the file, and fail, and then revert to default settings.

There are a couple of code changes required to fix this. First, fix the plugins so they don't throw on serialization.
This happened v1.3 of cropperplugins (http://cropperplugins.codeplex.com). Second: fix Cropper to notify the user when saving of configuration throws. Third, use a 2-phase write+copy approach to saving config data. Only replace the known-good cropper.config if no exceptions occurred saving the new one.

I'm a coordinator on cropperplugins so I can do (and have done) the necessary work there. I'm not a member of the cropper project so I cannot implement the proposed fixes required here.

wrote Dec 24, 2010 at 9:08 PM

wrote Feb 27, 2012 at 10:54 PM

Configuration updated with two step save and user is notified if an error is encountered during save.

wrote Feb 27, 2012 at 10:55 PM

wrote Feb 27, 2012 at 11:08 PM

wrote Feb 27, 2012 at 11:34 PM

wrote Feb 22, 2013 at 12:26 AM

wrote May 16, 2013 at 11:38 AM

wrote May 16, 2013 at 11:38 AM

wrote Jun 14, 2013 at 7:31 AM

wrote Jul 18, 2013 at 11:44 PM