Errors, bugs, questions - page 1172
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
There are errors in the standard library for MQL4, specifically in indicator classes.
For the CiATR class the body of the GetData method is missing.
For indicators that use parameters of the ENUM_APPLIED_VOLUME type(CiForce, CiOBV) there is an error: improper enumerator cannot be used
By the way, ENUM_APPLIED_VOLUME seems to be a standard enumeration; it is present in MQL4 documentation, but in fact it is absent ('ENUM_APPLIED_VOLUME' - undeclared identifier).
So, please check all your libraries. I have a feeling they were hastily ported from MT5 without even checking their functionality.
Compile error, build 966
build 932 is finedepends on the content of the comment
it's fine
Comments are never substituted - the compiler simply ignores them, otherwise #define in most cases could not be used with comments at all //
In any case, replace // with /**/ in https://www.mql5.com/ru/forum/1111/page1190#comment_993854The result is the same - compilation error.
Please explain the following situation. I have a multi-currency indicator, the values of which do not change depending on what chart it is attached to - it calculates the values for the specified instruments and is not related to the current window. I manually draw support and resistance lines on this indicator. Now the trick: if I drag another tool from the market overview into the window, the appearance of the indicator remains the same and lines disappear. If you open the Object List dialog box, those objects are still listed there. The endpoints values (dates and values) remain the same (i.e. they should be visible in the same places) - it's understandable, they have not been changed. However, the lines are not visible. If you then drag the former tool that was originally there onto the window, the lines become visible again. What is the problem?
Found and corrected.
Thanks for contacting me. Turns out to be a generic bug - it's always worked that way before
You cannot apply the abbreviated operator !() - compilation error
If the compiler understands (and it does) that f4( a ) means 'a' is an object and not a pointer/scriptor as a number)
it should also understand that !a' means the same thing for 'a' (object, not pointer/numeric)
in other words, if
a1.f() and a2.f() mean the same thing, whether a1, a2 is a pointer or an object, how is operator !() any worse?I should add that, for example, there is no compilation error with operator+(), nor is there one if we simply add operator+(), which is not used at all, to the first example above
but in this case another uncertainty occurs