Coordinating MQL4 Expert Advisors, Scripts, and Indicators
Summary
This article describes a MetaTrader 4 application split across an Expert Advisor, a script, and an indicator. It assigns configuration to the Expert Advisor, continuously running analysis and trading work to a looping script, and controls and status messages to an indicator. The split is motivated by differences in how each program type runs and what it can do: EAs process ticks and expose settings, scripts can trade but run once by default, and indicators display information but cannot trade.
The proposed coordination method uses terminal global variables to publish component availability, share settings changes, and let each program check that the others are present. The article walks through a sample setup and describes observed responses to component loading, EA enablement changes, and parameter edits. It claims the script can react to user controls between ticks, while some alert behavior remains tick-based. This is an architectural example, not a complete trading strategy: the author says practical analytical and trading operations still need to be developed, and the design is specific to the older MQL4 environment.
Key ideas
- The design separates configuration, continuous work, and user-facing display across three MQL4 program types.
- Terminal global variables communicate component availability and settings changes.
- Each component checks whether the required parts of the application are running.
- A looping script is intended to process user controls without waiting for a new tick.
- The article presents a framework and example behavior, not a finished trading system.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.