If my computer's time is set to GMT+8 and I am tracking the forex spot markets in realtime I will encounter a timezone problem when my computer clock turns 12midnight. The daily history updates I get will add the new day (my time) to the most recent daily bar (which is understandable) but the bar before that is signalled as a completed day when in fact that day has not ended (forex goes by GMT+0 and Esignal triggers settlement price at approx. 2300hrs GMT)...so that bar's high, low, closing prices are inaccurate. I have sort of found a workaround for that. But what will happen when the market actually ends? Will the bar that formerly showed a premature ending be updated with the correct high, low and closing prices at the time when the market has reached settlement or will it wait for my computer clock to turn midnight again?
In a nutshell, this problem exists because the esignal application follows my computer clock and not the actual time at which the market ends...which I think should be the correct way to signal me for end of day. Since I can only set one timezone per computer, I am not able to manage other markets from other timezones at the same time! And I am not willing to pay for 1 esignal account for each timezone either.
Any suggestions or help here will be great.
p/s: To the Esignal staff, I hope someone will solve this problem soon because this is pretty major; incorrect data can lead to losses. I've been calling the technical helpdesk many times and no one could provide any solution that even comes close.
In a nutshell, this problem exists because the esignal application follows my computer clock and not the actual time at which the market ends...which I think should be the correct way to signal me for end of day. Since I can only set one timezone per computer, I am not able to manage other markets from other timezones at the same time! And I am not willing to pay for 1 esignal account for each timezone either.
Any suggestions or help here will be great.
p/s: To the Esignal staff, I hope someone will solve this problem soon because this is pretty major; incorrect data can lead to losses. I've been calling the technical helpdesk many times and no one could provide any solution that even comes close.
Comment