Tested a bit and the problem seam to be that when adding new crop definitions to the crop datatype, the stored property data doesnt contain the new defintion and therefor the rendering of the positions of the old crop defenition fails and revert back to the default position.

Property data example:

<crops date="2010-09-14 08:17:40"><crop name="test" x="0" y="417" x2="351" y2="768" url="/media/238/creek_test.jpg" /><crop name="test2" x="674" y="0" x2="896" y2="222" url="/media/238/creek_test2.jpg" /><crop name="test3" x="266" y="642" x2="560" y2="768" url="/media/238/creek_test3.jpg" /></crops>

<crops date="2010-09-14 08:17:40"><crop name="test" x="128" y="0" x2="896" y2="768" url="/media/238/creek_test.jpg" /><crop name="test2" x="128" y="0" x2="896" y2="768" url="/media/238/creek_test2.jpg" /><crop name="test3" x="0" y="164" x2="1024" y2="602" url="/media/238/creek_test3.jpg" /><crop name="test4" x="0" y="0" x2="698" y2="768" url="/media/238/creek_test4.jpg" /></crops>

So basicly you cant add new definitions to a crop datatype as all old positions will be lost. Should we add this to codeplex as a bug or?

is working on a reply...