To help me further clarify this issue. Regardless of what changes are made, once they are activated by completing the programming session, these settings, whatever they may be, load each time. If this is the case, I'm not seeing the usefulness of the load previous setting options since the programmer would only be loading what is already saved, as shown in the first two tables of your example. The feature seems redudant in this format. I think this quote it what summarizes this.
Quote:
Originally Posted by Power Hungry
However, the next time you program and press Load Previous Settings, they will still be active. In this sense, all custom settings are cumulative, even those you made multiple sessions ago. Once an Option has been flagged as custom and a value selected for it, it will always be included in the Load Previous Settings.
|
However, the next quote below seems to be saying that the Load Previous Settings options can clear stored custom options, but only when chosen in the proper sequence. The two quoted statements seem to contradict each other regading the use of Load Previous Settings.
Quote:
Originally Posted by Power Hungry
If you select Custom Options, do NOT do Load Previous Settings, and then hit Done to begin programming, it does NOT clear any stored custom option status, it just doesn't use them this programming session.
|
Quote:
Originally Posted by Power Hungry
What I do think would be handy is a way to clear out any currently flagged custom options so it would be possible to start from scratch. I'll probably use a manual option like "Clear All Custom Settings" which will reset the status of all custom options.
|
It's people like me who need this option to be sure we don't screw anything up.
I'll get it eventually, but there doesn't seem to be any way to know if we are running the original tune or a custom, unless the unit is reflashed with an update back to original form.