![]() The help file and documentation include a reference guide, a user guide, demos with detailed 'how to' explanations, end-user help and a comprehensive example project (with complete sources) that contains 376 forms. Each class has properties that in many cases are other sub-classes, either from TeeChart API or from Embarcadero's VCL set of classes. Technically speaking, TeeChart Pro consists of 161 modules (units) and 90 form screens, totalling 798 object classes. Properties, methods and events follow a general, consistent style. Almost everything is an object or belongs to an object class. The architecture of TeeChart is fully Object Oriented. ![]() The TeeCommander component (a toolbar with charting specific buttons) provides one-click access to TeeChart editors, print preview dialogs and common features. These editors are available at design-time and also at run-time. TeeChart includes powerful and complete editor dialogs, for almost every component and sub-component. Net assemblies to group modules as per their own needs. ![]() Developers can create custom packages or. Packages (groups of units), are logically grouped depending on the category of each feature. Other rendering outputs are OpenGL (3D), SVG, DirectX, etc but they aren't as fast as plain old GDI for realtime charting.ĭivided into several modules (units) to reduce executable sizeĪ chart using the basic styles ( line, bar, area, pie, point ), has an executable size of only 190Kb. The code is streamlined as much as possible to increase internal speed, especially when re-drawing. ![]() Data is stored in dynamic arrays that are very closely mapped to memory which makes access and modifying the arrays almost as fast as the computer processor. The Chart graphical code speaks directly to Windows GDI API. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |