I'm fairly new to programming indicators, so this is probably a basic question. I'm trying to load The "Volume Patterns" indicator in NT7. For some reason the software won't let me import indicators the easy way and says there are files that have programming errors (and I should correct them before I can import).

So I extracted and copied the .cs files to the /bin/Custom and /bin.Custom/Indicators folders (not sure which to use) I was told I need to activate (install) the indicator by bringing it up in the editor and F5 compiling it. When I hit compile I get an "Error Generating Indicator" message "The namespace 'Ninjatrader.Indicator' already contains a definition for 'Volume Patterns' " I looked at the Ninjascript but don't see any type of duplicate definition.

As I said I'm new to this, and its probably simple, but I can use some suggestions.

It is telling you that you already have an indicator named VolumePatterns. I believe this should help you out.

Find this line of code...

 

Code

public class VolumePatterns : Indicator

Change to....

 

Code

public class NewVolumePatterns : Indicator

Press F5 to compile.

DennisA 

I'm fairly new to programming indicators, so this is probably a basic question. I'm trying to load The "Volume Patterns" indicator in NT7. For some reason the software won't let me import indicators the easy way and says there are files that have programming errors (and I should correct them before I can import). So I extracted and copied the .cs files to the /bin/Custom and /bin.Custom/Indicators folders (not sure which to use) I was told I need to activate (install) the indicator by bringing it up in the editor and F5 compiling it. When I hit compile I get an "Error Generating Indicator" message "The namespace 'Ninjatrader.Indicator' already contains a definition for 'Volume Patterns' " I looked at the Ninjascript but don't see any type of duplicate definition. As I said I'm new to this, and its probably simple, but I can use some suggestions.

Thanks MooreTech. There didn't seem to be another indicator with the same name, but changing the code to a new name fixed the problem.

Dennis