Discussion of article "MQL as a Markup Tool for the Graphical Interface of MQL Programs (Part 3). Form Designer" - page 2
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
Hello,
first of all thanks a lot for your fantastic articles!
I'm trying to port the code back to MQL 4, as the Standard Control library exists there, too.
But I'm stuck at getting GroupTemplate.mqh to work with the following errors:
Should it be possible to port this to MQL 4, or is this functionality of calling methods on the template type only available in MQL 5?
Any help is greatly appreciated,
best regards
Holger
Hello,
first of all thanks a lot for your fantastic articles!
I'm trying to port the code back to MQL 4, as the Standard Control library exists there, too.
But I'm stuck at getting GroupTemplate.mqh to work with the following errors:
Should it be possible to port this to MQL 4, or is this functionality of calling methods on the template type only available in MQL 5?
Any help is greatly appreciated,
best regards
Holger
I'm afraid MQL5 is significantly updated in many aspects against MQL4, so these templates are not portable backwards without complete re-work.
I'm afraid MQL5 is significantly updated in many aspects against MQL4, so these templates are not portable backwards without complete re-work.
Ok, thanks for the clarification!
After some changes in one of the builds, apparently related to the MQL5 compiler optimiser, the program stopped working properly in the release version, although it works properly in the debug version.
I reported it on the forum, but there was no MQ response.
order of object creation was always taken into account: those created later were considered as if "on top" - they were given priority in the click processing.
Now it is broken in a bizarre way.
If the Expert Advisor is compiled without optimisation or under the debugger - everything works as it should (as before).
If compiled with optimisation - the wrong object (underlying) is allocated.