If your talking about built in AFL functions like PlotOHLC() etc then they have 
built in abilities to plot beyond the end of the last bar... so wondering about 
how much space in there is not something you have to worry about.

If it's low level gfx, then I'm not sure I can help. I do use low level gfx 
quite a bit but it is either 'on or off' my chart... I tend to use it for 
display buttons & grids etc..etc...

There may well be a way to get back the info you want... maybe someone else can 
point you in the right direction...?

As a point of note Conrad, I wouldn't worry so much about code speed right 
now... my advice is to get down what you want, then worry about removing any 
superfluous calculation afterwards...

--- In [email protected], "sidhartha70" <sidharth...@...> wrote:
>
> Just to be clear Conrad, you are talking about low level gfx drawing 
> operations....? Rather than those in any way related to the AFL Plot() 
> PlotOHLC() etc..etc...?
> 
> --- In [email protected], "Conrad Joach" <consolejoker@> wrote:
> >
> > I'll ask this question in a totaly different way. Depending on a user's 
> > settings, there is a certain amount of padding on the right side of the 
> > chart when the chart is scrolled all the way to the right.
> > 
> > It could be none, but default is more than none. Mine is set to 15 bars.
> > 
> > My script would like to know how many bars of padding are visible on the 
> > chart. For instance if the default is 15, and the user hasn't moved the 
> > scroll bar, then there are 15 bars of space that I would like to plot some 
> > data in.
> > 
> > But if the user has scrolled just a bit, there may be only 7 blank bars 
> > left on the right, and I want to plot here just those 7 bars. If I plot 
> > more than 7, I am going to draw into the right hand price axis, plus waste 
> > resources.
> > 
> > It may be that when the user scrolls back in time, they see 0 bars. I would 
> > like to know not to plot anything beyond the bars that are visible.
> > 
> > So how can one find this out?
> >
>


Reply via email to