You're correct, of course, in that it doesn't generate an interrupt. But having programmed polling routines 40+ years ago and interrupt driven routines as well it can be done with both although, as you say, with a LOT less trouble via interrupts.
d > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of scourt2000 > Sent: Tuesday, January 29, 2008 8:51 PM > To: [email protected] > Subject: [amibroker] Re: Trading platform + AB > > > "This can be done now using GetCursorMouseButtons(), > GetCursorXPosition() and GetCursorYPosition() . HOWEVER there is no > function that returns the ChartID for the chartpane over which the > mouse is clicked" > > Hi Herman, > > All of that chartID stuff would not be necessary if you tied the > mouse button clicks to well-known event routines (like that ones I > mentioned as an example) which get called specifically from the AFL > code behind a chart pane. > > You want this type of facility event-driven, not polled. Polling > puts more work on the user's side and brings up other unpleasant side- > effects like what you just described. > > Which would you rather do? > > 1) Code a rats nest of polling inline with your other AFL code > > -or- > > 2) Have a well-known function called on a mouse click with all of the > information you need provided as the function parameters directed to > the script already bound to a particular chart pane? > > Anyone who chooses #1 last seriously programmed a computer more than > 20 years ago. > > "That's available now - check the list of functions, duude." > > No it's not...duude [sic] > > > > Please note that this group is for discussion between users only. > > To get support from AmiBroker please send an e-mail directly to > SUPPORT {at} amibroker.com > > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG: > http://www.amibroker.com/devlog/ > > For other support material please check also: > http://www.amibroker.com/support.html > > Yahoo! Groups Links > > >
