|Member since:||05 May 2012|
Last Forum Posts
@What's New in cTrader Desktop 4.6: 25 Jan 2023, 20:09
Mind-blowing update guys! Really thank you!
@Renko backtesting: 02 Jan 2023, 21:53
Thanks for the answer. Did you create your own backtester too?
Spotware team, could you answer my question too?
A number of years ago they announced it was on the roadmap. But they won't commit to a release date and it didn't even appear as an option on their recent feature survey.
Now they've completed the major upgrade to .Net 6 they will hopefully have more resources for new features. But there's no sign that Renko/Range/Tick backtesting is a priority.
So I wouldn't be holding my breath.
Personally I'm developing my own solution. I'm using cTrader as a tick-feed, market venue, optimiser and reporter, but generating my own bars, indicators and charts.
This is non-trivial, but does give me the opportunity to test a wider range of bars. The cTrader feed is limited to classic Renko without tails and a limited selection of Range bar sizes, which is too limiting for my own trading.
@Renko backtesting: 27 Dec 2022, 09:59
Do you have an implementation of the Renko backtesting in your roadmap? If yes, could you estimate in which version we should get it?
@How to debug using Rider/VS Code?: 06 Nov 2022, 20:08
At the moment only Visual Studio is supported for debugging,
Thanks for providing support for other IDEs than VS, but debugging is also crucial. Do you have plans to add it in the upcoming releases?
The biggest disadvantage of this solution is that I have to disable "Targets" for each chart separately.
Panagiotis Charalampous said:
Right click on Chart > Viewing Options > Targets.
@cTrader 3.0 - Performance issue.: 07 May 2018, 21:21
Ok, I will do it in free time. Please tell me what working hours you have in Spotware and could you provide me your email address, I'm going to contact with you before.
Panagiotis Charalampous said:
We cannot reproduce this behavior consistently internally. Could you please contact me at firstname.lastname@example.org? Our engineers would like to have a more closer look and maybe we can arrange a remote connection via TeamViewer.
@cTrader 3.0 - Debugging (PDB files): 06 May 2018, 13:57
Thanks for your response, but as you know cAlgo is build-in cTrader 3.0 and you can attach only to this process.
Moreover "Debug" is default option used by VS during compilation and I didn't change it to "Release" mode.
I've fixed problem and debugging is working now on both VS2015 and VS2017.
Debugging using Visual Studio 2015 or 2017 does work with cTrader, take a look at the link below which also has a video showing you how to do this, make sure your build configuration is set to Debug and not Release, if you still have an issue it will be the Visual Studio IDE and not the trading platform.
@cTrader 3.0 - Debugging (PDB files): 03 May 2018, 19:55
I'd like to notice that the debugging doesn't work for cAlgo 2.01 (Pepperstone).
Please confirm this issue.
@cTrader 3.0 - Debugging (PDB files): 01 May 2018, 20:40
My breakpoints can't be hit because there are no PDB files loaded to Visual Studio 2017. Can you tell me where can I find them or give me a hint how to debug cBots in VS 2017 and cTrader 3.0?
Like in topic. How can I remove it? Is there any option in Settings panel?