5,838
edits
Cumulus.ini (preserving history): Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Do I need to restart MX?
m (COUPLE OF TYPOS) |
|||
|
#SETTINGS THAT TAKE EFFECT IMMEDIATELY ON CLICKING “SAVE”
#SETTINGS THAT ONLY TAKE EFFECT WHEN MX IS RESTARTED
Unfortunately, there is no documentation available from developer on which settings, at any release, do not take effect until MX is restarted, a further complication is that in some releases, certain settings that used to require a restart have been changed so they take effect intermediately. This means that any attempt to document which changes do require a restart is working against a moving target, so this documentation cannot indicate where a restart is required. You can play safe, and restart MX each time you finish making edits to settings.▼
There used to be a third group. Before '''Release 3.11.2 - build 3131''' a few changes made in the interface were not saved into "Cumulus.ini", and therefore lost when MX was restarted. One example of these former exceptions was on Program Settings page where the former action was that choice for [[MXdiags folder|adding extra debugging information to file in MXDiags folder]] was not saved for subsequent session.
For the current MX release, any change made (on any settings page) will be saved into "Cumulus.ini", and will still apply when MX is restarted. That restart will ensure all settings changed in the last session do take effect, even those that did not take effect before the restart.
▲Unfortunately, there is no documentation available from developer on which settings do not take effect until MX is restarted, so this documentation cannot indicate where a restart is required. You can play safe, and restart MX each time you finish making edits to settings.
==Program settings==
| |||
