I will code your EAs and Indicators for no charge
{quote} Try this version: Added: extern string UniqueID = "Breakout1"; // Unique identifier for this indicator instance --- Image: {image} --- Source code: //+------------------------------------------------------------------+ //| BreakOut_BOX.mq4 | //| hapalkos | //| 2007.02.10 | //+------------------------------------------------------------------+ #property copyright "hapalkos" #property link "" #property indicator_chart_window extern int NumberOfDays = 50; extern string periodBegin = "06:00"; extern string periodEnd = "08:00"; extern string...
any programmer can solve this indicator error current chart signal and back test signal not same indicator is attach below {file} {file}
/* -------------------------------------------------------------------- Change-log: Percentage-TS_1.10 Updated: [24-05-2025] By: MwlRCT -------------------------------------------------------------------- - Initialized PTrailing buffer to EMPTY_VALUE for consistency. - Corrected calculation range by removing arbitrary limit decrements. - Added bounds checking for safe buffer index access. --------------------------------------------------------------------*/
//+------------------------------------------------------------------+
//| Percentage-TS.mq4 |
//| Copyright 2014, MetaQuotes Software Corp. |
//| http://www.mql5.com |
//+------------------------------------------------------------------+
#property copyright "Copyright 2014, MetaQuotes Software Corp."
#property link "http://www.mql5.com"
#property version "1.00"
#property strict
#property indicator_chart_window
#property indicator_buffers 1
#property indicator_color1 Red
#property indicator_style1 STYLE_DOT
#property indicator_width1 2
extern double Percent = 1.0;
double PTrailing[];
//+------------------------------------------------------------------+
//| Custom indicator initialization function |
//+------------------------------------------------------------------+
int OnInit()
{
//--- indicator buffers mapping
IndicatorShortName("Percentage Trailing Stop("+DoubleToStr(Percent)+")");
IndicatorDigits(Digits);
SetIndexBuffer(0,PTrailing);
ArrayInitialize(PTrailing, EMPTY_VALUE);
SetIndexStyle(0,DRAW_LINE);
SetIndexLabel(0,"Percentage Trailing Stop");
//---
return(INIT_SUCCEEDED);
}
//+------------------------------------------------------------------+
//| Custom indicator iteration function |
//+------------------------------------------------------------------+
int OnCalculate(const int rates_total,
const int prev_calculated,
const datetime &time[],
const double &open[],
const double &high[],
const double &low[],
const double &close[],
const long &tick_volume[],
const long &volume[],
const int &spread[])
{
//---
int limit = rates_total - prev_calculated;
if(prev_calculated > 0) limit++;
/*
perc:=Input("Trailing Loss % :",0,100,14);
loss:=C*perc/100;
trail:=
If(C>PREV AND Ref(C,-1)>PREV,
Max(PREV,C-loss),
If(C<PREV AND Ref(C,-1)<PREV,
Min(PREV,C+loss),
If(C>PREV,C-loss,C+loss)));
Trail
*/
double loss;
if(limit >= rates_total) limit = rates_total - 1;
for(int i=limit; i >= 0; i--)
{
loss = Close[i] * Percent / 100;
if(i+1 < rates_total && PTrailing[i+1] == EMPTY_VALUE){
PTrailing[i+1] = Low[i+1];
}
if (Close[i] > PTrailing[i+1] && Close[i + 1] > PTrailing[i+1]){
PTrailing[i] = MathMax(PTrailing[i+1], Close[i] - loss);
} else {
if (Close[i] < PTrailing[i+1] && Close[i + 1] < PTrailing[i+1]){
PTrailing[i] = MathMin(PTrailing[i+1], Close[i] + loss);
} else {
if (Close[i] > PTrailing[i+1]){
PTrailing[i] = Close[i] - loss;
} else {
PTrailing[i] = Close[i] + loss;
}
}
}
}
//--- return value of prev_calculated for next call
return(rates_total);
}
//+------------------------------------------------------------------+ Dear BestTrader, you can add the thickness of the ZigZags to this indicator to change them. They are not changed manually. {file} {file}
{quote} To quickly accommodate a daily hour offset, the hour offset and chart time has to match, gold doesn't trade at all hours so the day, so start hour at 0 probably doesn't exist. It may be better to use this instead- OHLC_MTF_Lines - prices for standard price options - mtf - optional text and separator - shows 1 set of lines, but can load more with different tf/price settings {file} {image}
{quote} It's correct, that's how the charts work. Any tf candle is based on all prices from the start of the candle to the next. A h1 candle on a 1m tf will be from the first tick(open=close) on and after hh:00 and include all ticks (last tick is close) up to the next hh:00. {quote}
Draw what you think a h1 candle would look like on the 1m chart, open is the first opening tick, the close would be the last tick in the period.
Key points covered in the changelog: - MTF (Multi-TimeFrame) functionality -
{quote} Yes that's also correct, the open of the 1hr candle at hh:00 is the first tick of the 1min candle on or after hh:00. I'll repeat a previous point, on the 1min chart, what do you think 1hr candle would look like, where would the HLC prices be? The 1h close is the last tick from the 1min candle at hh:59.
{quote} Maybe I don't understand MTF indicators? This one shows the Close on 1-hour, so I thought the logic would be that it would show the Close on, 15M, 5M, 1M. So as you said, the close on 1M would be the last tick in the period, which is where the DOT would be if it is true MTF. {quote} Anyway, upon deeper thought, the dot on the Close of 1-Hour is only a function of the formula; if an EA was developed, it could never trade the Close price - the real signal is the Open of the next candle, that is where the DOT needs to be. What are the chances?...
``` /*-------------------------------------------------------------------- Change-log: 4_Bar_Indi_MOD_rev2_MWLRCT Updated:[2025-05-25] By: MwlRCT -------------------------------------------------------------------- - Implemented `GetMTFBar` for robust bar mapping. - Enhanced pattern detection using `iHighest`/`iLowest`. - Improved buffer initialization for all indicator buffers. - Added explicit error handling for `iBarShift` calls. - Removed TimeFrame > _Period constraint for downscaling. --------------------------------------------------------------------*/ ```
{quote} Yes that's also correct, the open of the 1hr candle at hh:00 is the first tick of the 1min candle on or after hh:00. I'll repeat a previous point, on the 1min chart, what do you think 1hr candle would look like, where would the HLC prices be? The 1h close is the last tick from the 1min candle at hh:59.
{quote} Maybe I don't understand MTF indicators? This one shows the Close on 1-hour, so I thought the logic would be that it would show the Close on, 15M, 5M, 1M. So as you said, the close on 1M would be the last tick in the period, which is where the DOT would be if it is true MTF. {quote} Anyway, upon deeper thought, the dot on the Close of 1-Hour is only a function of the formula; if an EA was developed, it could never trade the Close price - the real signal is the Open of the next candle, that is where the DOT needs to be. What are the chances?
MTF indicator displaying higher timeframe data on a lower timeframe should visually align the higher timeframe's Close price with the final tick of the corresponding lower timeframe period.
