Creating a Cairo-Inspired Graphics Library for MetaTrader 5 (Part 1): Why the terminal needs its own 2D-renderer

Why this article was written

MQL5 gives you chart objects and CCanvas, and both were designed for straight lines and filled rectangles. The moment a panel needs a rounded card, a ring, a translucent overlay or a gradient, you run into hard limits: square corners, jagged edges, no true alpha in object background colors, integer-only geometry, and a redraw that slows down as the object count grows.

You can reach for a DLL, but then the product will not pass Market validation and many traders will refuse to install it. Part 1 starts the other way round: stay completely inside the terminal, and build the missing renderer in MQL5 itself.

What is inside

The case for a new renderer. A concrete look at what CCanvas and chart objects cannot do, and why each limitation matters for real interfaces.

Cairo's model, briefly. Geometry (paths) is kept separate from paint (sources), and a per-pixel coverage mask resolves the two before compositing. That separation is what lets one routine draw every shape — and it is what the rest of the series builds on.

Color.mqh — the color type. A single ARGB value packed into a uint as 0xAARRGGBB, with the conversion and blending helpers every later part needs. Real transparency starts here.

Surface.mqh — the drawing target. A pixel buffer bound to one OBJ_BITMAP_LABEL. Every shape in the series is written into this buffer and delivered to the chart as a single object, so complexity costs you nothing in chart performance.

A first drawing. A triangle and a circle, painted pixel by pixel in nested loops. It works — and it deliberately shows the two problems that drive Parts 2 and 3: the edges are staircased, and every new shape needs its own function.

What you can do after reading it

Create a surface, put pixels on the chart with real alpha, and understand why the library is split the way it is.