Should probably just use an indicator instead of a script, I guess for this its up to you, but you'll need to start checking return values and checking if data you want is even ready yet, and waiting until it is ready. In mql5 when you use an ...

I will code your EAs and Indicators for no charge

No, that is already handled by the terminal option for magnet sensitivity. That is a very specific nuance. Sounds like you want something else entirely.

I will code your EAs and Indicators for no charge

Right you are, and I already started writing before eess gave the link, so here's mine anyway, it handles more objects that aren't covered by the link. Snap_to_OHLC_rect_hl_arr_txt_lbl - input magnet in pixels - will snap to closest ohlc within ...

I will code your EAs and Indicators for no charge

There is a general setting for it:

I will code your EAs and Indicators for no charge

- added option to use atr instead, when points/porog is set to 0 - multipler to the atr value

I will code your EAs and Indicators for no charge

- you can express a change in any price value as a number of _points, which is the minimum price increment of a symbol, ie 589points, eg turning a decimal length of meters into an integer count of millimeters - I doubt you can prove this - start ...

I will code your EAs and Indicators for no charge

As bluerain stated you wont be capturing 2 events at once, it's not how onchartevent works. - to see how onchart event receives events, print its params out, you will see it as a queue of events, one after another, with differing l/d/s params - ...

I will code your EAs and Indicators for no charge

There is no s in my member name. int delta_ask = int((Ask-prev_ask)/_Point); - it is asking how many points changed, to the curent ask, from the previous ask, which will be an integer, a quantity/count/number of points eg 0.004 change to 0.007, is a ...

I will code your EAs and Indicators for no charge

- added all tfs - options to use any/all tf

I will code your EAs and Indicators for no charge

You're getting the value of Close[i], but i is not declared anywhere above it, let alone set to be anything, it's like saying give me Close[?]. Close[] is an array of the close prices of the current chart, a single index value is the close price of ...

I will code your EAs and Indicators for no charge

- there is no error, you found a limitation of the ellipse object, the lowst scale it accepts is limited to 0.001, and so scale increments are also limited to x0.001 - there are certain symbolprice/tf/zoom combinations that will reach this limit, ...

I will code your EAs and Indicators for no charge

VLine_Daily_wLabel - 1 vertical line and label with it - full styling of line/label, share same color - label can be placed/anchored/offset anywhere - label text is either user input, or time hour/min with/without date, put a spacebar in the text to ...

I will code your EAs and Indicators for no charge

- yes, bid/ask are single values, open/high/low/close[] are timeseries indexed arrays of price data on the chart - its an array, you get the value in the [index] you ask for - i hasnt been declared anywhere, it has no meaning - read the code line ...

I will code your EAs and Indicators for no charge

- when copy n pasting n modding, check what you've just done (this is a common issue for me too), address the #property lines under where b_close is declared - when you double click on a compilation error, it will take you to where the error is, may ...

I will code your EAs and Indicators for no charge

Alright as an example, with some additional stuff removed, heres the source that gives that output, with some notes scattered around. Note that the separate udpate_display() function isn't necessary and can be rolled into oncalc where the delta ...

I will code your EAs and Indicators for no charge

- technically every indicator is setup to be tick based due to the oncalc() present - oncalc() is the event function in indicators that gets called every tick, or every chart history update/change, loading of indicator, tf change - unless youre ...

I will code your EAs and Indicators for no charge

- follow what the compilation errors are telling you - you're never setting the bid array as a buffer, you're setting the ask array twice - the if statement in shiftarray is unclear, proper bracing for an if statement is //check 1 thing, do 1 thing ...

I will code your EAs and Indicators for no charge

Nothing is stopping you from googling "indicator total power", there are several sites that talk about it and have it. Below is one. url

I will code your EAs and Indicators for no charge

There's still 8 buffers for 4tfs and it's still cycling through all 4 tfs and theres still 4 text objects being made. You should add a short record in the source of your changes to the indicators.

I will code your EAs and Indicators for no charge

You can address them, you just blindly copy n pasted it in. i_bsw was some random variable for barshift of the w time, its what the ileftcandle is. Prev_calc is something that belongs in OnCalc in indicators. The point is: - make the rect - get the ...

I will code your EAs and Indicators for no charge