It uses your cBot's timezone. If there isn't one set, it's UTC+0
Well, that's annoying. According to the way it's implemented, if I wanted any cBot to log in local time for the time zones I go through because I travel often, I would have to update, recompile, and redeploy the bot every single time I cross a timezone to update the bot instances with the timezone I'm in?
Who decided that?! O.M.G. face palm
cTrader can certainly determine if the cBot is running locally (and not in the cloud), and can also determine if there's a timezone set or not.
If I start a cBot on a VPS that's set for my local time zone running an instance of cTrader bot locally (not in the cloud) set to the current timezone I want to use, then why doesn't the bot, by default if no time zone is specified and it's running locally, use the local time zone?!
It makes more sense to use the timezone the user has selected in cTrader in than a default UTC+0.
This is not something that works out of the box, automatic timezone detection needs to be developed. Feel free to post a suggestion in the Suggestions and we will consider it for future releases.
This really shouldn't have to be a suggestion.
Seriously, who releases software so that when a user changes time zones, the user needs to recompile and redeploy their code to pick up the new time zone?
When a bot is loaded, and before it's started, cTrader should already know if a timezone is specified or not from the bot's header directive.
If there is none specified, Spotware should read the timezone the user sets in cTrader itself.
Otherwise, what's the point of having that?
Again, facepalm
I'll save Spotware's team 10 seconds with this link:
I appreciate your contribution to the community but I cannot tolerate such language. Please respect the forum and consider this as a warning. I have developed hundreds of strategies and almost all of them need a fixed timezone regardless where the cBot is running. Decisions need to be taken at specific times no matter if the code is executed in London, New York or Beijing. Your suggestion is not as brilliant as you think. Adopting your suggestion would be devastating for many strategies. This should be an explicitly requested option in the cBot and not the default setting. However, over the last 13 years, not many people requested this, hence it was never implemented.
cTrader just prompts you to restart whenever it is more convienient for you. Disabling updates completely is not possible due to the nature of our service.
Best Regards,
Panagiotis
hi Panagiotis
I really can't take it with the new Ctrader optimization speed , it is not practical at all and i need to stick to Ctrader 4.x without update until you solve this issue . besides the Ctrader 5.x optimization tabs are really of no use . . I want to stay with Ctrader 4.x interface and performance
Hi Tarek,
You can still use your broker's application that has not been updated yet.
Unfortunately there is no way to do this. Hopefully such changes do not happen often. What you could do would be to monitor the connection i.e. receiving heartbeats from the server. If your application stops receiving heartbeats, it should notify you.
Thank you for reporting this issue. Could you pleasesend us some troubleshooting information when this happens? Please paste a link to this discussion inside the text box before you submit it.
This would need a lot of work since you would need to define your requirements better e.g. what should cross the line if not the price. If you need professional assistance, you can contact a consultant.
WebView is used to display some parts of the UI. Regarding the processes, this is handled by Microsoft's internal logic, therefore we cannot advise regarding the number you see in the task manager.
It uses your cBot's timezone. If there isn't one set, it's UTC+0
Well, that's annoying. According to the way it's implemented, if I wanted any cBot to log in local time for the time zones I go through because I travel often, I would have to update, recompile, and redeploy the bot every single time I cross a timezone to update the bot instances with the timezone I'm in?
Who decided that?! O.M.G. face palm
cTrader can certainly determine if the cBot is running locally (and not in the cloud), and can also determine if there's a timezone set or not.
If I start a cBot on a VPS that's set for my local time zone running an instance of cTrader bot locally (not in the cloud) set to the current timezone I want to use, then why doesn't the bot, by default if no time zone is specified and it's running locally, use the local time zone?!
It makes more sense to use the timezone the user has selected in cTrader in than a default UTC+0.
This is not something that works out of the box, automatic timezone detection needs to be developed. Feel free to post a suggestion in the Suggestions and we will consider it for future releases.
PanagiotisCharalampous
29 May 2024, 06:45
Hi there,
This will be fixed in the upcoming hotfix.
Best regards,
Panagiotis
@PanagiotisCharalampous