MetaTrader 4 Build 600 with Updated MQL4 Language and Market of Applications Released - page 20
![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
after modifying the shortcut with "/portable" and launch my platform, how do i know i did okay and the platform is actually running in portable mode?
after modifying the shortcut with "/portable" and launch my platform, how do i know i did okay and the platform is actually running in portable mode?
after modifying the shortcut with "/portable" and launch my platform, how do i know i did okay and the platform is actually running in portable mode?
Just ask the client terminal for data folder (File - Open Data Folder). You should see the installation folder.
after modifying the shortcut with "/portable" and launch my platform, how do i know i did okay and the platform is actually running in portable mode?
Live trades timeout on a live account. Build 603. 2014-02-07 10:00 - 11:00 CET. 3 out of 4 attempted trades failed to execute sucessfully.
Order 1:
Order 2:
Order 3:
Order 4:
The terminal fails to preform one of its main functions reliably and is therefore unusable. I'll have to downgrade to build 509 until the new version actually works.
Same problem here, since this morning (build 602) - happens on all the brokers I use (7), both live and demo.
Hello,
My robot has started working strangely after 574 and even after 600. I'm using and testing it in visual mode since months and I have not seen such a unexpected behavior.
If you look to the figure below, the robot opened a BUYSTOP (indicated with blue arrow on the top of graph) and after a while it opens it as BUY (#3 buy stop 1.00 Eurusd at 1.3528 buy by tester at 1.3528 1.3527). The issue is that the test data has never reached to that level (highest 1.3514 at that timeframe). I guess this is not directly related with robot behavior since robot only opened a BUYSTOP. How tester could trigger BUY in this position?
Because of this I'm getting very different results after build 509. I wonder if somebody has experienced such a strange behavior after 509? Any possible suggestions to correct this? I have already complied my robot for 600 and cleared all warning messages. I guess this is not directly related with the robot but I cannot guess what it is and how to correct it.
Thanks in advance for any assistance.
PS: I'm using Build 600 and test data is produced from 1M %90 quality data from FXDD, converted up to 1Month data using period converter successfully ( as I'm doing since 6 months)
If you look to the figure below, the robot opened a BUYSTOP (indicated with blue arrow on the top of graph) and after a while it opens it as BUY (#3 buy stop 1.00 Eurusd at 1.3528 buy by tester at 1.3528 1.3527). The issue is that the test data has never reached to that level (highest 1.3514 at that timeframe). I guess this is not directly related with robot behavior since robot only opened a BUYSTOP. How tester could trigger BUY in this position?
Hi is the related to spread? Buy @ Ask price?
Hello,
My robot has started working strangely after 574 and even after 600. I'm using and testing it in visual mode since months and I have not seen such a unexpected behavior.
If you look to the figure below, the robot opened a BUYSTOP (indicated with blue arrow on the top of graph) and after a while it opens it as BUY (#3 buy stop 1.00 Eurusd at 1.3528 buy by tester at 1.3528 1.3527). The issue is that the test data has never reached to that level (highest 1.3514 at that timeframe). I guess this is not directly related with robot behavior since robot only opened a BUYSTOP. How tester could trigger BUY in this position?
Because of this I'm getting very different results after build 509. I wonder if somebody has experienced such a strange behavior after 509? Any possible suggestions to correct this? I have already complied my robot for 600 and cleared all warning messages. I guess this is not directly related with the robot but I cannot guess what it is and how to correct it.
Thanks in advance for any assistance.
PS: I'm using Build 600 and test data is produced from 1M %90 quality data from FXDD, converted up to 1Month data using period converter successfully ( as I'm doing since 6 months)
Hmm!
While struct MqlStr not change, it still is char * ;
But when I transfer to handle string MqlStr (char *), then it returns wchar_t * ;
wchar_t * -> char * -> wchar_t * -> char * -> ... it's really crazy;
You should use new struct MqlStr format in the DLL