It’s always going to show current week if the bar isn’t changed from 0 double hi=iHigh(NULL,10080,0),lo=iLow(NULL,10080,0); This part just checks for HH or LL if(upper[0]!=hi)fillArray(upper,hi); if(lower[0]!=lo)fillArray(lower,lo); Also ...

I will code your EAs and Indicators for no charge

I had a typo in that one: if(rates_total==prev_calculated)return 0; 0 should be rates_total

I will code your EAs and Indicators for no charge

I don't want to step on anyone's toes but you can try this if you just want the current week bar's high and low: file Or any timeframe: file

I will code your EAs and Indicators for no charge

Perhaps there was just some miscommunication. It is very likely here dealing with programming and multiple user’s languages. But the code is working correctly as coded. Its not working as you intend. BlueRain is doing great and I’m sure they can ...

I will code your EAs and Indicators for no charge

Yes those are the hi/lo for the previous week, the 2nd bar.

I will code your EAs and Indicators for no charge

On loading on W1

I will code your EAs and Indicators for no charge

Working on my terminal. Check the experts tab of your terminal for error messages after attempting to load the indicator.

I will code your EAs and Indicators for no charge

Most here do not know MQL5, I do not

I will code your EAs and Indicators for no charge

That looks good to go. You are using bar=0 or the current un-closed bar. Just know when you first load AlertMe it will wait for a bar to complete before beginning it’s condition checks. If you want to see what it is doing, type “print” anywhere into ...

AlertMe!

Thanks for trying it out If I understand what you're saying, then yes to add more conditions load another instance of AlertMe. There isn't any subwindow interaction. iCustom calls indicators "invisibly". So you just input into AlertMe like ...

AlertMe!

Haha ask away buddy. I have no idea if the indicators/downloads will be an issue, that is outside my control. Whatever iCustom documentation or google says about that is what will happen. You aren't calling the indicator that is running on the ...

AlertMe!

Symbol parameter is thrown out. Name parameter replaces "iCustom". Everything else is the same. You can even input it with the parentheses if you want: half-trend nrp(current,2,0,1) The bolded "line index" is the buffer, the list of values in the ...

AlertMe!

Haha yes the manual part needs some help with clarification and readability. Aside from the below info, yessir that is how you do a downwards cross alert. The parameters you have filled in would be: name: half-trend nrp timeframe: current or 0 ...

AlertMe!

Buy at the Ask and Sell at the Bid, maybe you forgot to change the Ask to Bid when you changed to OP_SELL. Also potentially could be getting Error 130 as well

I will code & automate your strategy for free

Whelp then this won’t help you, it’s for MT4

Counting Green and Red Candlesticks

MT4 log file does not update in real-time could be your issue url

I will code your EAs and Indicators for no charge

I am likely not the best source for this information. However, if your prices are moving too fast then perhaps slippage would be the first thing to adjust. If you have actually used the program and your orders won’t send, the first place to look is ...

I will code your EAs and Indicators for no charge

If you run in a loop without exiting it might be helpful to also use RefreshRates() call.

I will code your EAs and Indicators for no charge