We discussed this and it appears that the problem is that because he loads the same indicator with different settings like in something like 100 blocks, this takes long time. For some reason MQL5 loads indicators slowly. And in the EAs I programmed MQL5 to load them on demand, which is not the official way of doing that. So I have a "while" loop that waits for indicator to load for 500 ms and then throw that error. So I changed that time to 5 seconds. Unfortunately I still don't know how to make MQL5 to load indicators more quickly.

Can you show it, please?

Thank you very much for your explanation. Now I understand it much better. I will try what you suggest.

Sorry, is my mistake. Is working now.

it appears to work as it should. thank you

I know this problem. It's MQL itself that orders object in this way, I guess that its algorithm doesn't look at the numbers the way you do

Yes, there is a bug in this block, when the color is selected to be "Any color". I still don't know how to fix it, but until I decide what to do you can specify the exact color over there and it should work.

I think that it's only you, because obviously no one else is reporting the same problem in the forum and in emails. But you can also compile the EA on the website and download the .ex4 version. What MetaEditor is this, maybe it belongs to MetaTrader 5? Because in MQL4 we have HideTestIndicators(), while in the new MQL5 they added this function named TesterHideIndicators(). That's why I'm just defining TesterHideIndicators() for MQL4. And MetaTrader 4 is actually stopped, at least on my PC the version that I have is from 19 May 2017.

Interesting. I think this happens when the second symbol in the pair is not the same as the deposit currency. It works properly for me on EURUSD when the deposit currency is USD. I need to check what is going on.

Ok. Thanks.

This is a warning, not an error. I fixed this warning, but it was not a problem anyway.

Interesting. This function iBars was not present in MQL5 as long as I know and that's why I defined it. On the server the compiler I use is a bit older and that's why it works. On your PC MetaTrader is the newest version and maybe they added this function lately, although I can't find anything about it in the documentation.

You are welcome.

Don't hesitate to ask anything in the forum because we are learning together.

@leksand

This is not a bug... just a technical glitch in your logic.

It happens because it's technically impossible to have an "Ask" quote below the lowest price from candle ID 0 to candle ID 10. In Forex candles are in most cases constructed with "Bid" quotes, and because "Ask" is always above Bid, it's impossible that any Ask quote in candle 0 goes below the lowest Bid price. If candle 0 makes a new low of the last 11 candles (from 0 to 10 we have 11 candles), the lowest price will be a "Bid" quote... so even if you choose Bid, it will never be below the lowest price.... So, the lowest Bid will be equal to (but not lower than, "<") the lowest price..

On the other hand, the ">" signal works because the Ask quote can be above the highest price, because the highest price comes from a "Bid" quote and, again, Ask is always above Bid..

I suggest you to choose candle IDs from 1 to 10, not from 0 to 10... then it should work

It's fixed, thanks!!

You know, those block number are not looking good anyway. Some weeks ago I believe I fixed one problem that caused blocks to suddenly receive such a big numbers, but who know, maybe there is another problem somewhere. So I will suggest to try this: 0_1527724171498_1113c52c-1c97-4503-acd3-c1160d84f0e9-image.png
... and then check if everything still works, just in case.

Oh, suddenly it works after I change the constant name. I added new prefix just to test.

So, for that blocks move problem, I see it happens on that project on the main page and also in each project in /Examples. But I wonder if anyone sees this problem in his own personal projects?