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 an issue with debugger in MT4 builds 614 & 616. Editor builds 900 & 904. Debugger loads the indicator to a chart but there is no output in the debugger windows, add watch is greyed out. Breakpoint appears to work but only to pause the debugger at that point. No output in the debugger. I tested that on my own code and included alligator code.
Also less of an issue but profiler only works some of the time, it works on included indicators but not on my own code that compiled with no errors. It loads my indicator to a new chart then immediately unloads it and closes the chart, but no errors reported in the log.
Can anyone confirm the debugger issue ? I really need that debugger it was working on an earlier build when I tested it a couple of weeks ago.
Tested with build 616. Debugger is working with a custom indicator. However the profiler isn't working with the same indicator, it immediately stops. (but the profiler is working well with an EA).
So I made some more tests, with an other indicator and this one is working (profiler). The main difference between the two is that the first used an other indicator (iBands), if I comment the lines with iBands the profiler is now working. Debugger is working well with the second indicator also.
1. Is there any way to manually make MT4 check for an update?
2. Wish List item: MQL: a real volume pre-defined variable like Volume[], something like RealVolume[].
3. 2 words, Renko charts. Other platforms have this capability built in. ie., Ninja trader.
Tested with build 616. Debugger is working with a custom indicator. However the profiler isn't working with the same indicator, it immediately stops. (but the profiler is working well with an EA).
So I made some more tests, with an other indicator and this one is working (profiler). The main difference between the two is that the first used an other indicator (iBands), if I comment the lines with iBands the profiler is now working. Debugger is working well with the second indicator also.
I tested debugger in 616 (ME 904) on ATR, Bands and Alligator and on my own custome indicator, debugger runs but add watch is greyed out on all of them so I can't do anything with debugger. Which custom indicator did you use ?
Ahhh ok yes I get it now, I did place a breakpoint while debugger was running so I thought I should be able to add a watch at the same time, I just tried it again and waited for the next tick so it would stop at the breakpoint and this time it lets me add a watch, it seems to be working thanks angevoyageur.
another small problem, already exist in 509 and 610:
if a EA using a long period MA like MA(1000)
and history (or chart?) has not this much records for related period, then EA do not work. it could try to refresh bars, instead of not to start working.
or a message to user required: refresh your chart's bar data..
If you turn UAC off MT4 will create the data folder in the installation directory. I dont know why your compiler is recompiling everything though, mine isn't doing that. Did it do that when you had UAC on ? Maybe someone else can tell you more about it.