Finite differences provide a discrete approximation of derivatives and align naturally with price series sampled in bars and ticks. First and higher-order differences can be chained to characterize momentum and curvature without assuming continuity.

A binomial transform built from successive differences can be inverted after attenuating higher orders, producing a practical smoothing and noise-reduction pipeline with explicit control over how noise scales by order.

Differences also support pattern encoding by quantizing D differences into L levels, then mapping level indices into a pattern ID for statistics-based forecasts. Similar logic applies to OHLC candlestick structure using derived differences, extending to multi-candle sequences.

Forecasting options include naive models (SMA shift, average rate-of-change), higher-order extrapolation, adapti...

👉 Read | Calendar | @mql5dev

APB Channel EA implements a two-step entry for XAUUSD/XAGUSD using Heikin-Ashi reversal detection plus a Keltner-style EMA/ATR channel confirmation. Logic executes once per closed bar and starts with a Heikin-Ashi colour flip that arms a pending direction.

A trade is only permitted after a re-entry trigger: buy requires a close at/above the lower band, sell requires a close at/below the upper band. The pending signal expires after MaxBarsToTrigger bars unless set to 0.

Before order placement, time-window, tick-volume ratio, and ATR-based volatility filters must all pass. Position sizing targets constant monetary risk using entry-to-stop distance, with TP at RR_Ratio.

Stops are structural (recent swing high/low plus buffer), with optional break-even and an immediate exit on an opposite Heikin-Ashi arrow. Correct PointsPerPip configuration is critical for al...

👉 Read | AlgoBook | @mql5dev

Multivariate time series fail when models treat each series in isolation. Cross-asset dependencies are time-varying, often driven by macro events, and dense correlation graphs become unstable at scale.

Adaptive-weight GNNs learn the graph from data, but an N×N adjacency matrix is expensive and tends to include weak, misleading links. SAGDFN addresses this with graph diffusion and spatial sparsity.

The framework samples significant nodes via Significant Neighbors Sampling and refines edges using Sparse Spatial Multi-Head Attention with α-Entmax for sparse weights. This compresses adjacency to N×M, reducing complexity from N² to MN and lowering memory pressure.

Use cases include large-universe forecasting, portfolio rebalancing, and low-latency multi-instrument trading during volatile regimes.

👉 Read | Calendar | @mql5dev

This part moves the replay system from chart playback to full trade-flow simulation by modeling server behavior inside MT5.

A lightweight SQL database becomes the shared state for orders and positions, letting the EA, indicators, and helper components stay consistent in both live trading and replay mode. Instead of duplicating code, the existing C_Orders class is extended via database inheritance, creates a single-table schema, and routes requests to either the real server or a simulator based on the symbol.

The simulator replays server-side trade events by dispatching OnTradeTransaction in the correct order, enabling repeated market orders and later pending-order support. Initial coverage targets only the required actions (DEAL and SLTP), with SL/TP implemented as a direct DB update plus a synthesized transaction response.

👉 Read | Signals | @mql5dev

This article closes out core operator overloading in MQL5 by showing why [] rarely stands alone: indexed access typically requires a matching operator= to support both reads and writes.

It walks through common compiler errors, especially returning references to private members (breaking encapsulation) and assignments the compiler can’t resolve. The key is understanding how the compiler rewrites obj[i] into operator[] calls, often producing a temporary that changes assignment behavior.

Practical examples demonstrate single vs chained assignments, ambiguity when multiple operator= overloads exist (fixed with explicit casts), and applying [] to a doubly linked list to make list access feel array-like—while preserving correctness and maintainability for trading code.

👉 Read | CodeBase | @mql5dev

In MetaTrader 5 build 6230, we have significantly expanded the capabilities of AI Assistant for interacting with the platform. New tools have been added for working with Expert Advisors, scripts, and indicators, preparing parameters before testing, and retrieving Economic Calendar data.

The agent can now independently perform even more complex sequences of actions — from preparing a trading robot for testing to analyzing the market in the context of macroeconomic events.

For developers, MQL5 capabilities have also been expanded. Vectors and matrices now feature a new sorting method, while complex matrices and vectors support additional mathematical operations, including products and methods for solving systems of equations. A Print method has also been added for matrices.

In addition, a number of issues related to interface rendering, chart operation, and connections to trading accounts have been fixed in the desktop and web terminals.

Read more...

Bitmap-based CCanvas UIs in MQL5 suffer from startup overhead, blurred scaling, and theme duplication. This article replaces embedded .bmp resources with a procedural vector icon system that renders crisp at any size and recolors directly from the active palette.

The core is a small set of anti-aliased primitives (strokes, discs, rings, rounded rectangles, and polygons) using per-pixel coverage blending. Complex icons are then composed from these primitives using fractional positioning, keeping proportions consistent across header/sidebar sizes.

Logos and glyphs (MQL5 wordmark, layered orb, X, sun/moon, search, new chat, clear, history, toggle) are wired into existing render functions via icon IDs, removing all image-loading and resize code. Practical gains: simpler distribution, cleaner visuals, and reliable light/dark/hover rendering without extra assets.

👉 Read | AlgoBook | @mql5dev

An adaptive Fibonacci volatility band indicator for MT5 replaces fixed offsets with volatility-aware distances. It centers bands on a smoothed moving average of the chosen price and scales band width with a smoothed ATR, so levels expand in fast markets and contract in quiet ones.

Implementation focuses on clean MQL5 structure: multiple plot/buffer mappings for three upper/lower Fibonacci levels, a direction-colored middle line, and filled outer zones. Data handling uses an ATR(200) handle, CopyBuffer(), lookback limits, warm-up logic for SMMA initialization via an initial SMA, and incremental recalculation to stay efficient.

Result: dynamic volatility zones that help spot evolving support/resistance and provide a solid base for strategy rules and further indicator work.

👉 Read | AlgoBook | @mql5dev

StrategyTester5 targets a common MT5 Python workflow issue: live trading uses the MetaTrader5 package, while backtesting often requires a separate tester API and duplicated strategy logic.

The framework adds VirtualMetaTrader5, a shadow implementation that mirrors MT5 methods, constants, and properties, caching terminal/account/symbol state for simulation use.

A single mt5 variable swap switches environments, keeping one EA-style main() / on_tick callback for both live execution and historical replay.

Backtests run via run_backtesting(), which handles data prep, modeling modes (ticks/open/1m OHLC), optional Flask-SocketIO dashboard, and a lighter optimization mode.

Results return as a TesterStats object with MT5-style metrics. Historical inputs can come from parquet via HistoryManager or optionally from the terminal to reduce file I/O overhead.

👉 Read | Signals | @mql5dev

This part advances an automated MT5 optimization pipeline that stores sequential Strategy Tester jobs in an SQLite database, turning manual multi-currency EA research into repeatable projects. The “project creation” EA behaves like a script: it generates stage-specific tasks, writes them to the DB, then exits.

Focus shifts to stage 2: combining top stage-1 passes into strategy groups and re-optimizing them with a chosen criterion (often a custom normalized annual profit) and an optional time cap to cut wasted tester runtime.

Key controls include filters on minimum custom metric, trade count, and Sharpe ratio, plus group size (2–16). The article also shows why iterative dry runs matter: a detected bug and missing symbol history can mark tasks “done” while preventing the pipeline from producing the final EA, so DB inspection becomes part of debugging.

👉 Read | Signals | @mql5dev

This stage makes the replay/simulation framework usable without rewriting the Expert Advisor or position indicator. A small addition to C_InServer enables correct handling of symbols used on hedging accounts, keeping server vs simulator execution transparent.

The focus shifts to C_Orders, where trade requests are decoded. Error handling is refactored so messages look consistent across real and simulated servers, with symbol-tagged output to trace request origin.

TRADE_ACTION_DEAL is implemented incrementally, since it must behave differently on netting vs hedging: update an existing position (including average price logic) or create a new one. The simulator also introduces an optional server-response delay hook, and fixes ticket generation to prevent duplicates.

Result: market opens and SL/TP edits can be tested end-to-end in replay; full closing ...

👉 Read | NeuroBook | @mql5dev

This article proposes a reusable MQL5 Expert Advisor template that separates strategy rules from platform plumbing. Instead of mixing signals, execution, and risk logic inside OnTick, the framework standardizes recurring tasks: history loading, new-bar detection, order management, spread checks, commission/swap handling, and UI updates.

Core architecture: a Virtual Chart (cached OHLC/time), a Robot class (state + trading operations), and a single Simulated() loop. Live trading uses a 1-second timer for stability with sparse ticks; the Strategy Tester runs on ticks, but both share the same entry point.

Trading logic plugs into one method that sets two variables: entry direction and close direction. Built-in modules cover auto lot sizing, risk controls, additional entries, martingale, and timed “waiting out losses,” with inputs grouped for safer testing and o...

👉 Read | Signals | @mql5dev

Average True Range (ATR) is derived from True Range (TR), defined as max(High-Low, abs(High-Close[1]), abs(Low-Close[1])). Initialization typically computes TR over Length bars, then uses the SMA of those values as the first ATR.

RMA uses alpha=1/Length and updates as: rma = alpha*TR + (1-alpha)*prev_rma. SMA mode recalculates the simple average of TR over the last Length bars on each candle. EMA uses alpha=2/(1+Length) with: ema = alpha*TR + (1-alpha)*prev_ema. WMA applies linear weights: sum = N*TR[0] + (N-1)*TR[1] + … + 1*TR[N-1], then wma = sum / (N*(N+1)/2).

Common validation setup: XAUUSD on H1, comparing RMA, EMA, SMA, and WMA outputs side by side.

👉 Read | Docs | @mql5dev

The article shows how MQL5 operator overloading can be used to express data-structure operations with stream-style syntax similar to C++ input/output, improving readability when done with clear intent.

A pointer-based queue is rebuilt using overloaded operators, where a small header-only change switches behavior between LIFO (stack) and FIFO without rewriting the calling code. This demonstrates separating policy (order) from usage.

The same idea is extended to a linked list: adding a subscript operator enables array-like access, then the implementation is revised so assignments append new nodes instead of overwriting existing values. The final design uses a doubly linked list and avoids traversal by maintaining links during insertion, making updates predictable for trading utilities like event queues and order pipelines.

👉 Read | Quotes | @mql5dev

This update finalizes the MT5 replay/simulation system for training by aligning simulated pricing with live-server behavior. A small fix removes hardcoded SYMBOL_DIGITS side effects, and a new config option lets users set per-symbol decimal precision so the position indicator formats prices correctly (e.g., instruments with 0.5 ticks).

Database stability is improved by moving table-creation SQL into an external script embedded as a resource and adding constraints to prevent invalid or duplicate records, reducing corruption risks without extra application logic.

Take Profit and Stop Loss become functional by adding a close-price check inside the position indicator and firing a custom event to the EA to close positions. The same event-driven pattern can be adapted to simulate pending orders by changing the trigger conditions and emitting the appropri...

👉 Read | Freelance | @mql5dev

PDF generation in MQL5 can work without DLLs when the format is treated as plain text plus a bottom index.

A minimal PDF has five regions: header, numbered objects, xref table, trailer, and %%EOF. Only the object list grows; most of the file is boilerplate.

The body is a flat set of indirect objects referenced by “N 0 R”. Pages do not embed content or fonts directly; they reference a content stream and resource objects.

PDF values are limited to eight types, with names (/Helvetica) distinct from strings ((Hello)). Streams require an exact /Length byte count.

A single page typically needs Catalog, Page Tree, Page, Contents stream, and Font. Correct xref byte offsets and startxref are critical; a one-byte shift breaks the file.

Content streams use postfix operators (BT, Tf, Td, Tj, ET). Multi-line layouts rely on relative Td moves and can switch fonts mid-s...

👉 Read | Docs | @mql5dev