> I am a bit worried about the "Update" functionality. I used it to get
> rid of the bug described earlier in this list by Wayne. There were
> two files to update and I updated both of them. Restarting Analysis
> then gave the same problem as before. Looking in Analysis.py (one of
> the files that should have been updated) the lines described by Wayne
> were not changed.
This was entirely my fault. I put the file in the update repository before
Wayne had entered the fix.
The version up now is hopefully OK.
> Is there any way of checking that a file really got updated? Is there
> for example a serial number or a time stamp? If not, perhaps that
> could be added?
Looking at the last modification time will hopefully let you see if
the upgrade was written. However, I'll think more on this matter. - I
expect a list of the various times in the upgrade popup will help.
The way that the update system works means that you only see an update if
the file on the update server is different to the version you have on
disk, i.e. if you do not see an upgrade, the repository version is
identical to your own (to the character).
Tim
-------------------------------------------------------------------------------
Dr Tim Stevens Email: [log in to unmask]
Department of Biochemistry [log in to unmask]
University of Cambridge Phone: +44 1223 766022 (office)
80 Tennis Court Road +44 7816 338275 (mobile)
Old Addenbrooke's Site +44 1223 364613 (home)
Cambridge CB2 1GA WWWeb: http://www.bio.cam.ac.uk/~tjs23
United Kingdom http://www.pantonia.co.uk
-------------------------------------------------------------------------------
------ +NH3CH(CH(CH3)OH)C(O)NHCH(CH(CH3)CH2CH3)C(O)NHCH(CH2CH2SCH3)CO2- -------
-------------------------------------------------------------------------------
|