Errors, bugs, questions - page 1513
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
Which is better, from a performance point of view, like this:
or by overloading methods?
Which is better, from a performance point of view, like this:
or by overloading methods?
you won't see a difference in terms of performance - both solutions have a place :)
Thank you! Another question:
What is the point of const fields in a structure? Such structures can't even be passed (compiler swears or stack overflows)?
Overloading the assignment operator for structures is actually impossible (it would make sense because of the infinite recursion). So why const fields in a structure then?
On Windows 10 x64 never encountered this error on 1241 build. After the "Unfold" command, the graphics window unfolds completely, without any holes:
You probably have some settings changed inside your operating system (maybe you're into trimming your operating system's defaults or cleaning the registry or the like...).
When dragging the glass with the mouse, press either "Shift" or "Ctrl" or "Alt" at this point.
My best advice is to write to serviceDesk with detailed description, with own code (which shows ticks), with screenshots.
>> Probably you have changed some settings inside of your operating system (maybe you are keen on cutting standard features of your operating system, or registry cleaning, etc...).
I'm not into that kind of stuff, systems are clean
>> Here I can advise you with detailed description, with your code (which shows tics), with screenshots to make an application to ServiceDesk.
and where is this? i thought this branch is the serwer
If I use #include to include an mqh-file that contains something similar into the indicator:
there are no errors at the stage of compilation of the indicator itself. But it occurs with mqh separately (see above).
How can I find the value of this property indicator in MT4, so the compiler won't complain more than once in plugged mqh?
I'm trying to ensure the application operating in MQL5 and MQL4 identically.
I suspect that when introducing sinput variables in MQL4, they forgot to add functionsParameterSetRange() andParameterGetRange() to the language.
They appear in MQL4 documentation asParameterSetRange() andParameterGetInput()-https://docs.mql4.com/basis/variables/inputvariables#sinput
but the compiler won't accept them.
Unfortunately, without these functions all the fun of sinput variables is lost.
Thank you! Another question:
What is the point of const fields in a structure? Such structures can't even be passed (compiler swears or stack overflows)?
Overloading the assignment operator for structures is virtually impossible (would make sense because of infinite recursion). So why const fields in a structure then?
Enjoy:
Enjoy:
Moved the MT4 terminal folder to another drive. Previously I ran it with the portable key. I did the same thing this time.
The terminal connected to the server at once. In the past when I moved a terminal folder the passwords were not saved - I had to re-enter them. Now (build 950) it doesn't happen.
Is this normal (and only for me)?
What better way, from a performance point of view, is this: