Daily Pivot Points

[QuantKey_Bruce]

When you save a copy of it, your code still have the same enumerations with the same names. You'll have to change those if they're public or they will conflict with the one you made a copy of.

[NinjaTrader_BrandonH]

Hello kiro1000,

Thanks for your notes.

QuantKey_Bruce is correct and has provided some great advice.

The public enums would need to have a unique name such as "MyHLCCalculationMode" instead of the default "HLCCalculationMode".

PivotsTypeConverter would also need to be changed to something like "MyPivotsTypeConverter"

And, on line 456 "(Pivots) value" would need to be changed to the name of the indicator, such as "(PivotsMyPIVOTS) value"

[kiro1000]

Hello,

Thank you Bruce and Brandon for your message and guidance.

Thank you very much Brandon for your clear and very well explained answer.

I've implemented the recommended changes, ensuring unique names for public enums, such as "MyHLCCalculationMode" and "MyPivotsTypeConverter." The adjustments compiled successfully, and I appreciate your assistance.

However, when attempting to load the indicator on the chart, a message box displayed the following :

Unhandled exception: Impossible to cast an object of type 'NinjaTrader.NinjaScript.Indicators.MyPivots' in type 'NinjaTrader.NinjaScript.Indicators.Pivots'

Thanks and best regards,

[NinjaTrader_BrandonH]

Hello kiro1000,

Thanks for your notes.

To resolve this error message you would need to edit the TypeConverter around line 33 to reflect the correct name.

This code below:

[TypeConverter("NinjaTrader.NinjaScript.Indicators. PivotsTypeConverter")]


Should be changed to something like this:

[TypeConverter("NinjaTrader.NinjaScript.Indicators. MyPivotsTypeConverter")]

[kiro1000]

Hello Brandon,

Thank you for your prompt response and guidance.

I've successfully made the suggested change in the TypeConverter around line 33, updating it to reflect the correct name.

I'm pleased to share that it works !

Your assistance has been invaluable in resolving this issue

Thanks again for your support