Either can work, it depends on your intended outcome. In your first example y is a count of occurrences and in the second y is a time interval. I mentioned the timer since the bid or ask can move without a tick, you'd probably want to run your code ...

I will code your EAs and Indicators for no charge

Yessir I did, only ever test on blank chart. Did you experience the same issue as the op?

I will code your EAs and Indicators for no charge

I 100% believe in you I think you’ll feel a bit like riding a bike again. The syntax is C based so it is something you know already, like variable and function data types: int, double, float, long, etc; for loops: “for(int i=0;i<20;i++)”; and if ...

I will code your EAs and Indicators for no charge

It seems to work okay for me, the line isn't moving when I change time frames. Perhaps there is another reason? Also trivial but you don't need UninitializeReason() if you are using OnDeinit(), the variable in OnDeinit(const int res) is the same ...

I will code your EAs and Indicators for no charge

I think if you open the file in an editor you will feel pretty comfortable tackling this on your own. Mql is “C++” and I am confident even a mediocre C programmer could work the file to their needs. It is simple code, a template really. In fact the ...

I will code your EAs and Indicators for no charge

Nooo I am no god, you’re just persistent Haha not forex_jesus, just helper of the community. I use that alert code a lot so it’s easy to copy paste honestly

I will code your EAs and Indicators for no charge

I also made this if anyone needs a strong reminder their max spread has been exceeded. It colours the area between the Ask and Bid. Negative lookback uses future area to the right. Alerts, notifications, emails included.

I will code your EAs and Indicators for no charge

Can try this out

I will code your EAs and Indicators for no charge

You're missing all the #property lines //+------------------------------------------------------------------+ //| ProjectName | //| Copyright 2018, CompanyName | //| http://www.companyname.net | ...

iTime Issues

It was quick copy/paste, I hope nothing got out of order or clipped.

iTime Issues

Use the OnTimer events call. You can put all the main flow code into one function and have it called in start and ontimer. In init() add EventSetMillisecondTimer(1); In start() or OnCalculate() call your main flow function, something like: int ...

iTime Issues

Maybe something like this: file Use levels or boxes options.

I will code your EAs and Indicators for no charge

Twas a group effort, BlueRain and me. I hope helps bring in the green pips

Need help with 'array out of range'

Yes, because if rates_total-prev_calculated==0, is the same as rates_total==prev_calculated, and means all bars have been calculated. To avoid the first time alert on attaching, then put "&&prev_calculated!=0" into the if statement.

Need help with 'array out of range'

I mean it looks like what you have does work and using Bars is like using rates_total. But if want to change it could do something like: if(rates_total-prev_calculated>0&&prev_calculated!=0)

Need help with 'array out of range'

Assuming the rest of the code works as intended then yes. Also this: ThisBarTrade = Time[0]; if (Bars != ThisBarTrade ) is comparing two different data types. Bars is the count of bars on the chart and Time[0] is a date time. Granted it can be cast ...

Need help with 'array out of range'

iHigh etc returns the actual double price not an int index. The section under //Get Prices, is using the prices of the chart: High[], Low[], etc are the prices for the current chart. So every index you get above is only being used with A/U prices. ...

Need help with 'array out of range'

Why are you using iHighest/iLowest for a single bar? (...,1,0) Just use the cohl arrays directly. I don’t know if it’s intended or not but you are taking the highest/lowest of a different pair and then use that bar index on only aud/usd arrays. ...

Need help with 'array out of range'

I would not use NormalizeDouble with prices for OrderSend or OrderModify. Better to normalize with something like point: price=floor(price/point)*point. Or since you are using the Ask price, you can just put Ask directly in the OrderSend. Why do you ...

I will code your EAs and Indicators for no charge

So only the view is being adjusted. If you look at your print values when MABuffer is commented out and then look when uncommented, they are the same and OBV values are the same. Perhaps you need to do some linear scaling?

How to program an indicator with OBV and its MA?