Spotware
25 Feb 2015, 17:07

Do you mean that if the stop loss modification is not valid, it will return that error and the previous price of the stop loss will be kept?

Yes, exactly.

Spotware
25 Feb 2015, 16:18

Do you have an ETA on our ability to influence those parameters? 

We cannot provide an ETA, but it is planed.

Spotware
25 Feb 2015, 11:15

First of all, you need to obtain MarketSeries object for TimeFrame.Hour using MarketData.GetSeries method.

Second of all, you need to create an indicator over the obtained series: Indicators.ExponentialMovingAverage(h1Series.Close, 30).

Hope this helps. If not, we can recommend you to contact one of our Partners or post a job in Development Jobs section.

Spotware
24 Feb 2015, 16:35

Currently decimal values of SL and TP are rounded to the integer number of pips. Therefore minimal SL is 1 pip. We plan to change this behavior and allow decimal protection in the future.

Spotware
20 Feb 2015, 17:27

We can recommend you to contact one of our Partners or post a job in Development Jobs section.

Spotware
20 Feb 2015, 17:23

Dear Trader,

Changing this color is not currently possible. We will consider such functionality for future releases. Thank you for your suggestion.

Spotware
18 Feb 2015, 12:40

Or in other words, what happens if by the time the stop loss order modification reaches the server, the current price is bellow the stop loss order? Does it get fired automatically? Does it return an error?

If SL will be invalid it will not be applied. You will receive TRADING_BAD_STOPS error. You can easily check this behavior using Demo account.

Spotware
18 Feb 2015, 11:41

It is a rounding issue in backtesing. Commissions must are rounded to cents using math round rules. Examples: 0.009 to 0.01, 0.003 to 0.00. We will fix this issue as soon as possible. Thank you for reporting it.

Spotware
16 Feb 2015, 12:19

Currently it is not possible. You can only obtain current Margin Level from the Account object.

Spotware
16 Feb 2015, 12:18

This functionality is in our road map.

Spotware
16 Feb 2015, 12:16

GA stops if one of the following criteria meets:

• all possible parameter sets were backtested
• 25 iterations were done
• best fitness value was not improved during last 5 iterations

We plan to provide an ability to change the above settings.

Spotware
16 Feb 2015, 12:08

Probably there is an issue related to specific version of VS. We will have a look at it. If you can, try to use VS 2012 for debugging your algorithms.

Spotware
16 Feb 2015, 12:02

Dear Trader, we cannot provide an ETA but it is planned.

Spotware
16 Feb 2015, 12:01

Dear Trader,

We can recommend you to read the following API Guide:

/api/guides/indicators.

Hope this helps.

Spotware
16 Feb 2015, 11:56

News about when it will be available for the desktop version?

We cannot provide an ETA but it is planned.

Spotware
16 Feb 2015, 11:55

Thank you for this idea, we will consider it. By the way, you can also write a custom indicator that will show the described info. If you cannot code you can contact one of our Partners or post a job in Development Jobs section.

Spotware
16 Feb 2015, 11:48

Dear Trader,

We plan to release new version (1.29) to all brokers this week.

Spotware
16 Feb 2015, 11:46

We can recommend you to contact one of our Partners or post a job in Development Jobs section.

Spotware
16 Feb 2015, 11:45

RE:

AlexanderRC said:

Any news when this will be available when backtesting/optimizing?

It is not implemented yet, but it is planed.

Spotware
16 Feb 2015, 11:38

Thank you for this idea. We will consider it.