Here is the key event sequence in the chart code:
Private Sub TRecordSet1_DataChange(ByVal nType As Long, ByVal nParam1
As Long, ByVal nParam2 As Long)
Picture1.Refresh
End Sub
'Refresh invokes _Paint
Private Sub Picture1_Paint()
Call PicTradeReDraw
End Sub
This code fires on a sales event(irrespective wether price AND size
change). _DataChange calls Picture1.Refresh, and the _Paint event
fires. The Paint event precipitates out of the .Refresh call.
Assuming a viable symbol and interval were entered, and in essence
ahead of this, an interval specific serverbased recordset is
opened..and the live up front interval is appended dynamically and
tracked on the client side.
In essence, the chart is painted from the semi-static, near term,
server sided recordset as returned in FieldArray. You have to deal
with the upfront interval dynamically.
The FieldArray dimension is controlled in this line of code:
If .TRecordSet1.Init(100, 0) > 1 Then .Picture1.Refresh
In this case we have a 100 item RecordSet.....
.....
I am just scraping the surface....but the dynamics seem pretty
straight forward ...
Scott
--- In twsapi@y..., "Christian Czirnich" <crocodile_1964@g...> wrote:
Scott,
thank's for your example, which will be of great help.
I had some problems to connect to Quote.com until i updated the
ContinuumX.ocx file to a more recent one. I have the file attached
for everyone to try, if the older one does not work. Replace Scott's
version with this one and the project should work.
Best regards,
croc
* REPLY SEPARATOR *
On 07/10/2002 at 21:03 marinindextrader wrote:
Qcharts users wishing to integrate Qcharts data into their IB TWS
application, their is a new file in the files section. The project
is
module oriented to afford portability. Much of the module work
could
be accomplished in the direct Qcharts calls, but I set it up to
keep
your main form clear of superfluous code. All the work is pushed
out
to the module.
If you are not a Qcharts user, this Zip will be of no interest.
Title Name: QchartsExample.Zip
Link:
Zip Pack Includes: Entire sample project, Exe file, and extensive
but
dated documentation, and the Qcharts OCX.
Let me know if you have OCX issues. The OCX normally ports with
Qcharts and QLink, and gets deposited either in the Qcharts
directory, or the Program Files/Common Files/Qcharts directory. If
you have issues check these locations first. Downloading QLink and
installing it usually registers the OCX properley. Remember, it
isn't
enough to have the OCX, it needs to be registered with the system
registry in order for the IDE to see it in the components
directory.
The project should port with the OCX on form, but I have included a
copy of the OCX for those having issues AND savy enough to do a
manual registration.
Again, an install of QLink should set things in order in terms of
OCX.
Let me know if you have issues; I would be interested in feed back.
Scott
Owner
To unsubscribe from this group, send an email to:
twsapi-unsubscribe@y...
Your use of Yahoo! Groups is subject to
