Errors, bugs, questions - page 1250

 
Tapochun:
Let me try to guess... through determining the increment between line points on two neighbouring candles?

No.

I only said it was possible because it really is possible and it works.

 
DiPach:

Is the protection working? :-)

What motivated you to write this indicator?

 
Silent:

Is the protection working? :-)

And what inspired you to write this indicator?

I'll keep quiet here about the first one (personal).

On the second: the need for trading. As it used to be, so it is now.

I used to use crosshairs to identify and verify by hand (I remember how much time it took). And wildly missed that sort of thing.

P./S.: / * whispering and looking around * / Andrew, we will not develop this subject here, okay? Otherwise for nothing, for nothing a referral to the bathhouse. And it's not a sauna day, it's an ordinary working day.

 
DiPach:

I'll keep quiet here about the first one (personal).

About the second: the need for trading. As it used to be, so it is now.

Once, I remember, I used to crosshair and calibrate by hand (when I remember, I shudder, how much time it took). And wildly missed that sort of thing.

P./S.: / * whispering and looking around * / Andrew, we will not develop this subject here, okay? Otherwise for nothing, for nothing a referral to the bathhouse. It's not a sauna day, it's an ordinary working day.

:-) All righty.

I just wanted to clarify, maybe I don't see all the faults.

ps here's a lesson for men. Instead of forum and sd to shake - went and solved the problem. Beautiful girl :-)

 
DiPach:

Don't talk about what you don't know.

When determining values of the trend line on the area of interest using some common calculations, there is a "pitfall". It may not appear at once. Getting around this pitfall was the hardest part for me.

In general, it would be nice if the ObjectGetValueByTime function in MQL5 would work similar to MQL4 with results. It would not look as on the screenshot.

As a line pricing professional, what is the pitfall?
 
DiPach:

Don't talk about what you don't know.

When determining values of the trend line on the area of interest using some common calculations, there is a "pitfall". It may not appear at once. Getting around this pitfall was the hardest part for me.

In general, it would be nice if the ObjectGetValueByTime function in MQL5 would work similar to MQL4 with results. It would not look as on the screenshot.

"I see one pitfall - weekends and missed bars, if there is anything else, please advise.
 
Talex:
"Pitfall" I see one - weekends and bar skips, if there's anything else, hint.
And what's the pitfall with that? Knowing the line formula, it makes absolutely no difference whether there was a skip (temporary) or not. The candlesticks are following one after the other... You just need to catch the moment of its formation, and then according to the formula...
 
Silent:

Thank you.

/*I'm embarrassed to say this, but the truth is, it was the SD who helped. Without their prompting, I don't know how long I would have been looking for a solution myself. It was just one of those cases when everything is visible and simple ("in front of your eyes"), but "your eyes don't see" until someone points a finger in the right direction.

 
DiPach:

Thank you.

/*I'm embarrassed to say this, but truth be told, it was the BOD that helped. Without their help, I don't know how long I would have been looking for a solution. It was just one of those cases when everything is visible and simple ("in front of your eyes"), but "your eyes don't notice" until someone points a finger in the right direction.

Well, to be fair, I was also told by the SD in my time with the fans where the bug was, if you create a second anchor point in the future.

I still did the solution myself.

So that's right :-) Way to go.

 
Silent:
Thank you, for your kind words!