instead of
datetime d=D'2014.03.07 20.00';
try
datetime d=D'2014.03.07 20:00';
This thread is two days old. Is MQ picking these items up for consideration?
This thread is two days old. Is MQ picking these items up for consideration?
Hi TheEconomist, Any update on the BCLib at http://forum.vamist.ro/blog/2-theeconomists-forex-arbitrage-blog/ ?
I'll be thinking about it. It needs an entire rebuild to this new MQL4... Hmm, nice to see people interested in that.
Since 5 was my bug, this is the new list (new 5)
1) Attempting to hide a focused editbox (standard library) will not work. Furthermore, the object will be visible even if the dialog window in which is located is minimized.
2) Pretty often, double clicking a label will put it in a selected status. It can be moved by mouse (though it jumps back to original position). Also, properties can be modified with right click (but are not taken into consideration).
3) Hidden buttons seem to receive events.
4) Programatically changing a combobox value will trigger its ON CHANGE event
5) Minimizing and restoring window (CControlsDialog) exposes hidden objects.
Where is the ServiceDesk link for MT4 ? Should it be on my profile ?

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
1) Attempting to hide a focused editbox (standard library) will not work. Furthermore, the object will be visible even if the dialog window in which is located is minimized.
2) Pretty often, double clicking a label will put it in a selected status. It can be moved by mouse (though it jumps back to original position). Also, properties can be modified with right click (but are not taken into consideration).
3) Hidden buttons seem to receive events.
4) Programatically changing a combobox value will trigger its ON CHANGE event
5) Date compilation (the one with D') seems to have strange effects.
Today is sunday, march 9, and last H4 bar on USDJPY is 2014.03.07 20:00.
Writing
returns 5 for both true and false versions, even though iBarShift of 5 is 2014.03.07 00:00.
However, calling
will return 0, correctly, therefore it's a bug with datetime compilation.