Discussion of article "Library for easy and quick development of MetaTrader programs (part IV): Trading events" - page 3
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
It's like a very interesting lecture in terms of content. I will definitely follow the whole series.
Unfortunately, there may even be small mistakes on purpose - the content is very complex and perhaps you should stay on the ball.
In the "
" the field total_market is not found - this already happened before with ORDER_STATUS_MARKET. The changeover from simple to complex is very impressive.
At the refresh point, I couldn't go any further, as the next object didn't want to run straight away either. So I was happy to use the download.
mfG
Marc Tolkmitt
Strange, I can't realise the simplest logic with your methods...
Here I need to get the closing time of the last trade. It seems that the library has a mechanism for working with abstract orders a la MT4, but I don't see any methods for working with them.
I request Deals, but ORDER_PROP_TIME_CLOSE is not supported:
I request Deals, but ORDER_PROP_TIME_CLOSE is not supported:
ok, it is somehow incorrect to request the closing time for a trade. But it doesn't work with GetListHistoryOrders() either...
I request Deals, but ORDER_PROP_TIME_CLOSE is not supported:
In the test Expert Advisor, in the button press handler.
(and this is just an example of how to handle events and get data).
There are code blocks there that are responsible for closing positions. You can see how it is implemented there. For example, a code block for closing a purchase by the current symbol with maximum profit:
About closed positions - I did it a long time ago, now I can't tell you how to get what you need at a glance. I'll take a look later and write - I'm very busy at the moment.
In the test Expert Advisor, in the button press handler
(and this is just an example of how to process events and get data).
There are code blocks there that are responsible for closing positions. You can see how it is implemented there. For example, a code block for closing a purchase on the current symbol with maximum profit:
About closed positions - I did it a long time ago, now I can't tell you how to get what you need at a glance. I'll take a look later and write - I'm very busy at the moment.
Thanks, but there is no need to catch the event.
ORDER_STATUS_MARKET_ORDER gives error : undeclared identifier. looks like things changed in recent versions for MQL 5, it shows up both in COrder::OrderMagicNumber and CMarketOrder Constructor!
I downloaded the MQL5.zip archive file attached to the article - each file individually and all together (when compiling Engine.mqh or TestDoEasyPart04.mq5) are compiled without errors.
What exactly are you doing that you are getting a compilation error?
I downloaded the MQL5.zip archive file attached to the article - each file individually and all together (when compiling Engine.mqh or TestDoEasyPart04.mq5) are compiled without errors.
What exactly are you doing that you are getting a compilation error?
Figured it out, there was one entry missing from the define enum. somehow It was missing (although I copy paste the code from the tutorial into the editor)
The codes in the article do not always match the codes in the attached files. Sometimes I may miss something during the description, and sometimes something is added after writing the article. The article is not a step-by-step guide in the “read-copy-use” style, but only a detailed explanation in the form of training material. And small errors and omissions make you think, and that’s good)