Do you have any documentation on how the server works in tick modes, because I have any issue while coding IF-THEN AND WHILE.DO in tick mode

the following code is OK

ONCE FutTime=40000
ONCE s=2*pipsize
CH=Hour
CM=Minute
//CMC=Minute
CloseTime=Close
CT=Time
CTC=Time
BI=barindex
Y=high
v=volume
DRAWTEXT("Time: #CT#" , BI, Y+10*s)
DRAWTEXT("Current time: #CTC#" , BI, Y+9*s)
DRAWTEXT("FutTime: #FutTime#" , BI, Y+8*s)
DRAWTEXT("Volume: #v#" , BI, Y+7*s)
DRAWTEXT("Close0: #closeTime0#" , BI, Y+6*s)
DRAWTEXT("Close1: #closeTime1#" , BI, Y+5*s)
DRAWTEXT("Close2: #closeTime2#" , BI, Y+4*s)
DRAWTEXT("Close3: #closeTime3#" , BI, Y+3*s)
DRAWTEXT("Close4: #closeTime4#" , BI, Y+2*s)
DRAWTEXT("Nb hits: #CountMM5M15#" , BI, Y+1*s)


IF CT > FutTime AND CT<220000 Then
while yabug=CountMM5M15 do // and add a while as the kludge is the basic kludge
closetime4=closeTime3
closeTime3=closeTime2
closeTime2=closeTime1
closeTime1=closeTime0
closeTime0=closetime
CountMM5M15=CountMM5M15+1 // This is the basic kludge while end
Y=close
s=-s
DRAWTEXT("Time: #CT#" , BI, Y+10*s)
DRAWTEXT("Current time: #CTC#" , BI, Y+9*s)
DRAWTEXT("FutTime: #FutTime#" , BI, Y+8*s)
DRAWTEXT("Volume: #v#" , BI, Y+7*s)
DRAWTEXT("Close0: #closeTime0#" , BI, Y+6*s)
DRAWTEXT("Close1: #closeTime1#" , BI, Y+5*s)
DRAWTEXT("Close2: #closeTime2#" , BI, Y+4*s)
DRAWTEXT("Close3: #closeTime3#" , BI, Y+3*s)
DRAWTEXT("Close4: #closeTime4#" , BI, Y+2*s)
DRAWTEXT("Nb hits: #CountMM5M15#" , BI, Y+1*s)
DRAWTEXT("Yarg: #yarg#" , BI, Y+1*s)
s=-s
y=y+1
WEND // works better if placed here
IF CM < 58 then
futmin=(ROUND(CM/2)+1)*200
IF FutMin < 6000 THEN
FutTime=(CH)*10000+FutMin
ELSE
FutTime=(CH+1)*10000+FutMin-6000
ENDIF
IF FutTime > 210000 then
FutTime= 040000 // make sure we do not collect value between 21:00:00 and 4:00:00 (fixed timings depending on local TZ)
CountMM5M15=0
ENDIF
ENDIF
// WEND // logic fails if placed here
ELSE
yabug=CountMM5M15 // This is the basic kludge, Invert IF condition and use a while to kludge
ENDIF
Return

The following code does not change the programming logic, the WEND is moved a few line below,  but the execution is not correct and FutTime ss not updated accordingly

ONCE FutTime=40000
ONCE s=2*pipsize
CH=Hour
CM=Minute
//CMC=Minute
CloseTime=Close
CT=Time
CTC=Time
BI=barindex
Y=high
v=volume
DRAWTEXT("Time: #CT#" , BI, Y+10*s)
DRAWTEXT("Current time: #CTC#" , BI, Y+9*s)
DRAWTEXT("FutTime: #FutTime#" , BI, Y+8*s)
DRAWTEXT("Volume: #v#" , BI, Y+7*s)
DRAWTEXT("Close0: #closeTime0#" , BI, Y+6*s)
DRAWTEXT("Close1: #closeTime1#" , BI, Y+5*s)
DRAWTEXT("Close2: #closeTime2#" , BI, Y+4*s)
DRAWTEXT("Close3: #closeTime3#" , BI, Y+3*s)
DRAWTEXT("Close4: #closeTime4#" , BI, Y+2*s)
DRAWTEXT("Nb hits: #CountMM5M15#" , BI, Y+1*s)


IF CT > FutTime AND CT<220000 Then
while yabug=CountMM5M15 do // and add a while as the kludge is the basic kludge
closetime4=closeTime3
closeTime3=closeTime2
closeTime2=closeTime1
closeTime1=closeTime0
closeTime0=closetime
CountMM5M15=CountMM5M15+1 // This is the basic kludge while end
Y=close
s=-s
DRAWTEXT("Time: #CT#" , BI, Y+10*s)
DRAWTEXT("Current time: #CTC#" , BI, Y+9*s)
DRAWTEXT("FutTime: #FutTime#" , BI, Y+8*s)
DRAWTEXT("Volume: #v#" , BI, Y+7*s)
DRAWTEXT("Close0: #closeTime0#" , BI, Y+6*s)
DRAWTEXT("Close1: #closeTime1#" , BI, Y+5*s)
DRAWTEXT("Close2: #closeTime2#" , BI, Y+4*s)
DRAWTEXT("Close3: #closeTime3#" , BI, Y+3*s)
DRAWTEXT("Close4: #closeTime4#" , BI, Y+2*s)
DRAWTEXT("Nb hits: #CountMM5M15#" , BI, Y+1*s)
DRAWTEXT("Yarg: #yarg#" , BI, Y+1*s)
s=-s
y=y+1
//WEND // works better if placed here
IF CM < 58 then
futmin=(ROUND(CM/2)+1)*200
IF FutMin < 6000 THEN
FutTime=(CH)*10000+FutMin
ELSE
FutTime=(CH+1)*10000+FutMin-6000
ENDIF
IF FutTime > 210000 then
FutTime= 040000 // make sure we do not collect value between 21:00:00 and 4:00:00 (fixed timings depending on local TZ)
CountMM5M15=0
ENDIF
ENDIF
WEND // logic fails if placed here
ELSE
yabug=CountMM5M15 // This is the basic kludge, Invert IF condition and use a while to kludge
ENDIF
Return

Hi Roberto, Nicolas

I work with ticks that can range from 200 to 10000 ticks per bar.

I neeed to get the price that was given @12h00:00 sharp, I do not want to get the price that would be the close at the end of the candle (on a 2000 tick candle, that could be delayed by more than 15 minutes easily).

I can get that price after the candle is closed, but I need the price that was current @12h:00:00 and not the one current at the close of the bar instead.

I go from problem to problem with the implementation of the graph tick mode that does not provide a correct CurrentTime.

PRT does provide Time, but it does not authorize to store a price value sampled at a precise Time.

I made a test moving the WEND as a possible kludge but it doesn’t work better.

I am stuck.

ThanksRoberto.

Let’s say I have a bar starting at @11:55:25 and closing @12:17:54.

I am able to retrieve the price value at the tick just after 12:00:00 (or just before), that is not a problem. My problem is to store that value for good into a variable, and keep it unchanged.

I need to use the price that was @12:00:00 later in the afternoon, let say at 16:43:45 or whatever else time in the afternon.

All my tests show that I will not store the value of the price @12:00:00, but PRT will retain only the price of the bar close (i.e. the close @12:17:54). And this is biased data for me.

Sorry about my snippet of code, at line 3 CLOSE shall be replaced with:

close[1]

It’s because OpenTime is the time a candle opens, replace it with TIME, instead.

Being totally incorrect does not exist!

IT IS correct according to the TF or Number of TICKS you selected. If you want a greater accuracy you need to decrease the number of ticks, up to 1, still in this case, as I wrote some posts ago, there can be ticks with no price movement (actually there are no ticks).

At any one time, no matter whether you are using time-base or tick-based charts, in case there is no movement (ticks) at the time you are monitoring, the correct value for that time is the previous known one!

Yes, that would be doable if there were no graph constraints.

But I also need visuals in 200-10000 tick periods. ANd with a very low number of ticks displayed, 1 would get a graph that is too fast.

Like: if I had this issue on a 1 hour graph, I don’t want to kludge it by displaying a 5 second or a 1 minute graph, this without seeing any signal on my hourly chart.