FXCodeBase.COM: Forex Chart Indicators and Development

The indicator shows the time remaining until the close of the last bar.



Download:



MT4 version
https://fxcodebase.com/code/viewtopic.php?f=38&t=71500

Hi. Thanks for the indicator.

Just want to let you know that there's a bug. Because the indicator is based on the operating system's clock, it doesn't work with any computer that is not set to the same timezone as the server.

Thanks again.

The indicator was revised and updated.

Hi Apprentice,

Would I please be able to have a version of this indicator that displays 3 times instead of one. Either side by side or one on top of the other so the inner is one time the middle is the time traded and the outer is a larger time..

For example I trade the m5 chart and would like to see the m1, m5 and H1 times displayed.

Hope you can help.

Cheers!!

Time_Left times three added.

Awesome!! Thank you.

FxLowe wrote:Hi. Thanks for the indicator.

Just want to let you know that there's a bug. Because the indicator is based on the operating system's clock, it doesn't work with any computer that is not set to the same timezone as the server.

Thanks again.

To fix.

REPLACE

function now()
if __debug__hook ~= nil then
return core.host:execute("convertTime", core.TZ_EST, core.TZ_LOCAL, core.now());
else
return win32.currentTimeLocal();
end
end

WITH

function now()
return core.host:execute("convertTime", core.TZ_LOCAL, core.TZ_SERVER, win32.currentTimeLocal());
end

Hi Apprentice,

I'm not understanding the way time is calculated in TS V Marketscope.

Two things have me puzzled.

Firstly the changes I used in the post above only work in Marketscope to correctly set the time to count down for a new Daily candle appearing on the chart for the local machine reguardless of display time settings.


If you drag the same chart from Marketscope to TS the time to the end of the daily candle (Right Hand Clock) Changes from a count down to the next daily candle to a count down to 00.00 Server time again reguardless of local display time settings.


Can you explain how Marketscope and TS treat time differently and how to correctly work with time for time based Indicators / Strats. I assume that Strats use the time from Marketscope?

I'm also Not Understanding how the Time/Date is treated by Strats and Indicators in relation to Hourly and Daily Candles. A new Daily candle forms at 00.00 Server Time but the hourly candles Do not change to the new date until 9 hrs later.



How is this treated for example when using a MVA based on D1 as a filter for a Strat running on a H1 time frame using Local time? Does the Strat calculate start of the daily period correctly for Daily at Local time or is the Server time used as with the chart display?

Thanks for your help.

Cheers,
Mark

OK Previous fix does not work.

The Server time for MS is not the same as for TS. At least not in Australia. The other problem I had was overcoming the Daylight Saving offset because I live in a time zone where there is Daylight Saving but our State does not observe it putting me out by one hour. The previous did seem to overcome that but just simply does not work in any other time zone or in Market Scope.


So. A better solution for me in Queensland Australia is simply to and add an offset to UTC time in min. If you are in a timezone that has Daylight Saving and you observe it or no Daylight Saving at all I think win32.currentTimeLocal() would work better.

If Daylight Saving gives you hell.

ADD TO INIT

indicator.parameters:addInteger ("TIMESET", "TIME Offset", "Offset from UTC to Local Time in min.", 1);

REVISED NOW FUNCTION

function now()
local TIMESET = instance.parameters.TIMESET;
return win32.currentTimeUTC() - (TIMESET * 60 / 86400);
end

Fixed.
Proposed solution is not correct as well.