After MacOs 5.0.1 Update, crashing issue is solved.
But I am facing some other problems right now.
As you can see from 2 videos below, same code, on same pair but getting different outcomes when I print results of combobox.SelectedIndex and combobox.SelectedItem
I'd also like to hear from Spotware some clarifications on this.
We have clarified several times how this works. What further clarifications do you need?
Best regards,
Panagiotis
Hi Panagiotis,
I don't think I've been involved in such discussions.
Could you please share these? I'd be glad to look into them.
Nevertheless, this is not only about explain how it works.
The main question here is what considerations might have led to the current design choice, which doesn't really seem to be logical/ intuitive at all.
In short: Traders should feel confident about any time references that are made available, both in the platforms and text files.
Hi ncel01,
The main question here is what considerations might have led to the current design choice, which doesn't really seem to be logical/ intuitive at all.
cBots work on UTC time unless explicitly requested otherwise by the programmer. This design choice has been made 13 years ago. Spotware in 2011 and Spotware in 2024 is not the same thing. So we cannot know the exact reasoning, neither we can defend it as the best. Most probably the reason was that the cBots should work as similar as possible to MT4 EAs, since back then the main target was EA developers to jump to cTrader. So I guess the main design consideration was to minimize the learning curve. Apart from that, the fact is that at the moment there are thousands of cBots running under the default UTC assumption and changing the logic would break their execution rules. Changing the current logic while keeping backwards compatibility would be a very complicated task. Hence the possibility of changing this is because 3-4 users asked for it, is almost non existent.
What about the SelectionStart property, any chance your team will implement it ? I managed to solve my initial problem using a lock + countdown to prevent the ObjectsUpdated event from firing when user is typing in a TextBox, but I now face a similar issue (aka the caret is jumping in front of the chars when typing).
I made a simple ValidateInput(TextBox) method to ensure the value entered in a TextBox matches some parameters: only one ‘.’ is allowed, max amount of decimal digits equals symbol.Digits, and append a ‘0’ if string starts with a ‘.’ I'm using this inside the TextChanged event handler. The method works fine, except the caret is jumping to the left if we append a ‘0’ or if the amount of decimal digits is too big. Since the text gets set in every case, I assume it really gets updated only if there is a difference between original text and filtered text, right? Here is the code, self-explanatory I believe :
private void ValidateInput(TextBox textBox)
{
string text = textBox.Text;
bool decimalPointFound = false;
int decimalDigits = 0;
StringBuilder filteredText = new();
foreach (char c in text) {
if (char.IsDigit(c)) {
if (decimalPointFound && decimalDigits < _symbol.Digits) {
filteredText.Append(c);
decimalDigits++;
} else if (!decimalPointFound) {
filteredText.Append(c);
}
} else if (c == '.' && !decimalPointFound) {
if (filteredText.Length == 0) {
filteredText.Append(0);
}
filteredText.Append(c);
decimalPointFound = true;
}
}
textBox.Text = filteredText.ToString();
textBox.SelectionStart = filteredText.Length; // Would be nice to be able to do that, effectively setting the caret position to end of text
}
Tyty, sea yah !
Hi there,
We do not have such plans at the moment, we can consider it in a later update.
Can you please provide more information about this issue e.g. steps to reproduce and some screenshots demonstrating what you are looking at?
Best regards,
Panagiotis
Hi
You can also test yourself in the backtest section; Add the Keltner Channels indicator and you will see that before starting each robot; The opening of the indicator is, for example, 50 pips away, but immediately after the start of the robot and the revelation of new candles; The opening of the indicator will quickly get closer to each other and it will show, for example, a distance of 5 pips. Photo 1 that I have attached is before the start of the robot and photo 2 shows shortly after the start of the robot. The same problem caused the robot that I wrote earlier based on this indicator and it worked correctly; It is now disabled after the recent update. I tried some similar indicators but they did not have this problem.
Thank you. We managed to reproduce this behavior and we will fix it in an upcoming update.
Thank you for your attention. Are you a member of the Ctrader technical team? How long does it take to provide the new update?
Hi there,
Yes I am. We cannot provide an ETA unfortunately. As soon as it is ready and tested, it will be released.
To be clear, it means no leverage with cryptocurrencies on the cTrader platform?
Edit : Regardless of the version of cTrader, regardless of the currency, whether on the demo account or my FTMO account, i cannot use leverage. And there is apparently nothing I can do about it.
The leverage is decided by the broker, not by the platform
Can you please provide more information about this issue e.g. steps to reproduce and some screenshots demonstrating what you are looking at?
Best regards,
Panagiotis
Hi
You can also test yourself in the backtest section; Add the Keltner Channels indicator and you will see that before starting each robot; The opening of the indicator is, for example, 50 pips away, but immediately after the start of the robot and the revelation of new candles; The opening of the indicator will quickly get closer to each other and it will show, for example, a distance of 5 pips. Photo 1 that I have attached is before the start of the robot and photo 2 shows shortly after the start of the robot. The same problem caused the robot that I wrote earlier based on this indicator and it worked correctly; It is now disabled after the recent update. I tried some similar indicators but they did not have this problem.
Thank you. We managed to reproduce this behavior and we will fix it in an upcoming update.
You need to check your symbol's leverage as well, through the active symbol panel, not only your account's leverage.
Best regards,
Panagiotis
Hello,
Thank you for your response!
Here's a screnshot of my symbol window. It seems all the crypto symbol are set on 1:1 leverage (forex has more than 1:1 leverage). (It's on Windows, but same problem on my Mac)
Edit : Same problem ("not enough money") with a demo cTrader account, despite the leverage in the window symbol :
It is done. I think I'll uninstall and reinstall it as soon as I have the time. That should fix the problem.
I have forwarded your video to the team. Please let me know if this fixes the problem.
Also could you pleasesend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
Can you provide more detailed information? Please share the cBot code and screenshots of the error message you receive so that we can reproduce this problem.
PanagiotisCharalampous
12 Jul 2024, 07:21
RE: Cbot in cloud
test-01 said:
Hi there,
Email notifications are not supported in the cloud.
Best regards,
Panagiotis
@PanagiotisCharalampous