BUG: Line 5067 in Cumulus.cs
Posted: Sat 17 Jul 2021 8:29 am
This is not a serious bug, but a typo introduced when you presumably tried to tidy some of the code.
The code in Cumulus.cs reads from Cumulus.ini a parameter with attribute name LowTempAlarmSoundFile into a internal variable. MX used to write back that internal variable into the configuration file with the same attribute name.
Sometime (between release 3.8.2 and 3.10.4, but I am not wading through all your past commits to work out the exact build involved), a code rewrite in Cumulus.cs has introduced a bug (in the current release this in line 5067) as now MX is writing the internal variable back into Cumulus.ini using an attribute called LowTempAlarm.SoundFile i.e. a full stop as in the internal variable name has been introduced into the attribute name.
Consequently, If somebody decides to tidy up their configuration file, by deleting the file while MX is running and do a dummy "Save" on one of the settings pages to recreate the file, MX will lose any value associated with this setting!
The code in Cumulus.cs reads from Cumulus.ini a parameter with attribute name LowTempAlarmSoundFile into a internal variable. MX used to write back that internal variable into the configuration file with the same attribute name.
Sometime (between release 3.8.2 and 3.10.4, but I am not wading through all your past commits to work out the exact build involved), a code rewrite in Cumulus.cs has introduced a bug (in the current release this in line 5067) as now MX is writing the internal variable back into Cumulus.ini using an attribute called LowTempAlarm.SoundFile i.e. a full stop as in the internal variable name has been introduced into the attribute name.
Consequently, If somebody decides to tidy up their configuration file, by deleting the file while MX is running and do a dummy "Save" on one of the settings pages to recreate the file, MX will lose any value associated with this setting!