I don't know of any issues specifically. Can you please reply with the whole block of code for the exit condition, exit statement and alert and I can have a look if anything seems amiss.
Ok, thanks for that. I just realised something. You have specified the dotted lines to be displayed on the current real-time bar because you are conditioning the lines on barstate.islast. The pine script manual states... "PineScript code that uses this variable could calculate differently on history...
Thanks for your reply and sorry I haven't been back to you for a while.
When you say "script should search Local Top as long as RSI rises Up after crossover", what do you mean by local top? I'm still trying to understand what local top means to you?
Yes, the theory of loading up the highest high values and bar_index over the last 20 bars into an array is good. I'd love to help but my experience with arrays is limited. Hopefully someone else can help you.
It may be a repainting issue with your request.security statements. The best way to fix this is for reference the prior bar when a real-time bar is updating such as this: tH = request.security(syminfo.tickerid, resolution, barstate.isconfirmed ? high : high[1], barmerge.gaps_off, barmerge.lookahead_...
Hey Ponderosa, Firstly when you copy code can you please indent if statements, custom functions and line continuations Your code is not compiling because of the 3rd line below does not assign anything to signal if signal == 1 or signal == -1 alert(message, alert.freq_once_per_bar_close) signal I'm a...
Hi Jari, I have questions about your criteria. I'm assuming rsiLongTrig & rsiTrig2 are the 2 standard RSI lines? You've said your criteria is... 1. trigger is ta.crossover(rsiLongTrig, rsiTrig2); this trigger stays on and waits for rsiLongTrig to go up (IS THAT JUST ONE BAR UP?) and make local top (...