Hi SummaCollege, Checking what has changed in the definitions of the built-in settings is a manual process, unfortunately: create a new config file based on a Windows Common Setting or Applic...
See more...
Hi SummaCollege, Checking what has changed in the definitions of the built-in settings is a manual process, unfortunately: create a new config file based on a Windows Common Setting or Application Template, Expand it, and compare it to your own config file... (Which is probably what you had in mind already There's definitely things we can improve in this functionality. The problem, as is so often the case, is that we have limited resources. Compare functionality would be cool, but is most probably not going to happen – too much effort for something with limited value (in that there is not a lot of customer demand for this). I'll keep track of your interest, though. However, it might be feasible to at least keep track of the fact that a Flex config file was originally created based on a built-in setting which was then expanded, and at least notify you in case that setting is subsequently updated. No guarantees as to when or whether this might happen, but I'll definitely give it some thought. Happy to receive feature requests, no worries!