Mark Silverwood

It appears to me that your main requirements are: - Ability to plot moving average lines, - Draw coloured rectangles with the positions defined by price and time coordinates, and...

I appreciate that this would be a useful feature, however there are hundreds of useful features which could also be implemented and one of the goals of this library is...

Apologies, I forget to reply to this message. The names I would suggest are: ```typescript interface Execution { price: number; time: Time; } interface Trade { open: Execution; close: Execution;...

Yes, I believe that this is expected behaviour (only check value after a timeout like requestAnimationFrame). For the chart to know the width of the timeScale it needs to render...

@skdillon Would you say that your issue is the same as this one? - https://github.com/tradingview/lightweight-charts/issues/1271 - https://github.com/tradingview/lightweight-charts/pull/1281

When the chart is automatically adjusting the price scale min and max range values, this is called `autoScale` and what it is doing is automatically adjusting the scale to ensure...

You are correct. AutoScaleInfo won't help for that case. I'll mark the issue as a feature request.

Would this `isDisposed` property only be `true` if the [`remove()`](https://tradingview.github.io/lightweight-charts/docs/api/interfaces/IChartApi#remove) method is called on the IChartApi? Since the `remove()` method is only called externally (not within the library), you should...

I would recommend removing the reference to the chart instance (in the state variable) whenever the `remove()` method is called because the chart instance wouldn't be of any use going...

In general, you wouldn't need to remove and create a new chart when the data (or instrument) is changed. It would be better to only use a single chart instance...