IsTradeContextBusy() => Error-Number? - page 2
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
Thank you but are they still valid?
These err-numbers are now used differently:
e.g. 135 (formally: ERR_PRICE_CHANGED) is now
which I guess - could happen not only at compile-time!!
Gooly
PS: See all these needless End-Of-Lines :(
You are mixing compilation errors with trade server errors. Read carefully the documentation.
Trade server errors didn't change, only the documentation changed as noted by RaptorUK (in the link given to you by qjol).