Also, the following chart events would be very helpful...
CHARTEVENT_OBJECT_CREATE
CHARTEVENT_OBJECT_DELETE
Also, the following chart events would be very helpful...
CHARTEVENT_OBJECT_CREATE
CHARTEVENT_OBJECT_DELETE
Hi
I daily communicate with 60-80 traders via email and live trading room.
I think Meta trader 5 is a good effort as they added object oriented programming.
However; the company clearly missed the basic requirement of most traders
who actively use MT4 platform on a daily basis.How customers are going to use it in trading?
Specially, when almost all of the Meta Trader 4 custom indicators and E.As
are not going to work in this Meta trader 5 version.
A 'Pause' button on the Strategy Tester and Optimizer would be an excellent addition in MT5 so that one wouldn’t lose previous calculations and start all over again from the beginning again if there was the need to pause it for some reason like the computer ( hopefully temporarily) stalled due to overload etc.
An extremely useful feature in MT5 would be a Take Profit target that closes out only HALF (or whatever its set to) of the overall trade.
Closing 1/2 of a position at 1:1 reward is an extremely common approach amongst serious traders and this feature would be very handy.
Fix OnTrade() to indicate which order/position has changed status instead of forcing the programmer to iterate over all orders to find out, using the same sort of time wasting procedure that was necessary in MQL4.
No response was forthcoming when this question was asked over on the MQL4 forum. Maybe someone from MetaQuotes will comment here eventually, now MQL5 has a dedicated forum of its very own?
Jim
Fix OnTrade() to indicate which order/position has changed status instead of forcing the programmer to iterate over all orders to find out, using the same sort of time wasting procedure that was necessary in MQL4.
May be in future
Fix OnTrade() to indicate which order/position has changed status instead of forcing the programmer to iterate over all orders to find out, using the same sort of time wasting procedure that was necessary in MQL4.
No response was forthcoming when this question was asked over on the MQL4 forum. Maybe someone from MetaQuotes will comment here eventually, now MQL5 has a dedicated forum of its very own?
Jim
I second this, in addition to the events I already mentioned. It would be nice also if the OnTrade() could distinguish between pending orders and successful fills. An order modification event would also be nice.
MQL5 seems to have an events based system for the sole purpose of having buttons and input boxed, ignoring anything else that could benefit from it--especially in terms of efficiency.
These are the things that make EAs inefficient and a pain to code: looping through orders, looping through history, and looping through objects. It is so frustrating that MQL5 has an events based system, yet I'm still needing to do all of these things that slow down my EAs and make coding so painful.
13
Some things I thought of while trying out the beta. Thanks for your consideration.
- Show crosshair when placing objects to allow precise placement.
- Ability to make certain objects (including indicators) unselectable. This prevents selecting, deleting, or moving the wrong objects when there are a lot of objects (some overlapping) on the screen. It would also be nice if my EA could prevent certain objects that it uses from being selected/changed.
Things I liked about MQL4 that has changed in MQL5 Beta:
- Ability to label line objects with the "Descriptions" field
- Trendlines that stick to the bars
- Object placement cancels and mouse returns back to cursor when right click in the terminal