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
I have been working with MT5 for a couple of days now and noticed that stops and profits can now be edited with the mouse, which is good, but there is a small bug in it. When I move the mouse to the stop, its pointer changes to show that the stop is active for editing, but the pointer also changes when using "Crosshair" tool, which means that if I want to measure distance from the stop, it is not very convenient, because the second point is behind the pointer and I can not see where I am taking it to. I wanted to do PrintScreen, but it does not take a picture of the mouse.
The bottom line: it is not convenient to measure with "Crosshair" from the stop.
The error is fixed.
The switch-check "fetch" was discussed and we cannot implement correct/correct control.
The value of the switch expression may be anything, for instance:
OK, I see. The compiler cannot control the switch expression's value instead of the programmer.
As a side question, this construct is used in the above example:
Does it mean that it is acceptable to handle data of an enumerated type not only with named constants (v1, v2, etc.) but also by specifying their ordinal number in the enumeration ( EV(n) )?
...I made such constructions to solve such a question - but here it can be much simpler.
Does this mean that it is acceptable to refer to data of an enumerated type not only with named constants (v1, v2, etc.) but also by specifying their ordinal number in an enumeration ( EV(n) )?
In this case, just the standard int type conversion to EV is applied. In functional notation.
There are two possible syntactic forms of type conversion in mql5 that are equivalent in result: (Type_name) Value and Type_name(Value).
I mean, it's not some special feature related to enumerations, it's just a normal type conversion.
I have been working with MT5 for a couple of days now and noticed that stops and profits can now be edited with the mouse, which is good, but there is a small bug in it. When I move the mouse to the stop, its pointer changes to show that the stop is active for editing, but the pointer also changes when using "Crosshair" tool, which means that if I want to measure distance from the stop, it is not very convenient, because the second point is behind the pointer and I can not see where I am taking it to. I wanted to do PrintScreen, but it does not take a picture of the mouse.
Bottom line: it is not convenient to measure with "Crosshair" from the stop.
I agree, it is a good observation, but it is not a bug.
Good wishes for MT5
In this case, just a standard int to EV conversion has been applied. In functional notation.
There are two possible syntactic forms of type conversion in mql5, which are equal in result: (Type_name) Value and Type_name(Value).
I mean, it's not some special feature related to enumerations, it's just a normal type conversion.
Cannot start the test in visualisation mode. The visualiser itself starts, but the test does not start. This is what it says in the log:
2011.06.16 21:25:47 EURUSD: symbol synchronized, 2904 bytes of symbol info received
2011.06.16 21:25:47 symbol EURUSD synchronization error
2011.06.16 21:25:47 cannot get history EURUSD,M1
2011.06.06.16 21:25:47 log file "C:\Program Files\MetaTrader 5\Tester\Agent-127.0.0.1-3000\logs\20110616.log" written
2011.06.16 21:25:48 tester agent shutdown
Developers.
Is the visual tester really that slow or am I just imagining things?
Cannot start the test in visualisation mode. The visualiser itself starts, but the test does not start. This is what is written in the log:
2011.06.16 21:25:47 EURUSD: symbol synchronized, 2904 bytes of symbol info received
2011.06.16 21:25:47 EURUSD symbol synchronization error
2011.06.16 21:25:47 cannot get history EURUSD,M1
2011.06.16 21:25:47 log file "C:{Program Files\MetaTrader 5\Tester\Agent-127.0.0.1-3000\logs\20110616.log" written
2011.06.16 21:25:48 tester agent shutdown
The same problem. Agent log can't be opened via specified path.
Please give me the code.
Good night, I was wondering if in this code
after checking B>spred, which is "FALSE", the rest of the values are checked
It increases the test running time, so I have to modify the code in the following way
And the most time consuming in terms of calculations ( proverka() - copying of buffer values of an indicator)
I put it last but it does not check the last one. I wonder.
And why so ???
Or it does not check the last one: