Topics
16 Nov 2023, 07:42
 1526
 1
15 Nov 2023, 10:36
 2672
 19
Replies

Spotware
29 Aug 2014, 10:51

Thank you for your idea. We will consider it.


@Spotware

Spotware
29 Aug 2014, 09:28

Dear Trader,

Thank you for your suggestion. We will consider it. Additionally you can post this idea to vote.spotware.com


@Spotware

Spotware
28 Aug 2014, 11:04

Dear Traders,

Do you still observe the issue?


@Spotware

Spotware
28 Aug 2014, 11:04

Dear Traders,

Do you still observe the issue?


@Spotware

Spotware
28 Aug 2014, 10:59

Please press Shift+Ctrl+Alt+T. It will send us troubleshooting information.


@Spotware

Spotware
27 Aug 2014, 17:13

RE:

stoko said:

Yep, testing it since yesterday. Pretty impressive! Thank you!

Does it include what the spreads and commission would have been for each tick?

Spreads are historical. Commissions are fixed and must be specified in backtesting settings.


@Spotware

Spotware
27 Aug 2014, 17:04 ( Updated at: 21 Dec 2023, 09:20 )

Tick data backtesting has been released:


@Spotware

Spotware
27 Aug 2014, 17:03 ( Updated at: 21 Dec 2023, 09:20 )

Tick data backtesting has been released:


@Spotware

Spotware
27 Aug 2014, 17:02 ( Updated at: 21 Dec 2023, 09:20 )

Tick data backtesting has been released:


@Spotware

Spotware
27 Aug 2014, 17:01 ( Updated at: 21 Dec 2023, 09:20 )

Tick data backtesting has been released:


@Spotware

Spotware
27 Aug 2014, 16:09

Thank you for reporting the issue. We will fix it.


@Spotware

Spotware
27 Aug 2014, 16:01 ( Updated at: 23 Jan 2024, 13:14 )

RE: RE:

philipduffney said:

admin said:

Yes. Please refer to Sample Buy Trailing and Sample Sell Trailing Robots in cAlgo as examples to code trailing stops.

 

 

 

PLEASE PLEASE PLEASE add trailing stop, my hands are tiring of changing it manually constantly and I do not want to switch to MT4 but may have to.

Trailing stop for existing positions was implemented a few months ago. Please visit [/forum/whats-new/1317]


@Spotware

Spotware
27 Aug 2014, 15:59

Thank you for your idea, we will consider it.


@Spotware

Spotware
27 Aug 2014, 15:58

Thank you for detailed explanation. We will fix this issue.


@Spotware

Spotware
27 Aug 2014, 15:37

Thank you for reporting this issue. This problem occurs if cBot prints several messages in one millisecond. We will fix it.

For now you can add some incremental prefix (like "0000012", "0000013", etc.) to every message and then sort cBot Log by Message column.


@Spotware

Spotware
27 Aug 2014, 15:08 ( Updated at: 21 Dec 2023, 09:20 )

Unfortunately, we cannot reproduce this problem. You can try to change system language for non-Unicode programs:


@Spotware

Spotware
27 Aug 2014, 10:08

RE: RE:

kricka said:

Spotware said:

It is a known issue. It can be reproduced on several Demo environments only. It will be fixed as soon as possible.

I have not experienced this issue until the last update on cAlgo on the 26th. Ontick seems not to respond to the code properly after the update.

Please fix this quickly.

kricka, please provide more details about the problem.


@Spotware

Spotware
26 Aug 2014, 19:25

It is a known issue. It can be reproduced on several Demo environments only. It will be fixed as soon as possible.


@Spotware

Spotware
26 Aug 2014, 17:18

RE:

strutch said:

 

 

Is there any prevision for the availability of this so much important tool ??

 

 

 

We are currently working on Optimization, but cannot provide an ETA at the moment.


@Spotware

Spotware
26 Aug 2014, 17:11

RE:

StormeNet said:

Hi,

I have the following exception happening:

25/08/2014 22:30:24.282 | Executing Market Order to Buy 10k EURCZK
25/08/2014 22:30:24.578 | ? Executing Market Order to Buy 10k EURCZK SUCCEEDED, Position PID24657760
25/08/2014 22:30:24.578 | USDCNH (Ask: 6.1574, Bid: 6.1524) False
26/08/2014 06:46:11.379 | Crashed in OnTimer with AlgoAbortedException: Exception of type 'Frontend.CrossDomain.Dispatchers.AlgoAbortedException' was thrown.
26/08/2014 06:46:12.887 | cBot "CreateTrades" was stopped for EURUSD, h1.

In my Ontimer I log to a csv file every 30 seconds but it stopped logging at 23:29 whilst the exception only happened at 6:47.

Any thoughts on the situation?

Did you press the Stop button?


@Spotware