5,838
edits
Amending dayfile: Difference between revisions
m
→Using the Cumulus MX editing functonality
m (add note at top) |
|||
| Line 51: | Line 51: | ||
If you do have a 'duplicate' error, you need to decide which row to ''delete'', and whether to copy any values from that row into the row you are keeping to ensure the correct extremes are retained. | If you do have a 'duplicate' error, you need to decide which row to ''delete'', and whether to copy any values from that row into the row you are keeping to ensure the correct extremes are retained. | ||
= Using the Cumulus MX editing | = [[File:Badge vMx.png]]Using the Cumulus MX editing functionality= | ||
*'''Cumulus MX beta version 3.0.0 (checked at build 3043) does not provide an editor''' | |||
*'''Cumulus MX Version 3.4.5 - Build 3069 onwards provides an editor''' | |||
*From MX release 3.9.2 - b3097 historic charts are added to admin interface | |||
**If you use the in-built editor to update dayfile.txt, your change will be reflected in the historic graphs | |||
**If you edit dayfile.txt outside Cumulus MX, historic graphs will not be updated until Cumulus MX is restarted | |||
There is a dayfile.txt editor within the admin interface to edit this log file. In the '''Edit''' menu, choose the '''Dayfile''' option. | There is a dayfile.txt editor within the admin interface to edit this log file. In the '''Edit''' menu, choose the '''Dayfile''' option. | ||
| Line 82: | Line 89: | ||
As all lines are passed back via an application programme interface to the MX engine, there is no validation there either, the new line replaces the old one when the whole file is recreated. It is likely that the next time MX attempts to read the dayfile.txt it will find any error. There was a third-party proposal to add simple validation into a replacement editor, that would hav | As all lines are passed back via an application programme interface to the MX engine, there is no validation there either, the new line replaces the old one when the whole file is recreated. It is likely that the next time MX attempts to read the dayfile.txt it will find any error. There was a third-party proposal to add simple validation into a replacement editor, that would hav | ||
Pick '''Delete''', click that, and a simple dialog pops up (MX uses '''altEditor ''' software for this) showing all the fields in the selected line and asking you to confirm that you want to delete it. Again, the labelling on the buttons varies depending on which version you are running, one confirms the deletion (which sends the array back to the MX engine with an instruction that line number is to be deleted. Despite the MX engine getting a copy of the fields that are to be deleted, it does not validate the fields, just the line number. The button labelled 'Close' or 'Cancel' does the same effect as clicking the "x" in the top right corner, it prevents the api sending any deletion message back to the MX engine. | Pick '''Delete''', click that, and a simple dialog pops up (MX uses '''altEditor ''' software for this) showing all the fields in the selected line and asking you to confirm that you want to delete it. Again, the labelling on the buttons varies depending on which version you are running, one confirms the deletion (which sends the array back to the MX engine with an instruction that line number is to be deleted. Despite the MX engine getting a copy of the fields that are to be deleted, it does not validate the fields, just the line number. The button labelled 'Close' or 'Cancel' does the same effect as clicking the "x" in the top right corner, it prevents the api sending any deletion message back to the MX engine. | ||
= Important Rules when editing dayfile.txt = | = Important Rules when editing dayfile.txt = | ||