Hi sidhartha70,

Thanks for your thoughts. I actually did try something like that, but seemed to 
find some sensitive timing issues. My objective was, as soon as I detected a 
new bar (this was using one minute bars), to access information about the just 
completed bar. At least in my experience, it was necessary to introduce a delay 
so that the Ref(XYZ, -1) function returned information about the bar I was 
interested in and not the one before it. In the end, I just felt uncomfortable 
that I had an approach I could rely on as being rock solid.

I think I'll revisit it, but in the end, would love to be able to rely on a 
built-in function. Assuming I'm successful in revisting a one-off solution, 
I'll post the results (code).

The exploration start/stop is a little tougher. One way to do it is to invoke 
AA through VBScript, and do your own pre- and post- processing. Another might 
be to create ficticious symbols guaranteed to be the first and last symbols 
visited by the exploration code and use the name() function to test for them.

Regards,

Gordon 

--- In amibroker@yahoogroups.com, "sidhartha70" <sidharth...@...> wrote:
>
> Gordon,
> 
> I'm pretty sure you can code for this type of stuff already in AFL. You can 
> simply set up your on checks to see if an event has occurred, and if it has, 
> execute any code you want...
> 
> For example, OnBar() that you are talking about could be achieved by looking 
> for a change in DateTime() of the most recent bar...
> 
> --- In amibroker@yahoogroups.com, "Gordon" <gordon@> wrote:
> >
> > Hi All,
> > 
> > I just posted a new suggestion at www.Amibroker.com/feedback. It occurred 
> > to me that most AB users don't know about or use the feedback area. So, I 
> > wanted to take a second to highlight the value of using the site to add 
> > suggestions and provide feedback for existing ones. If you haven't gone 
> > there (you need to be a registered AB user), there are tons of neat 
> > suggestions.
> > 
> > My second reason for posting is, I'm curious to know how many would find 
> > the addition event-based AFL coding useful -- e.g. functions you write that 
> > would be executed automatically upon the occurrence of specific events, 
> > such as the current bar jused completed (geared toward tick and other 
> > intra-day charts), backtester started, exploration finished, etc.
> > 
> > Regards,
> > 
> > Gordon
> >
>


Reply via email to