Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
this explains why you only see 0 for the milliseconds, as you are asking for the ending time stamps of the bars.
Hover over the bars and check the exact time that MC displays. You will see that all end with 0 seconds and milliseconds.
Now apply your code to a tick chart and you should get different values or check
plot2(MillisecondsFromDateTime(ComputerDateTime)); on minute charts.
I need to see time frame = 1 minute.
And want a indicator that show the time of change from last close price to last close price.
For example:
18h:36m:12s:125mm, price is at level 2830
18h:36m:12s:525mm, price is at level 2830 (new tick at the same level, not relevant)
18h:36m:12s:725mm, price is at level 2831 (new tick at NEW level)
And then indicator shows: 0.600 (because .725-.125)
IntrabarOrderGeneration = true, to update in real time the value of indicator
But, "if close <> close[1]" it means a new close on 1 minute bar. And I need a new close (level) on the price.
Each new closing level then:
t2(last time) = t1
t1 = new time
...and then plot t1-t2
you are welcome. By the way you can show your appreciation for posts on futures.io by clicking the "Thanks" button next to a post.
You will require two variables for that on each code calculation store the value of the first variable in the second and then store the current close in the first variable. This way you can compare the value of the last two real time ticks.
Sorry but I dont understand
Historical bar is no problem, it works on real time.
You say: "You will require two variables for that on each code calculation store the value of the first variable in the second and then store the current close in the first variable. This way you can compare the value of the last two real time ticks."