Alltime.ini: Difference between revisions

388 bytes added ,  15:29, 18 May 2020
m
Line 71: Line 71:
=== Editing alltime.ini within Cumulus ===
=== Editing alltime.ini within Cumulus ===


Expanding what it says in FAQ: [[FAQ#How_do_I_correct_my_all-time_.28or_monthly.29_records.3F]], the stored values can be corrected using the ''All time records'' screen on the '''Edit''' menu and this Cumulus editor allows you to read from the [[dayfile.txt|daily log]] or the [[Monthly_log_files]]. Therefore, normally any rogue values are corrected in these source files, and resulting lows and highs copied across to the all time log using the in-built editor.  However, you can also just edit any low, high or timestamp manually looking at [[Alltimelog.txt]] for current and previous values.
Remember, normally any rogue values are corrected in the monthly or daily log files first, and then resulting lows and highs are copied across to this all time log file using the in-built editor.  However, you can also just edit any low, high or timestamp in this log file manually after looking at [[Alltimelog.txt]] for current and previous values.
 
Both Cumulus 1 and MX have internal editors for this file.
 
Expanding what it says in FAQ: [[FAQ#How_do_I_correct_my_all-time_.28or_monthly.29_records.3F]], the stored values can be corrected in Cumulus 1 using the ''All time records'' screen on the '''Edit''' menu.
 
For Cumulus MX the editor is found in the admin interface.
 
Both Cumulus editors allow you to read from the [[dayfile.txt|daily log]] or the [[Monthly_log_files]], in case you created rogue values there first as advised above.  In the cumulus 1 editor you can click to copy figures across, in the MX editor you can only manually overwrite with the revised figure.


=== Editing alltime.ini outside Cumulus ===  
=== Editing alltime.ini outside Cumulus ===  
5,838

edits