Spotware
29 Aug 2014, 11:10 ( Updated at: 21 Dec 2023, 09:20 )

When going back from cAlgo to Visual Studio I get an annoying warning that file has been change outside of VS when in fact it was not.

Steps to reproduce.

1. Disable code reformat in cAlgo.
2. Open any indicator and add an instance of it in cAlgo.
3. Invoke Edit in Visual Studio.
4. Make some changes and save the file.
5. Go back to cAlgo (it should display the changed file without any warnings)
6. Hit F5 to build the .algo file and update the instance.
7. Go back to Visual Studio and be annoyed by an unneeded warning.

Because cAlgo has code reformat disabled it should not update the timestamp on the file by saving it again when building. I am doing build in cAlgo because it is faster than in VS and F5 instantly shows me the updated instance on the chart.

We plan to fix this issue.

And by the way the built-in editor does not autocomplete attribute members like [Parameter("Foobar", DefaultValue = "moobar"]. When I type def it shows me only default as an autocomplete suggestion instead of DefaultValue.

Unfortunately, auto-completion improvements are not in our short term roadmap.

Spotware
29 Aug 2014, 10:51

Thank you for your idea. We will consider it.

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
28 Aug 2014, 11:04

Dear Traders,

Do you still observe the issue?

Spotware
28 Aug 2014, 11:04

Dear Traders,

Do you still observe the issue?

Spotware
28 Aug 2014, 10:59

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

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
27 Aug 2014, 17:04 ( Updated at: 21 Dec 2023, 09:20 )

Tick data backtesting has been released:

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

Tick data backtesting has been released:

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

Tick data backtesting has been released:

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

Tick data backtesting has been released:

Spotware
27 Aug 2014, 16:09

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

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
27 Aug 2014, 15:59

Thank you for your idea, we will consider it.

Spotware
27 Aug 2014, 15:58

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

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
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
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
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
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.