Best posts made by roar

All I can say that your EA seems to work during higher daily volatility. But volatility cannot be really forecasted, so I cant give any answers there.

Like this?

https://fxdreema.com/shared/lLJy8gRX

@OntradingX I tried to use current timeframe, but there was an error with the quick example I made.

Here's corrected code:

int openid_current_tf = iBarShift(NULL, 0, iTime(NULL, PERIOD_D1, 0));

if(iClose(NULL, 0, openid_current_tf) > iOpen(NULL, 0, openid_current_tf))
	Comment("Today started with a BULL candle");
else
	Comment("Today started with a BEAR candle");

The same blocks as usual, just change the group filter.

@tec-nacks most news filters dont support that.

Technically its possible, if you get some kind of database of old news records. In fact, I'm willing to code it for you, if you really find such database.

@kavmasayuki my example should work fine.
I dont use this feature myself, but this is how I understand it.

Something like this in the On Init -tab should work.

@gooseman every indicator reserves some amount of your RAM memory. When you have 100 indicators with their memory allocations, there might not be space left for 101st.

Alternative structure: work with just 1 group of blocks, but run the same blocks multiple times, changing the symbol in between. You can put the symbols in an array.

@gery https://www.mql5.com/en/docs/constants/indicatorconstants/prices

it must be exactly "ENUM_APPLIED_PRICE"

@Abade69 to play devils advocate: the statistical metrics for walk-forward system tells how good the EA is fitting different strategies (parameter combinations) to sections of history data, right? There is less evidence that the latest strategy will work today and tomorrow

Record the datetime value of hourly candle:

datetime timevar = iTime(NULL, PERIOD_H1, 123);

Get the candle ID from that time, in selected timeframe:

int idvar = iBarShift(NULL, PERIOD_M1, timevar);

https://www.mql5.com/en/docs/series/itime
https://www.mql5.com/en/docs/series/ibarshift

• You need to draw your button just once, not on every tick or every chart event. Move the draw button to On Init.

• When checking the mouse clicking, you are looking for a different name - "Button1" vs "button 1"

Datatypes (int, bool) are lower case

@talshemtov you need to declare a new constant for each MA setting. Find the correct enumeration from mql5.com:
https://www.mql5.com/en/docs/constants/indicatorconstants/enum_ma_method

Basically you can just use the ChartOpen function: https://www.mql5.com/en/docs/chart_operations/chartopen

https://fxdreema.com/shared/h3f6nEY3

@joseanrod the total number of bars is in variable called Bars.
But the indicator probably needs some history before it can start calculating the indicator results, so you can try something like this:

i = Bars - 100;

https://docs.mql4.com/predefined/bars

@gooseman ok, if MA has a variable timeframe as well, its better to use slightly different structure.

1. Start with the market selection loop
2. Record the currently selected market into "market" variable
3. Run a checkup in custom block: if market is this, set timeframe to this and set rsi target level to this
4. Apply the found timeframe to every next block
5. Run the MA and RSI conditions with the previously selected variable timeframes and target levels

https://fxdreema.com/shared/nvVoaSASc

@gooseman so you have different RSI timeframes and different RSI levels for each symbol?

In that case, I would first record the RSI on all timeframes into their own variables, also record the currently selected market, and then do the symbol + RSI check in one big condition block.
For the syntax, && means "and", || means "or".

This doesnt compile since I dont have all your variables, but I hope you get the idea
https://fxdreema.com/shared/D0LMD4Hnc

To avoid the unnecessary loading of all RSI timeframes for all symbols, you could first do a checkup for the correct TF for the selected symbol, but it is not strictly needed