Hi, new to the forums, new to ProRealTime programming. First off, having some C coding experience the concept of the code iterating through each bar automatically is a concept I need to get used too. In C/C++ you would need to code that element too.
I am working through Advanced programming > Loops > Descending loops and got to the code
Descending Loop
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
ema20=average[20,1]
ema50=average[50,1]
result=0
FORx=100DOWNTO0DO
result=result+(ema20[x]>ema50[x])
IFresult=50THEN
BREAK
ENDIF
IFresult<30THEN
CONTINUE
ENDIF
IFresult=30then
signal=30
ELSE
signal=0
ENDIF
NEXT
returnresult,(ema20>ema50),signal
My question (probably the first of many) is that as noted in the ‘IF result = 30 THEN signal = 30’ test, once ‘signal’ is equal to 30 it gets set at 30. However the true value of ‘signal’ is 30 or below and does not get reset to 30 again until ‘signal’ moves above 30. Isn’t his poor programming? Shouldn’t ‘signal’ get reset to zero just after the last ENDIF and before NEXT. I realise that this is just a teaching exercise but want to make sure I understand this correctly. Or is it simply dependant on exactly what you are trying to achieve? Thank you for your time.
Thank you for that JS. I guess what I am trying to say is aren’t we getting false information? We do in fact have values of 30 or less (hypothetically they could in reality be 5, 10 ,20) but looking at the signals on the indicator they are all showing 30. So the indicator is surely showing incorrect information? In the previous code without, the CONTINUE instruction, we only generate two signals at 30, which is surely correct. That is why I thought ‘signal’ should get reset to zero just after the last ENDIF and before NEXT.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
.
