ADXVMA raw code

Discussion in NinjaTrader

Updated March 16, 2011

2,822 views
0 thanks given
0 followers

Search this Thread

ADXVMA raw code

ADXVMA raw code (post #106298)

jtrade · 2011-03-16T09:32:50-04:00

I just did something very stupid : importing the .cs file ADXVMA v.01.5.2, I thought I'd just paste it over the ADXVMA file already in NT7. However, I now realise that the plain ADXVMA must have imported as part of another indicator, as I am generating an error as it can no longer be accessed. I cannot import, say DoubleMA (one of the indis that is trying to access it), until I fix the error, so I'm thinking if I can paste the correct code back in, all will be well (and I'll import the v.01.5.2 .cs file correctly via my indicator folder). So, I would be really grateful if someone would please post this code for me - not being a programmer, I am unsure what to cut and paste from any of the existing ADXVMA variations). . J. EDIT : issue solved - I had it in 6.5 and it appears to be the same, so fixed. Apologies for not working this out before posting

March 16th, 2011, 10:32 AM	#1 (permalink)
jtrade near Amsterdam Elite Member Experience: Advanced Platform: NinjaTrader Trading: (M)ES, (M)NQ Posts: 328 since Feb 2010 Thanks Given: 442 Thanks Received: 337	I just did something very stupid : importing the .cs file ADXVMA v.01.5.2, I thought I'd just paste it over the ADXVMA file already in NT7. However, I now realise that the plain ADXVMA must have imported as part of another indicator, as I am generating an error as it can no longer be accessed. I cannot import, say DoubleMA (one of the indis that is trying to access it), until I fix the error, so I'm thinking if I can paste the correct code back in, all will be well (and I'll import the v.01.5.2 .cs file correctly via my indicator folder). So, I would be really grateful if someone would please post this code for me - not being a programmer, I am unsure what to cut and paste from any of the existing ADXVMA variations). <red face> . J. EDIT : issue solved - I had it in 6.5 and it appears to be the same, so fixed. Apologies for not working this out before posting !