OK mate I did a submit with the issue but I think I found that if I do a build inside CTrader it will then work. So something was out of sync perhaps with VS and2022 and Ctrader perhaps?
Thanks mate but I don't see how that is going to help you, maybe if I could send you a stack trace/symbolic dump or something?
The error occurs before the bot gets to debug. I have tried a clean rebuild etc. I just cloned one bot to make changes and it happened after making changes to the clone. I will reclone again and see if I get the problem again before making any changes.
Thanks @PanagiotisCharalampous. Is there a temporary solution/hack I could use locally while you're guys finishish a proper fix? It's just a showstopper that stops the whole work I'm doing.
Unfortunately there isn't. It seems that some data of the specific broker is corrupted and needs to be fixed
Ok, clear. How long do you think it will take to fix the data? Are we talking more days or weeks?
Hi there,
The data is the responsibility of the broker. What we will do is to fix the method so that it does not hang when there are no data for the specific symbol. Unfortunately we do not have ETA for this fix at the moment.
It sounds like a problem with your connection to the proxy server. Pleasesend us some troubleshooting information the next time this happens? Paste a link to this discussion inside the text box before you submit it.
This function should solve the comma problem on the textbox. When I enter floating point text with the period, the function should replace the period with the comma. But it doesn't work, what am I doing wrong? or is there a better solution to do this? Thanks you Panagiotis.
private void TextBox_TextChanged(TextChangedEventArgs obj){ char oldChar = '.'; char newChar = ','; string str = obj.TextBox.Text; for (int i = 0; i < str.Length; i++){ if (str[i] == oldChar){ str.Replace(oldChar,newChar); } } Quantity = Convert.ToDouble(str); }
It seems you haven't read the documentation carefully :) You don't need a for loop and the method does not work on the current string, it returns a new one with the character replaced.
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.
Hello. I sent a report via the form on cTrader this saturday. No response yet.
Regards /danerius
Hi danerius,
The team has received the troubleshooting information and they are investigating the issue.
Thanks mate but I don't see how that is going to help you, maybe if I could send you a stack trace/symbolic dump or something?
The error occurs before the bot gets to debug. I have tried a clean rebuild etc. I just cloned one bot to make changes and it happened after making changes to the clone. I will reclone again and see if I get the problem again before making any changes.
Please send us some troubleshooting info and quote the link to this discussion by pasting a link to this discussion inside the text box before you submit it.
Best Regards,
Panagiotis
OK I sent!
I wait for a response!
Tks!
I think it's a problem related to the new accounts (DEMO (possibly?!?!?!)).
No matter if I have newly opened account on spotware, topfx, icmarkets... The problem is the same... I cannot do backtesting tests without checking the VISUAL box, or in the optimization tab.
I asked a friend to log in into my computer with his older account and everything seems to be working normally. (So, it is not a computer problem !!!)
If I log in, with my account (which is a newer account than his) backtesting and optimization no longer work.
Do you have a solution to this problem? Please if you have to post it, I am bored of writing... monologue!
Thanks!
Hi,
As explained above, this issue will be resolved in an upcoming update. We do not have any other solution at the moment. If you have found a workaround i.e. using a different account, then you could use it.
Thanks for reporting this. 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.
IsLastBar is just a boolean indicating if the Calculate() method is executing on the last bar of the chart. Calculate() is called once for every historical bar and on every tick for the current bar.
We have received the troubleshooting and it is under investigation.
Best regards,
Panagiotis
Hello
Since the last post there were much fewer disconnections (1-2 a week) and I thought this issue was taken care of. Unfortunattly since about a week ago the problem came back and there are disconnections every few hours (about 5-10 disconeections happend last week). I was able to send troubleshooting within 3-4 minutes of the disconnection with a reference to this post.
I'm looking forward to hear from you.
Thanks
Hi eynt,
Troubleshooting received, our team is investigating.
PanagiotisCharalampous
22 Jan 2024, 06:54
Hi there,
Please share with us the following
Best regards,
Panagiotis
@PanagiotisCharalampous