public enum myType

[Camdo]

Does anyone know how to make an enumeration type private to a Ninja script?

With NT7 enum could be defined within the indicator class in the region "variables".

public enum myType { }

A renamed copy of the indicator could be produced without any problem.


With NT8, enum needs to be defined outside the NameSpace and outside of the indicator class. So it is truly public. When a renamed copy of the indicator is created, an error is produced that the myType is already defined. This requires renaming myType so it is unique for each indicator.

What I want is an enumeration type that is private to the Ninja script, but I don't know how to produce it. Any assistance or code examples would be appreciated.

[tradesmart]

I place my enums in their own script to make them available to all indicators. In this way, copying an indicator that uses an existing enum does not need to rename it.

[NinjaTrader_ChelseaB]

Hi Camdo,

Enums should be outside of the class of the indicator and outside of the NinjaTrader namespace.

Below is a link to the reference sample on using enums.

http://ninjatrader.com/support/forum/showthread.php?t=3420

tradesmart's advice is sound if you would like to use the enums for multiple scripts.
I also recommend putting these in your own namespace to prevent conflicts with other developers who may by change use the same enum names.

Last, below is a link to an advanced script that modifies the descriptions for enums.

http://ninjatrader.com/support/forum/showthread.php?p=490303#post490303

[Harry]

I understand that enums should be outside of the class of the indicator and outside of the NinjaTrader namespace.

Should I use a separate namespace for containing the enum (as you recently did) or simply follow the sample provided here

http://ninjatrader.com/support/forum...ead.php?t=3420

and not use an additional namepsace.

What is the difference?

[NinjaTrader_ChelseaB]

Hello Harry,

This is your preference.

I add my enums to a custom namespace so that they do not cause conflicts with anyone else who happens to make a script that uses the same enum names. (Just by chance I have seen two developers use the same enum name and didn't place this in a custom namspace so the scripts conflicted and only one could be imported at a time)

[Harry]

Hello Harry,

This is your preference.

I add my enums to a custom namespace so that they do not cause conflicts with anyone else who happens to make a script that uses the same enum names. (Just by chance I have seen two developers use the same enum name and didn't place this in a custom namspace so the scripts conflicted and only one could be imported at a time)

I have also seen this and will consider using namespaces in future.

Thank you for your answer.