Spotware
02 Sep 2014, 14:16

Thanks for the suggestion we will consider it. 

Spotware
02 Sep 2014, 13:59

RE:

oguti said:

It would be possible to implement an Undo/Redo in graphics?

(For example, if I delete a line or other object accidentally, it could be recovered with CTRL+Z)

Regards

Thank you for your idea, we will consider it.

Spotware
02 Sep 2014, 12:04

jdaerial, could you please post the screenshot with the problem?

Spotware
02 Sep 2014, 09:57

In Minute bars data mode we generate 4 ticks (open, high, low, close) for every m1 bar.

Spotware
02 Sep 2014, 09:50

Thank you for your idea. We will consider it. Currently we plan to provide an ability to load tick data from a CSV file.

Spotware
02 Sep 2014, 09:47

RE: Ctrader Failed to save workspace - cannot connect to CHUB

jdaerial said:

Hi there,

I've been trying to login to Ctrader ID for desktop to save my workspaces - keeps coming up with an error message saying that workspace cannot be saved due to Chub not connecting.

Any ideas?

Thanks,

 

jdaerial, please press Shift+Ctrl+Alt+T. It will send us troubleshooting information.

Spotware
02 Sep 2014, 09:44

You can already modify stop losses and take profits by dragging it on the chart.

Spotware
01 Sep 2014, 11:57

mijo212, please check cAlgo 1.24. We optimized GetSeries method.

Spotware
01 Sep 2014, 11:56

cbellew, please check cAlgo 1.24. We optimized GetSeries method.

Spotware
01 Sep 2014, 11:07

RE: RE:

hiba7rain said:

Thanks its fine on previous bar value , so if someone decide to go OnTick instead of OnBar the values would be accurate or still with some difference?

 

Spotware said:

OnBar event happens when new bar is opened. At that moment MarketSeries collection already contains tick from new bar. It means that last bar is not formed and in general cases open = high = low = close. If you want to access to last formed bar you need take previous one.

            Print("{0}", ema.Result.Last(1));

 

 

In case of usage OnTick handler last bar is a live bar as well. You need to use previous values if you want to calculate indicator based on formed bars.

Spotware
01 Sep 2014, 10:33

OnBar event happens when new bar is opened. At that moment MarketSeries collection already contains tick from new bar. It means that last bar is not formed and in general cases open = high = low = close. If you want to access to last formed bar you need take previous one.

            Print("{0}", ema.Result.Last(1));

Spotware
01 Sep 2014, 09:55

Unfortunately we cannot reproduce the issue. Please try specify the scenario.

Spotware
01 Sep 2014, 09:53

Please make sure that Periods of indicators are the same. Also, it is not clear how do you print values of indicator, because statement Print("{0}", ema) supposed to print name of indicator instead of its values.

Spotware
01 Sep 2014, 09:44

Chart objects are not supported in backtesting. We plan to implement it in the future.

Spotware
01 Sep 2014, 09:36

Thank you for your suggestion. We will add Undo/Redo buttons in the future.

Spotware
29 Aug 2014, 17:05 ( Updated at: 19 Mar 2025, 08:57 )

RE:

rkokerti said:

Please do something with cAlgo, always crashes...

If it is possible, please send code of your cBot to support@ctrader.com. We will use it for troubleshooting purposes only.

Spotware
29 Aug 2014, 15:13

cTrader Web does not support the new timeframes yet. We will implement these in the future.

thanks

Spotware
29 Aug 2014, 14:39

Does your trader still observe the issue?

Spotware
29 Aug 2014, 14:24

You can specify ScalePrecision property of Indicator attribute:

    [Indicator("Stochastic Oscillator", ScalePrecision = 0, AccessRights = AccessRights.None)]
    public class StochasticOscillatorIndicator : Indicator, StochasticOscillator

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.