Have you ever wanted to compare two Monticello .mcz files that do not
appear in each other's history?
Did you come across the 'changes against ...' menu option in the yellow
button menu in version list in Repository browser?
Were you puzzled why it gives you a 'does not understand snapshot' error
when you tried to use it?
Did you figure out it happens after you have previously used 'flush cached
versions' on the repository?
Did you find out that as a workaround, you can first use the 'Browse'
button on the version selected and then it will work?
Did you shrug and went right ahead with whatever you were doing before
never trying to figure out what was the issue here?
I did all those things.
It bothered me because 'changes against ...' is the way I like to use to
compare my .mcz packages.
The packages in the Repository browser's version list definitely exist
unlike the ones in the History's list. So there should never be a 'does not
I wanted 'changes against ...' to just work.
First I figured out how to modify it so that the list it presents to you is
limited to only the versions displayed in the right pane of the Repository
browser. And also for it to be sorted. According to the order selected in
the same yellow button menu.
I have uploaded that first iteration to the Inbox and it got moved to the
Trunk by dtl. Thanks Dave!
This iteration of 'changes against ...' fixes the 'does not understand
If you are using 'changes against ...' you want this. You will never see
the 'does not understand snapshot' error again after you use the 'flush
cached versions' menu option in Monticello Browser.
Why would you ever use the 'flush cached versions' menu option you wonder?
Well if you remove .mcz files from a Monticello directory repository with a
file manager such as FileList the Repository browser will refuse to forget
them even if you press the Refresh button and it will keep seeing the
versions it has cached. After you use 'flush cached versions' and do
Refresh, they will finally disappear.
What are you waiting for?
Download this iteration of 'changes against ...' now!
You will be rewarded with never having to work around the 'does not
understand snapshot' bug.