MetaTrader 4 Build 529 beta released with new compiler - page 28

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
Code
void start() { double iv=iVolume(NULL,PERIOD_D1,0); Print("iv = ",iv," err = ", GetLastError()); }
always gives out
iv = 0.0 err = 0
Code
always gives out
iv = 0.0 err = 0
Why double? Can it be 2.5 ticks?
I have no idea what clever person came up with that instead of INT,
but that's the way it used to be. And now the compiler says that this function returns
DOUBLE type. But in fact it seems not to work at all :(
The 532 build reported runtime errors (e.g. array overruns), the 536 does not.
It will be harder to monitor.
Although in the old terminal everything worked and did not write anything
Why double? Can it be 2.5 ticks?
I updated the terminal... I wish I hadn't done that :)
Now
iVolume(NULL,PERIOD_D1,0)
outputs something like the following
iv = 1.360089743589744 err = 0
or
iv = 5.9 err = 0
I updated the terminal... I wish I hadn't done that :)
Now
iVolume(NULL,PERIOD_D1,0)
outputs something like the following
iv = 1.360089743589744 err = 0
or
iv = 5.9 err = 0
This is beta-testing, not ah-ha-sighing. You either help to get it to a normal working condition, or silently use the old 509 build and quietly wait for the release of the updated terminal. No one is forcing you into this thread if you don't want to accept the beta testing workflow.
I am helping.
Found the fault. Pointed out where and how it manifests.
How else can I help? I have no sources :)
The terminal is running in /Portable mode, ME is also running in /Portable mode. After compiling a new indicator, which was not previously present in the terminal navigator, the new indicator does not appear in the Custom Indicators list. Only after restarting the terminal, the new indicator appears in the Custom Indicators list of the navigator window.
Precisely the same way existing indicators are not updated after their modification in ME if the indicator is already working in the currency pair window. Only removing and restarting the indicator allows you to see the changes made in its code.
I am helping.
Found the fault. Pointed out where and how it manifests.
How else can I help? I have no sources :)
Who wrote this:
"...I updated the terminal... I wish I hadn't done that :)..."
Was it me?
Is this the help of a beta tester or is this the grumbling of a disgruntled user?