1) After the recompile of the code (even with a change of the default parameter values), the parameters of the indicator or signal on the chart remain the same as before. This perhaps is not a big deal and can be accepted.

2) After the parameters were reordered in the code, the values of those on the chart are all mixed up. This should be treated as a bug.

3) After the recompile of the code (even with no change to the default parameters), the optimazation interface adopts the values of the recompile code rather than those on the chart. For consistency, parameters on optimazation interface should go with those on the chart.

4) After a set of parameters were accepted after an optimization, the interface at the next optimization (without recompile of the code in between) still keeps the range settings from the last optimization. For ease of operation, all ranges should be reset and the values should be taken from the chart.

The current way is very inconvenient. I hope my suggestions make sense.

1) After the recompile of the code (even with a change of the default parameter values), the parameters of the indicator or signal on the chart remain the same as before. This perhaps is not a big deal and can be accepted....The current way is very inconvenient. I hope my suggestions make sense.

We do not want any chart parameter values to change after recompilation. We have the same indicators applied to different charts, of different resolution, with different settings. If a recompilation changes the parameters, then all the charts will lose their set values. It will be a nightmare to re-adjust all the charts back to their desired settings.

A few different ways of handling cause some headache....2) After the parameters were reordered in the code, the values of those on the chart are all mixed up. This should be treated as a bug....The current way is very inconvenient. I hope my suggestions make sense.