FXCodeBase.COM: Forex Chart Indicators and Development

Margin requirements are defined per account and symbol. To get these values you should use either O2GTradingSettingsProvider.getMMR or O2GTradingSettingsProvider.getMargins method.

You can find the example of usage of the methods in TradingSettingsProviderSample.cs or TradingSettingsProviderSample.cpp provided with ForexConnect API:
C:\Program Files\Candleworks\ForexConnectAPI\samples\cs\WholeSample\TradingSettingsProviderSample.cs
C:\Program Files\Candleworks\ForexConnectAPI\samples\cpp\WholeSample\source\TradingSettingsProviderSample.cpp

As for including PointCost and MMR in tables, I've passed your request to the development team. May be the values will be available with the release of table manager.

frAnton wrote:Another issue:
O2GMessageRow.Text is in Base64(?) format.

O2GMessageRow.Text can be either a plain text or text in Base64 format. I've passed the issue to the development team.

Just a quick remark:
you guy are doing a great job with this ForexConnect API, I like it very much, it works very fast, and it is easy to develop the code based on it.
When can we expect next release of it?

thanks,
Anton.

Thank you, Anton.
The next beta release is expected in the beginning of June. This version will include JNI wrappers and Android support. Besides, a couple of minor modifications and fixes will be made in this version (e.g. RollS and RollB columns will be included in the Offers table).

sunshine wrote:Margin requirements are defined per account and symbol. To get these values you should use either O2GTradingSettingsProvider.getMMR or O2GTradingSettingsProvider.getMargins method.

Thank you for your answer,
Are you guys doing to introduce O2GResponseType.TraddingSettingsUpdate?
It would be helpful.

thanks,
Anton.

When the trading settings are updated on the server for a particular user, the session is always dropped, so there is just no such server notification.

Hi Nikolay,

Nikolay.Gekht wrote:When the trading settings are updated on the server for a particular user, the session is always dropped, so there is just no such server notification.

Thank you for explanation, so if the session dropped then what should the client expect O2GSessionStatusCode.Disconnected, O2GSessionStatusCode.SessionLost, or both?

thanks,
Anton.

May depend on the reason of the disconnecting. For sure, you'll get Connected state finally. I also asked developers to prepare exact state machines for session status. These must be published soon.

sunshine wrote:a couple of minor modifications and fixes will be made in this version (e.g. RollS and RollB columns will be included in the Offers table).

Would you please add PointCost field as well?
I assume it should be added per account and be accessible through O2GTradingSettingsProvider.

thanks,
Anton.

frAnton wrote:Thank you for explanation, so if the session dropped then what should the client expect O2GSessionStatusCode.Disconnected, O2GSessionStatusCode.SessionLost, or both?

If the session dropped then client receives:
1) O2GSessionStatusCode.SessionLost;
2) O2GSessionStatusCode.Disconnected.
The new article "Session statuses" was added to online help. See,
http://www.fxcodebase.com/documents/For ... tatus.html.
Best regards.