max-td 

great infos mike ! thats the trick here i think! do you have a snipet for this enum auto-rename-routine ? or you know in wich indi you did this like this - that we can have a look at ?

No, but that's it, just name it the same as the Base name. The code I did was for people who hired me in the past.

Mike

ok thanks - so just manualy renaming the used ma_file too - should be no problem.

max-td 

ok thanks - so just manualy renaming the used ma_file too - should be no problem.

I avoid coding with these extra files, they are a pain. Just embed the public enum into the original base indicator file itself, and ditch the extra file.

Mike

Big Mike 

What is the full error? Your screen shot doesn't show it. But most likely, it's the maType enum, you probably have another indicator with a similar enum name. Change it to something unique in every instance of the file (Find/Replace, "maType" -> "ss_maType"). Mike

If I change this:

publicenum maType
{
SMA,
EMA,
};

To This:

publicenum TMFT_maType
{
SMA,
EMA,
};

Do I need to change this also:

case maType.EMA:
f = EMA(Input,FastAverage)[0];
break;
case maType.SMA:
f = SMA(Input,FastAverage)[0];
break;

Thank you for your time and consideration.

Yes:

 

Code

case maType.EMA:

should become

 

Code

case TMFT_maType.EMA:

There is also going to be a section down in #Properties for the input parameter that will need to be changed as well.

Mike

BTW,

To prevent spacing issues and word wrapping when posting code on the forum, you should paste Code wrapped inside the [code ] wrapper (the # sign on the toolbar above is code), that way the spacing and stuff is preserved.

Mike

Big Mike 

Yes:   Code case maType.EMA: should become   Code case TMFT_maType.EMA: There is also going to be a section down in #Properties for the input parameter that will need to be changed as well. Mike

That worked!

Thanks!