arrow issues

[NinjaTrader_RyanL]

Hello Muratello,

You can search our extensive library of NinjaScript consultants to implement or provide NinjaScript coding services for you through the link below. Simply enter a consultant name or search by using our filter categories. Once you have identified your consultants of choice, please visit each consultant's site for more information or contact them directly to learn more!

• http://ninjatraderecosystem.com/Part...ultants.php#81

This NinjaTrader Ecosystem website is for educational and informational purposes only and should not be considered a solicitation to buy or sell a futures contract or make any other type of investment decision. The companies and services listed on this website are not to be considered a recommendation and it is the reader's responsibility to evaluate any product, service, or company. NinjaTrader Ecosystem LLC is not responsible for the accuracy or content of any product, service or company linked to on this website.

Please let me know if you have any questions, concerns or if I can provide any further assistance by responding to this thread at your convenience.

[Muratello]

Thank you for your report Muratello. Please change StringFormat to String.Format in your code. Please let us know if this does not resolve your query or if there are any other ways we can help.

Thanks to you for your answer, NinjaTrader_JessicaP.
Excuse me, I do not own programming. Would be grateful if who could complete this indicator for last version NT8.
Thanks.

[NinjaTrader_JessicaP]

Thank you for your report Muratello. Please change StringFormat to String.Format in your code. Please let us know if this does not resolve your query or if there are any other ways we can help.

[Muratello]

WoodiesCCIpanel v1.7 beta for NT7 in NT8

Hello,
The help is necessary. Converted in Converter the indicator WoodiesCCIpanel v1.7 beta for NT7 in NT8. At compilation in NT8 has given out 3 mistakes. Please, help it(him) to finish up to a working condition.
Thanks.

[simpletrades]

You have been very helpful so far and Paul was great in November.

[NinjaTrader_JessicaP]

As full development is ordinarily beyond the scope of the support we provide, and because I have reviewed with my colleagues and it seems you have a vendor relationship with NinjaTrader, please contact us at platformsupport[at]ninjatrader[dot]com with Attn:NinjaTrader_JessicaP and 1664455 in the subject line so we can assist further.

[simpletrades]

Also even if the bar after the arrow paints and then unpaints by the bar close I still do not want the next bar to paint since there was no second arrow in a row allowed.

[NinjaTrader_JessicaP]

I am glad you were able to add the code I was using successfully. It was intended more as an educational aid. If you could help me understand what our goal is by preparing something in the following format, I can help you turn this into C# code.

Format

• At time 1, I start my car
• At time 2, I turn on my headlights
• At time 3, I back out onto the street

I look forward to assisting further

[simpletrades]

It paints at 5 and unpaints at under 5 but it paints the bar following any bar that met the condition to generate an arrow even though saveBar = CurrentBar; was being used to prevent multiple arrows. In the screenshot the bar after the arrow painted and unpainted. The next bar which is also blue should not have painted at all.
I added your code to an up indicator painting blue but its identical.

// This flag will prevent repeat paints
        bool didPaint = false;
        /// <summary>
        /// Called on each bar update event (incoming tick)
        /// </summary>
       protected override void OnBarUpdate()
        {
              if (CurrentBar < 2) return; // do not process until first n  bars loaded. 
			 // We just painted the last bar
            if (didPaint)
            {
                didPaint = false;
                return;
            }

	
			// Condition set 1   
           if ( Close[0]> Open[0] &&Close[1]> Open[1] && Close[1]>High[2]    //prior green closed above its prior red or green high
			 &&    Close[0]-Open[0] >=(TickSize*dist))  
		{
			BarColor = Color.Blue;   saveBar = CurrentBar;
		// This is an example showing how you can prevent something from
              // repeating
              didPaint = true;
		}
				
							
	 	 if (( ((Close[1]> Open[1] && Close[1]>High[2]) == true)// && ((Close[2]>Open[2] && Close[2]>=High[3] 
			&& Close[1]> Open[1]) ==true  &&  ( Close[0]-Open[0] < (TickSize*dist) )&& Close[0]<Open[0] )                    
		   BarColor = Color.Violet; 
		
		 if (( ((Close[1]> Open[1] && Close[1]>High[2]) == true)// && ((Close[2]>Open[2] && Close[2]>=High[3] 
			&& Close[1]> Open[1]) ==true &&  ( Close[0]-Open[0] < (TickSize*dist) )&& Close[0]>Open[0] )                    
		   BarColor = Color.LimeGreen; 
		
		 
		}

[simpletrades]

I just loaded your indicator and realized it actually was about the paintbar not the arrow. The .cs name was deceiving, sorry.
At first it wasn't working but I removed a doji program that colors them yellow and replaced it with a different file and now the paintbar works.
I guess I'll find out tomorrow if it removes the paint whenever price retraces intrabar below the 5 ticks.

[simpletrades]

I don't need help on the arrows. Paul fixed that in November for me.
I need help not showing paintbars multiple times in a row meaning I am currently geting them but not wanting them on bars that follow down bars that met the close lower than prior low terms but don't have arrows because I already had an arrow bar during that downward run and didn't want repeats. I have code to prevent repeat arrows but I couldn't figure out how to use that CurrentBar- saveBar > 2 to not repeatedly color bars red at the 5 ticks bar after bar.

[NinjaTrader_JessicaP]

Thank you for this additional information simpletrades. The easiest way to prevent something from duplicating multiple bars in a row would be with a boolean flag. I have added such a switch as an educational aid to your arrows indicator. While I do not believe this will do exactly what you had in mind, if you study the code near my initials (JDP) you should be able to see how you can have more control over what happens in two consecutive bars. I will be happy to answer any questions I can.

[simpletrades]

Its not a question of v1 vs v2 on the same indicator that I uploaded.
There were 2 separate indicators I was calling type 1 for dots and type 2 for arrows but they did have versions I was tracking but you don't care.,
Each has the same situation with my wanting a paintbar on the very next bar that paints and unpaints depending on which side of 5 ticks its moved intrabar.
Its the paintbar only for the bar immediately and more importantly only after an arrow that I have problems writing,
The dots and its related paintbar works just fine and because for shorts its coded to require a downbar to close below its prior up bar's open it always has to follow a green up bar so since 2 dots in a row won't happen 2 paintbars in a row won't happen either so there is no need to code to prevent it. I'm satisfied with the type 1 short and the type 1 paintbar following that dot short signal.

The arrows having paintbars follow them are a problem because to signal the arrow they only require that a short close below the prior bar's low and doesn't require an opposite color bar so everytime that close lower than prior low sets up it sets up for the paintbar for the next bar too. Since the red paintbar is only meant to tell me when price is 5 or more ticks below open on the 'entry' bar I don't want lots of later bars painting.
You showed me how to prevent multiple arrows using CurrentBar- saveBar > 2, but I cant figure out how to prevent multiple painting.
These 2 sets of code were my attempt to tell it to stay violet or green on the second successive close below prior low--
if ((( Close[2]< Open[2] && Close[2]<Low[3])==true)
&& ( Open[0]-Close[0] <= (TickSize*dist)) && Close[0]<Open[0])
BarColor = Color.Violet;
if (((Close[2]< Open[2] && Close[2]<Low[3]) == true)
&& ( Open[0]-Close[0] <= (TickSize*dist) )&& Close[0]>Open[0] )
BarColor = Color.LimeGreen;

[NinjaTrader_JessicaP]

Hello simpletrades, and thank you for your questions. Would it be possible to let us know

• a brief description of every difference between your V1 dots and your V2 arrows we can help with
• if your dots and arrows draw correctly on your chart without any of your conditional trade logic you mentioned in your most recent post
• if you add Print statements immediately before your draw statements, are these reached with your conditional logic at appropriate times

We will be happy to assist further

[simpletrades]

I Had 2 programs that color dojis yellow.
To day I replaced one for the other and now that paintbar works--sort of.
I'm attaching the paintbar code this time and a screenshot.
The problem is that since lots of bars can meet this Close[1]< Open[1] && Close[1]<Low[2] without that prior bar being an arrow too because I use the line you provided to eliminate that... if ( Close[0]< Open[0] && Close[0]<Low[1] && CurrentBar- saveBar > 2)...
it still paints red at 5 ticks.
When I had it read like this, it didn't paint at all and Variables had this...private int saveBar = 0;
and onbar update read...
if ( ((Close[1]< Open[1] && Close[1]<Low[2]) == true)
&& ( Open[0]-Close[0] >=(TickSize*dist) ) && CurrentBar- saveBar > 2)
BarColor = Color.Red; saveBar = CurrentBar;
Can you fix that part?
Because this happened today I don't know if it removes red if it falls under 4 ticks or colors what should be a green next bar violet and cant find out until Tuesday unless you can tell by looking.