[ARCHIVE!] Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Can't go anywhere without you - 4. - page 23

You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
1th: your philosophy of changing the array size is defective from the very beginning, you can do with 10 cells to process indicator readings in 99 out of 100 cases;
2nd: to recalculate these readings on every tick is a whim of an uninformed brain.
Igor, either you start giving sensible advice on how to get out of the situation, or don't post at all.
Rough, but to the point) After experimenting, I realised that data on the number of points can be summed up in one cell. This is sufficient.
So point him in the right direction, not just stating the fact of deadlock.
This is a thread...
It's OK! Helping people on this forum is invaluable! A month or two ago I didn't know how to work with arrays at all)
If the array is heterogeneous, you should probably convert all elements to string type and then search for the required one using
StringFinde(https://www.mql5.com/ru/forum/138609/page22#613148). Correct me if I'm wrong.
Thank you. I found the function.
I just don't understand how to use it correctly.
It returns only a place in string where the searched part starts, but not a part.
I need a part of a string.
Thanks. I found the function.
I just haven't figured out how to use it correctly yet.
It only returns the place in the string where the searched part starts. but not the part.
I need a part of the string.
StringSubstr ().
Just what I need.
Thank you very much.
Good evening, everyone!
The problem: I can't figure out how to use the function for finding the intersection point of two lines (I've tried Kim's function too, but the result is the same).
The point is that sometimes the crossover is detected in the wrong place.
Here's what happens:
The red horizontal line is the price level calculated by the function. The yellow one is a level that should be.
What is interesting, this bug does not always happen: often the intersection is defined as it should be...
Below I am pasting the code of the function.
The trailer contains an Expert Advisor for testing it.
Please advise what I am doing wrong!
Thank you very much in advance)