BridgeClient MT4-MT4

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.74

2018-01-18 15:03:19
2018-01-18 15:03:19
  • The check for the minimum amount at closing orders is removed
  • Code refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.73

2017-11-27 16:27:44
2017-11-27 16:27:44

Code refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.72

2017-11-27 15:44:29
2017-11-27 15:44:29
  • On the client side automatic reload of configs *.symbol_links.ini and *.markups.ini is implemented when it changes
  • Code refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.71

2017-05-15 16:02:47
2017-05-15 16:02:47
  • The error of checking the prohibition of pending orders with the active setting of ProcessPendingsAsMarketOpen has been fixed.
  • Added logging of the prohibition of autosumbmission of pending orders with the active setting of ProcessPendingsAsMarketOpen
  • Added setting LogRequestBlocking, which activates the logging of blocked orders

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.70

2017-05-04 17:47:51
2017-05-04 17:47:51
  • Added DetectDealerCloseByLogs setting, which activates the mode of detecting and processing orders closing by the manager manually by spitting events in the log and sending to the server part a request for closing at the current price
  • The bug was fixed, as a result of which, with the active setting of ProcessPendingsAsMarketOpen, the postponements could be deleted after sending to the server part of the request for opening
  • Refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.69

2017-04-28 14:10:57
2017-04-28 14:10:57
  • Added AllowGroupSpreadDiff setting, which activates the use of the spread spread of the group
  • Refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.68

2017-03-16 19:41:08
2017-03-16 19:41:08
  • In the server side, an error was fixed, as a result of which logging with an external order was not always logged (LogOuterOrderLinking setting)
  • In addition to the accounts specified by the LicenseMonitorRecieverLogins setting, mail notifications will be sent to active accounts from the "manager" group whose status or comment satisfies the "LIC_MAN2, LIC_MAN2|*, *|LIC_MAN2, *|LIC_MAN2|*" or "LIC_MAN3, LIC_MAN3|*, *|LIC_MAN3, *|LIC_MAN3|*", and Push notification is also sent if MQID is specified, but in the case of LIC_MAN3 only when the LicenseKey
  • Code refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.66

2016-09-02 14:36:11
2016-09-02 14:36:11
  • Fixed bug with using DefaultMarkup setting

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.65

2016-08-19 17:58:13
2016-08-19 17:58:13
  • Server: added filter to detect stop-outs
  • Server: when the DiscardProcessedRequests setting is disabled, the deleted applications added by the plugin are deleted in a separate thread and defaults to a timeout of 5 seconds (the timeout value can be changed with the optional setting of ProcessedRequestDeleteTimeout)
  • Server: support for comments received from clients
  • Client: sending a comment "Bridge-OCC" for applications for closing canceled transactions
  • Client: Added logging and logging of failed client requests acknowledgments
  • Refactoring

BridgeClient MT4-MT4 (Products - MT4 Plugins) v. 0.0.0.64

2016-08-03 12:26:58
2016-08-03 12:26:58
  • Changed the logic of the work: the communication flow does not stop when changing the settings, and only reconnection occurs if the LiquidityProviderServer, LiquidityProviderPassword, LiquidityProviderClientName settings have changed
  • Added an optional ForceReconnect configuration for forced reconnection
  • For debugging purposes, the optional LogCommunicationStatsForce setting is added, which activates the recording of detailed communication statistics in the file NamePlugin.communication_stats.log
  • For debugging purposes, the optional LogOutLastState setting is added, which is used to output the plugin's current internal state to the log and to the log file
  • Changed the logic of the work: when restarting / stopping the server, the plug-in continues to work, provided that responses from the other party still arrive, or the last application was sent less than 20 seconds ago