Codes
Trendline zigzag in qualitative channel for MetaTrader 5
A dynamic trendline-based evolution of the Donchian Channel
Multi-Day Dynamic VWAP for MetaTrader 5
Dynamic VWAP level which can be averaged over multiple days
Volume MA with candle color tracking for MetaTrader 5
A moving average of pure tick volume with histogram bars tracking bullish/bearish candle color
PSAR Zigzag (Non lagging) for MetaTrader 5
A zigzag based on the trend change of the parabolic sar
Ranging Market Detector for MetaTrader 5
An indicator which attempts to highlight a ranging market area
Trend Zigzag (on ma cross) for MetaTrader 5
A static zigzag which connects the intersections of a moving average crossover
Autoscaling Zigzag for MetaTrader 5
A zigzag indicator that uses a single input to adjust the step size for detecting wave direction changes
Intrabar Volume Flow for MetaTrader 5
An indicator which visualizes how volume changes over time within each bar. It shows tick volume in a rolling histogram format
Portable Moving Average for MetaTrader 5
Calculate a moving average in one function call. Code that can easily be transported between different projects
Zigzag fibo oscillator for MetaTrader 5
An advancement of the MetaQuotes zigzag with an oscillator mode, current bar leg tracking, fib levels, and dynamic scaling
Forum
Fake Pivots and false experts (retrospective algorithms)
Through experimentation one night, I figured out it was very easy to calculate the truest pivots in the market with minimal code by calculating the candles moving backwards in time rather than forwards. Moving backwards in time isn't reality, and of course we always move forwards in live trading
Indicators: Ranging Market Detector
Ranging Market Detector : An indicator which attempts to highlight a ranging market area Author: Conor Mcnamara
Is it not possible to have direct control of the entry price when automating buy or sell trades?
I wanted to see if it was possible to make the EA enter a buy position only when the ask price is less than or equal to the moving average price. NormalizeDouble (currentAsk, _Digits ) <= NormalizeDouble (ma[ 0 ], _Digits ) Full snippet: if (allow_buy && trade_type == market_orders &&
Indicators: Trend Zigzag (on ma cross)
Trend Zigzag (on ma cross) : A static zigzag which connects the intersections of a moving average crossover Author: Conor Mcnamara
I'm very close to abandoning a practice conversion
I set out to do a practice conversion to convert a more tedious MQL4 indicator to MQL5. This wasn't for anything other than practice, and because I'm focusing on MT5 now. I thought, maybe I can do it in 30 minutes... but no, this wasn't the case at all. I have tried numerous times to convert it
Experiencing an issue with objects when two separate window indicators are on the same chart
I wanted to create a text object to measure the "power" on the last histogram bar for the bears power and bulls power indicators. It seems that there are no issues with the placement of the text object if I load one single indicator on the chart (either bulls or bears). Chart with only bears
Is it possible to emulate one EA inside another EA script?
Let's say you like the performance of an EA over a certain period, but you are unwilling to use it because of the fact that it lacks any risk management features. In this case you could code another EA which applies the desired risk management and have both running on separate charts. But you are
Explain the post attachment rule
Why must attachments on posts only be .mq5? For example, if I didn't want to post code, I could just attach it as a text file which is handier for the recipient. But apparently there is a problem with that
Mqltick struct not providing volume information
I want to know why the volume fields of the mqltick struct are always giving 0.0, both "volume_real" and "volume" are not giving any data. The "tick_volumes" buffer is plotting fine in this small example I made, but not volume from Mqltick struct. #property indicator_separate_window #property
Do you use and support indicators from the codebase?
It's clear that there are a lot of interesting, experimental, and useful indicators on the MQL codebase. Do *you* like to collect and support these programs? In my opinion, we don't have time to code everything, and we don't always have the same ideas, so it's good to support other people's codes