Good day coders and traders, please i need help to make this EA open trade with 0.01 lotsize, i am not comfortable with the current lotsize
Attached File(s)
I will code your pivot EAs for no charge 28 replies
I will code your scalping EAs for no charge 163 replies
Oanda MT4 - Indicators and EAs not showing 2 replies
EAs and indicators relating to moutaki... 22 replies
InterbankFX has loaded its MT4 platform with custom EAs, indicators and scripts 1 reply
Disliked{quote} {quote} - when copy n pasting n modding, check what you've just done (this is a common issue for me too), address the #property lines under where b_close is declared - when you double click on a compilation error, it will take you to where the error is, may not be exactly where the issue is, but close enough - highlight and press f1 for "Close" to see how to properly use it {quote} - up to you, as mentioned before, a tick change in bid could be 0.90045 to 0.90047, +0.00002, you can plot 0.00002, or divid by the minimum tick increment _Point,...Ignored
Dislikedcan you build an ea based on indicator colour buffer. I mean when red buffer open sell position and when blue buffer open buy position. I have attached indicator. pls help. {file}Ignored
DislikedGood day coders and traders, please i need help to make this EA open trade with 0.01 lotsize, i am not comfortable with the current lotsize {file}Ignored
DislikedCan someone please help me to update this indicator to only show the Gaps that are not closed yet. I tried my my limited knowledge to loop through candles on right of the gap to see if lows of candles on the right (in case of gap up - blue lines ) or highs of candles on the right (in case of gap down - orange lines ) cross the lines created. If later (recent candles) do cross the lines then lines should not show. thanks. {file}Ignored
Disliked{quote} Kindly assist i need a single arrow alert pointer for the attached breakout box the strat is based on 4hrs , box drawn based on the first high and low of the beginning of each week, with 20 buffer up or down, 4hrcandle that breaks and closed above or below is the signal candle, i need arrow signal that should confirm the break,i know youve done stuff like that in one of your postings here, please see the attached screenshot,normally the breakout make take a day or two or more before the break comes , but once it does it makes profit with...Ignored
Disliked{quote} Alright...so....turns out this EA is not the best lol! Here are the results and I even changed the take profit to make it 1:2 and even 1:3 ratio (along with the 1:1 I originally put in for the parameters) and the following are the graphs of each. Also I tested from 01.01.2015 through 06.29.2022 and the period I used was H1 and the currency pairs were GBP/JPY, EUR/JPY, EUR/USD and So I feel bad that you had to make this for it not to work but also really appretiate it!I am going to play around with it a bit and modify it some and...
Ignored
Disliked{quote} Here is a version using the candle close. As far as your "Rules" go this EA follows exactly what you requested. Your request: The idea is to place a horizontal line on the chart and when the price closes above, it will open a buy, and if it goes back and closes below the horizontal line, the previous order will be closed and a sell order will be opened. This will happen until the price moves in one direction or the other. My entries are usually on the 1min, with trade decisions based on the 1hr and 4 hr. NOTE : You cannot change the name...Ignored
Disliked{quote} dear CJA , there is a error in your EA. it automatically opens and close the trades fastly without wait to close candle.its opens sell trade and close it and then open buys and immediately close it and again opens sell trades. some time it will works very well but some times it will just open and close trades without wait of candle close. plz correct the error and allow ea to open next trade after candle close. GOD BLESS YOU MY FRIEND. YOU ARE DOING GREAT WORK FOR THE FOREX COMMUNITY. {image}Ignored
Disliked{quote} {quote} - when copy n pasting n modding, check what you've just done (this is a common issue for me too), address the #property lines under where b_close is declared - when you double click on a compilation error, it will take you to where the error is, may not be exactly where the issue is, but close enough - highlight and press f1 for "Close" to see how to properly use it {quote}Ignored
#property copyright "Copyright :copyright: June 2022, jeanlouie"
#property link /*"www.mql5.com/en/users/jeanlouie_ff"*/"https://www.forexfactory.com/jeanlouie"
#property description "www.forexfactory.com/jeanlouie"
#property description "www.mql5.com/en/users/jeanlouie_ff"
//#property version "1.00"
//+------------------------------------------------------------------+
//| |
//+------------------------------------------------------------------+
input int tick_count = 1000; //Show last x ticks
//+------------------------------------------------------------------+
//| |
//+------------------------------------------------------------------+
#property strict
#property indicator_separate_window
#property indicator_buffers 3
double b_bid[];
#property indicator_type1 DRAW_LINE
#property indicator_color1 clrPurple
#property indicator_width1 1
#property indicator_style1 STYLE_SOLID
double b_ask[];
#property indicator_type2 DRAW_LINE
#property indicator_color2 clrBlueViolet
#property indicator_width2 1
#property indicator_style2 STYLE_SOLID
double b_close[];
#property indicator_type3 DRAW_LINE
#property indicator_color3 clrWhite
#property indicator_width3 1
#property indicator_style3 STYLE_SOLID
#property indicator_levelcolor clrSilver
#property indicator_levelwidth 1
#property indicator_levelstyle STYLE_DOT
#property indicator_level1 0
//+------------------------------------------------------------------+
//| Custom indicator initialization function |
//+------------------------------------------------------------------+
//place to store stuff
double arr_bid[];
double arr_ask[];
double arr_close[];
int OnInit()
{
//set draw buffers
SetIndexBuffer(0,b_bid);
SetIndexEmptyValue(0,EMPTY_VALUE);
SetIndexBuffer(1,b_ask);
SetIndexEmptyValue(1,EMPTY_VALUE);
SetIndexBuffer(2,b_close);
SetIndexEmptyValue(2,EMPTY_VALUE);
//size the dynamic arrays to tickcount
ArrayResize(arr_bid,tick_count);
ArrayResize(arr_ask,tick_count);
ArrayResize(arr_close,tick_count);
//start them off with 0's
ArrayInitialize(arr_bid,0);
ArrayInitialize(arr_ask,0);
ArrayInitialize(arr_close,0);
IndicatorDigits(_Digits);
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[])
{
if(prev_calculated<0)return(-1);
if(IsStopped())return(-1);
//save the last ask/bid prices
static double prev_ask;
static double prev_bid;
static double prev_close;
//get the current ask/bid change from the previous
int delta_ask = int((Ask-prev_ask)/_Point);
int delta_bid = int((Bid-prev_bid)/_Point);
int delta_close = int((Close[i]-prev_close)/_Point);
//if the previous ask/bid is non existent
if(prev_ask ==0) delta_ask = 0;
if(prev_bid ==0) delta_bid = 0;
if(prev_close ==0) delta_close =0;
//set values of prev ask/bid for next call
prev_ask = Ask;
prev_bid = Bid;
prev_close = Close[i];
//update display
display_update(delta_ask, delta_bid, delta_close);
return(rates_total);
}
//+------------------------------------------------------------------+
//+------------------------------------------------------------------+
//| |
//+------------------------------------------------------------------+
bool display_update(int d_ask, int d_bid, int d_close)
{
//move array elements back 1 position, stop at index 1
//i50=i49 ... i1=i0
//array is array indexing, but treated as timeseries by filling new from index 0
for(int i=tick_count-1; i>=1; i--){
arr_ask[i] = arr_ask[i-1];
arr_bid[i] = arr_bid[i-1];
arr_close[i] = arr_close[i-1];
}
//insert new 0 element
arr_ask[0] = d_ask;
arr_bid[0] = d_bid;
arr_close[0] = d_close;
//update buffer display
for(int i=0; i<tick_count; i++){
b_ask[i] = arr_ask[i];
b_bid[i] = arr_bid[i];
b_close[i] = arr_close[i];
}
//set the previous left buffer val outside the tick count to empty or 0
b_ask[tick_count-1+1] = EMPTY_VALUE;
b_bid[tick_count-1+1] = EMPTY_VALUE;
b_close[tick_count-1+1] = EMPTY_VALUE;
return(true);
}
//+------------------------------------------------------------------+
//| |
//+------------------------------------------------------------------+
void OnDeinit(const int reason)
{
} Disliked{quote} {quote} - when copy n pasting n modding, check what you've just done (this is a common issue for me too), address the #property lines under where b_close is declared - when you double click on a compilation error, it will take you to where the error is, may not be exactly where the issue is, but close enough - highlight and press f1 for "Close" to see how to properly use it {quote} - up to you, as mentioned before, a tick change in bid could be 0.90045 to 0.90047, +0.00002, you can plot 0.00002, or divid by the minimum tick increment _Point,...Ignored
QuoteDislikedBid/Ask. High, Low, Open etc are more like Close.
QuoteDislikedadded the [] and it helped a bit with the errors but not completely. Using Close[i] didnt help either.
- when youre coding something you have to be very specific, there is no vagueness, you need to make clear instructions that have no room for interpretation