TeeChart direct access to data
Posted: Wed Jun 20, 2018 9:26 am
Hi All,
Time ago, back to 2001 I was working in an application with C++ Builder that required frequent plot updates of a lot of points in a TimePlot. All I tried to make it faster was not fast enough, and then I took a look at the sources and I've found that I could make virtual one method (I can't recall whitch one) and then In C++ Builder I could inherit from a class and develop a proxy class that was allowing to TChart access to my internal storage structures without need to Add the points.
I'm now back to a similar application where plots change frequently. Lot of time is spent just clearing and adding points to get rid of the old view and create the new view. All my data it is already in memory and it will be way more efficient if I could do something similar this time, because the improvement in performance could be huge in my particular user case. As all this clear Series points and add points could be avoided, like I did time ago.
By 2001 TChart sources were way smaller and easier to understand in a reasonable amount of time. 17 years later TeeChart has grown quite a bit and it is not longer so easy to follow the source code in a reasonable amount of time. I would like to know if it is still feasible such a design and where I would need to look in the sources.
Thanks
Javier
Time ago, back to 2001 I was working in an application with C++ Builder that required frequent plot updates of a lot of points in a TimePlot. All I tried to make it faster was not fast enough, and then I took a look at the sources and I've found that I could make virtual one method (I can't recall whitch one) and then In C++ Builder I could inherit from a class and develop a proxy class that was allowing to TChart access to my internal storage structures without need to Add the points.
I'm now back to a similar application where plots change frequently. Lot of time is spent just clearing and adding points to get rid of the old view and create the new view. All my data it is already in memory and it will be way more efficient if I could do something similar this time, because the improvement in performance could be huge in my particular user case. As all this clear Series points and add points could be avoided, like I did time ago.
By 2001 TChart sources were way smaller and easier to understand in a reasonable amount of time. 17 years later TeeChart has grown quite a bit and it is not longer so easy to follow the source code in a reasonable amount of time. I would like to know if it is still feasible such a design and where I would need to look in the sources.
Thanks
Javier