TeeChart Pro ActiveX教程(十八):TeeChart运行时要求

下载TeeChart Pro ActiveX最新版本

TeeChart运行时要求

本教程介绍了TeeChart应用程序的运行时安装的某些方面。

TeeChart运行时文件

使用TeeChart应用程序提供哪些文件取决于应用程序的交付方式。标准Windows应用程序与Web应用程序交付不同。

Windows应用程序
  • teechart2017.ocx

    <p>该文件可以在TeeChart安装文件夹中找到。它可以安装在客户端(运行时)机器上您选择的任何文件夹中,但必须注册。</p>
    </li>
    <li>
    <p>teeuserx.hlp</p>
    
    <p>可选编辑器帮助支持。该文件可以在TeeChart安装文件夹下的Docs文件夹中找到。它可以安装在客户端(运行时)机器上您选择的任何文件夹中,但必须注册。</p>
    </li>
    复制代码
Web浏览器应用程序
  • teechart2017.cab或teechart2017.ocx

    <p>您可以将任一文件用于Web应用程序(两者都可以在TeeChart安装文件夹中/下方找到)。teechart2017.cab是teechart2017.ocx的压缩版本,更适合在考虑速度的互联网上进行传输。CAB文件已经过身份验证。可以在客户端计算机中手动安装文件并手动注册,也可以使用HTML OBJECT Codebase链接动态加载和注册文件。如果下载速度是您的应用程序中更重要的元素,您可能希望考虑使用替代&#39;小&#39;TeeChart CAB文件部分中列出的替代&#39;缩减功能&#39;版本的TeeChart 。</p>
    </li>
    <li>
    <p>teeuserx.hlp</p>
    
    <p>可选编辑器帮助支持。该文件可以在TeeChart安装文件夹下的Docs文件夹中找到。使用http连接下载时,不会自动注册此文件,因此应通过其他方式注册。</p>
    </li>
    复制代码
*使用PNG格式导出(所有应用程序类型)
  • TeeChart Pro AX使用动态链接库Lpng.dll来方便导出为PNG格式的图形文件。该DLL包含在TeeChart安装程序中,并在安装时安装到Windows \ System [32]文件夹中。如果您需要可再发行应用程序导出为PNG格式文件,则应将此DLL包含在安装程序文件中。Lpng.dll是公共域名。

替代'小'TeeChart CAB文件

备注的TeeChart Cab文件随注册版本一起提供。该文件位于TeeChart安装文件夹下方的CAB文件文件夹中,提供了一组有限的TeeChart功能,从而减小了Cab的大小。CAB文件已经过身份验证。

teesmall2017.cab文件中缺少功能
  • 没有TeeChart编辑
  • 没有JPEG支持
  • 没有打印预览器
  • 没有关于屏幕
  • 没有ODBC访问权限
  • 没有OpenGL

通过使用HTML OBJECT Codebase参数,可以使用与teechart2017.cab文件相同的方式使文件可用。

注册表考虑

在拥有TeeChart Pro的ActiveX控件必须在Windows注册表中注册是可用的。在大多数情况下,注册是自动完成的,但在某些情况下(例如,在创建自己的应用程序安装例程时),必须手动注册Control。在拥有TeeChart运行编辑器帮助文件,teeuserx.hlp还必须注册在运行时从的TeeChart编辑器支持求助电话。

在为已编译的Charting应用程序创建安装程序或安装例程时,您应该为TeeChart注册包含以下方面:

  • 注册teechart2017.ocx 要手动注册teechart2017.ocx,请使用Window的Regsvr32.exe。

    <p>例:</p>
    
    <pre class="brush:csharp;">
    复制代码

    syntax: regsvr32.exe installdrive:\installfolder\teechart2017.ocx eg. regsvr32 c:\Program files\MyChartApp\teechart2017.ocx

    <p>teeChart2017.ocx注册表项将自动添加到Windows注册表的多个位置。无需手动编辑注册表。</p>
    </li>
    <li>
    <p>注册teeuserx.hlp 要注册teesuerx.hlp,您必须创建一个例程,或手动添加到Windows注册表中:</p>
    
    <pre class="brush:csharp;">
    复制代码

    Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Help] Entry: "teeuserx.hlp"="drive:\installfolder\installsubfolder"

    Eg. "teeuserx.hlp"="c:\Program files\MyChartApp"

    (Here assuming that teeuserx.hlp is installed in the c:\Program files\MyChartApp folder)

    You may create a .reg registry file (which is ascii format) by exporting the key from an existing registry entry. The file may be used for direct importation to a client installation.

    <p>使用teechart2017.cab文件和HTML OBJECT代码库时,TeeChart会自动注册到客户端Windows机器。如果您希望将teeuserx.hlp用于Web浏览器应用程序,则必须创建自己的例程来注册帮助文件。这可以选择性地使用导出的注册表文件(通常以.reg结尾),该文件在执行时自动更新寄存器(例如双击)。</p>
    </li>
    复制代码
自定义TeeUser运行时帮助

teeuser运行时编辑器帮助(rtf文件)的源保存在TeeChart Pro安装文件夹下的Docs \ Teeuser帮助源文件夹中。可以使用标准的32位Windows帮助编辑器或Microsoft Word95编辑帮助源,并使用Microsoft的32位帮助编辑器v4.00.0950 +或使用Microsoft Word97 / 2000进行编译,并使用Microsoft的32位帮助编辑器v4.02.0060 +进行编译。如果使用Word97编辑,则无法使用早期版本的Microsoft 32位帮助编辑器进行编译。帮助编辑器可从Microsoft免费获得。 使用标准帮助编辑器编辑/编译或使用Microsoft帮助编译器进行编译时,请打开teeuserx.hpj帮助项目。

使用修改后的版本替换默认的teeuserx.hlp文件并根据注册表注意事项部分中的说明在客户端计算机中注册它将启用该帮助以便在运行时使用。

*注意:如果使用Word编辑帮助.rtf文件,请确保仅编辑页面内容,而不是修改脚注或隐藏代码。对于该措施,为避免错误,建议使用Word选项“显示代码”,激活。

OpenGL支持

要在设计时或运行时使用OpenGL支持,请确保在Windows计算机中启用OpenGL。标准Microsoft dll,OpenGL32.dll,在Windows95和Windows98的情况下通常位于Windows \ System文件夹中,在Windows NT的情况下通常位于Winnt \ System32文件夹中。 替代OpenGL驱动程序可从Silicon Graphics,www.sgi.com获得,适用于NT和Windows 95/98。 根据您的CPU和视频硬件,可能是Silicon Graphics的OpenGL dll比Microsoft的更快。

在同一台机器上运行TeeChart Pro AX v8和TeeChart Pro AX v2017。

您可以在同一台PC上并排使用TeeChart Pro AX v8和TeeChart Pro AX v2017。使用TeeChart Pro AX 8或更早版本编译的应用程序将继续使用该版本。请考虑以下因素:

如果您的应用程序不在TeeChart GUID中编码(当TeeChart放置在Form上时会自动发生)并且仅使用CreateObject for Chart实例,则CreateObject将创建TeeChart Pro AX v2017图表。由于代码在很少的实例中向后兼容( 有关详细信息,请参阅教程15,VC ++ MS应用程序),然后版本的更改对应用程序用户是透明的。可以通过在创建期间命名版本来修复特定版本创建(例如,在VBScript中创建TeeChart v6图表:CreateObject(TeeChart.TChart.6)

转载于:https://juejin.im/post/5c777143f265da2de165b410

=========================================== TeeChart Pro Activex Control v2018 MS .NET COMPATIBILITY Copyright (c) 1997-2018 by Steema Software SL All Rights Reserved. http://www.steema.com email: info@steema.com supportx@steema.com =========================================== Document updated: June 2004 TeeChart Pro Activex Control MS Visual Studio .NET compatibility notes =========================================== Please see the release.txt release notes for bugfix and feature information about this release. =========================================== Changes for NET compatibility - The Chart.Series(xx) read-only property has been replaced by a Function method (affects only code written in VC++ and similar languages that make direct reference to Get_ and Set_ of properties). The new Series method (called Series) changes visibly by removal of the property 'Get_' element of the Function. The change is required due to a current MS.NET import restriction causing non-import of ActiveX properties that have an index parameter (only affects the root level of controls !). For a VB application no code change is necessary. Please see the following notes for other environments. The original property has been hidden in the interface and renamed to aSeries keeping its existing Dispid to support backward compatibility with applications compiled with previous releases of TeeChart 5. - The TChart OnSeriesBeforeAdd method uses a boolean variable called 'Continue'. "continue" is a keyword in C# (the language used to interim compile TeeChart namespace information in .NET). This had caused an import problem with the earlier releases of Visual Studio .NET. As a precaution we have chosen to rename the parameter to 'MoreValues' for the TeeChart Pro ActiveX Control. Notes on use: ------------- - Constant names in NET require full reference by default: eg. AxTChart1.AddSeries(TeeChart.ESeriesClass.scLine) Upgrading existing projects: ---------------------------- Upgrading existing Visual Studio projects works without manual intervention in code for most simple projects. Notable points relating to import: VISUAL BASIC project: ===================== - Designtime saved content of a Chart does not always successfully import to a NET project. We recommend you open the project first in its current environment (eg. Visual Basic v6) and provoke a change in the Chart and resave the project. That will update the saved frx Chart information data to v5.0.3. Then save the Chart content as a tee file by right-clicking the Chart and selecting 'Export'. Some projects 'may' then import the saved Chart correctly without further steps required. If the Chart content doesn't import successfully then right-click on the Chart and import the saved tee file. If the project fails to import, clear the Chart content after saving it to tee (remove and replace the Chart with an empty one) and re-import following the above step to later import the saved tee file. - Calls to interfaces not supported. In Visual Studio v6 and prior versions, it was possible to connect components by interface. eg. TeeCommander.Chart=TChart1 This is no longer possible. You should use the integer link: eg. TeeCommander.ChartLink=TChart1.ChartLink - Colour definition requires update TeeChart colours map as UInt32 when imported to NET. The colour definition when applied takes the following form: .Labels.Font.Color = System.Convert.ToUInt32(System.Drawing.ColorTranslator.ToOle(System.Drawing.Color.Cyan)) - Some event syntax is incorrect on import. Notably the Mouse events which are 'duplicated' by default NET appointed events. If you find event syntax to be incorrect, modify the syntax as follows: eg. Private Sub TChart1_OnMouseUpEvent(ByVal eventSender As System.Object, _ ByVal eventArgs As AxTeeChart.ITChartEvents_OnMouseUpEvent) _ Handles TChart1.OnMouseUp 'do something End Sub - Some form object (eg. Checkbox) events may fire before the Chart is loaded. That didn't occur in VB6 and will require a workaround in VB.NET if Chart properties are referenced in this way at Form load. eg. taken from VB Drag Points example: 'Check1.CheckStateChanged may fire when form is intialized Private Sub Check1_CheckStateChanged(ByVal eventSender As System.Object, _ ByVal eventArgs As System.EventArgs) _ Handles Check1.CheckStateChan ' switch 2D / 3D view... TChart1.Aspect.View3D = Check1.CheckState ' enable scroll-bar only in 3D... HScroll1.Enabled = Check1.CheckState End Sub In the above event the View3D line will fail as the Chart isn't yet loaded when the event is called. An option to workaround it may be to set a boolean 'OK_To_Run' variable to set after the first Chart Repaint. eg. OK_To_Run false on load and set to true in Form_Load event after Chart is populated, etc. Private Sub Check1_CheckStateChanged(ByVal eventSender As System.Object, _ ByVal eventArgs As System.EventArgs) _ Handles Check1.CheckStateChan ' switch 2D / 3D view... If OK_To_Run = True Then TChart1.Aspect.View3D = Check1.CheckState End if ' enable scroll-bar only in 3D... HScroll1.Enabled = Check1.CheckState End Sub Microsoft recommend a similar step (add a IsInitializing property to the Form). We'll be taking a closer look at these issues to see if we can recommend less demanding steps to resolve them. VISUAL C++ project: ===================== The Series declaration has changed. The easiest way to upgrade the project is to import TeeChart classes before upgrading the project to .NET. 1. All references to 'GetSeries(xx)' should be changed to 'Series(xx)' That will call the new Series method that returns the Series Interface (just as the predecesor property did). The Series property has been name changed to aSeries, retaining its DispId to support existing compiled applications. 2. The following is handled automatically if you import the TeeChart classes. For reference, the following changes occur to the Series declaration. *Note you should not need to do anything if you import TeeChart to your project. a) In the TChart.h Class header file the GetSeries declaration changes to: CSeries Series(long SeriesIndex); b) In the TChart.cpp Class impl. file the GetSeries declaration changes to: CSeries CTChart::Series(long SeriesIndex) { LPDISPATCH pDispatch; static BYTE parms[] = VTS_I4; InvokeHelper(0x14, DISPATCH_METHOD, VT_DISPATCH, (void*)&pDispatch;, parms, SeriesIndex); return CSeries(pDispatch); } Projects should then compile without issue. =========================================== Use of Strong Named Assemblies =========================================== If you compile Strong Named Assemblies then imported ActiveX Controls must also be Strong Named. The Utilities folder contains a Strong Name compiled version of: \Utilities\VS.NET\Strong Named DLLs - AxInterop.TeeChart.dll - TeeChart.dll They may be used to replace the automatically generated AxInterop.TeeChart.dll and Interop.TeeChart.dll created when TeeChart AX is added to a Windows Form. You should remove auto-generated dlls from the references list in the project Solution Explorer and from the Obj folder of the project and Debug or Release Bin folder. Then copy in the new Dlls to Obj and Bin folders and reference the new Dlls from their Obj folder location. =========================================== Please send us details about any other issues found to: http://www.teechart.net/support/modules.php?name=Forums Many thanks ! =========================================== http://www.steema.com support: http://www.teechart.net/support/modules.php?name=Forums -------------------------------------------
=========================================== TeeChart Pro Activex Control v5 Copyright (c) 1997-2002 by David Berneda and Marc Meumann All Rights Reserved. http://www.steema.com email: info@steema.com supportx@steema.com =========================================== July 2002 TeeChart Pro Activex Control v5 v5.0.4.0 Release notes: ===================================== For information about differences and use of TeeChart Pro ActiveX v5 with respect to TeeChart Pro ActiveX v4 please refer to the 'Upgrading from TeeChart v4.doc' document accessible via the TeeChart Program Manager group. =========================================== Changes for this release: ------------------------- Bugs resolved: 1. Print Preview from TeeCommander for multi-page Charts in v5.0.3.x functioned incorrectly. Now resolved. 2. ZoomPen definition failed to save in tee files. Now resolved. 3. Integer overflow error reported after multiple zooms. Now resolved. 4. The property 'Controls' in TeeCommander coincides with a protected word in VBA. To permit access to this functionality in VBA the method has been duplicated with name 'Buttons'. 5. Omission in previous releases, the OffsetValues ValueList for Bar3D Series is accessible by code for this release. 6. Omission in previous releases, MACD function has new Period3 property. 7. Visual Studio.NET doesn't support the passing as Interface of the Chart to the TeePreviewPanel AddChart method. A substitute AddChartLink has been added for this release to accept ChartLink. 8. The keyword 'Months' as a database field name was incompatible with prior translation system for non-english language versions' db access via the Editor. Now resolved. 9. TeePolar/Radar Series problem when labelling datasets of 13, 19, 25, etc. values. Internal rounding error resolved. 10.Help button on Chart Editor not functioning. Now resolved. New features: 1.
=========================================== TeeChart Pro Activex Control v2018 MS .NET COMPATIBILITY Copyright (c) 1997-2018 by Steema Software SL All Rights Reserved. http://www.steema.com email: info@steema.com supportx@steema.com =========================================== Document updated: June 2004 TeeChart Pro Activex Control MS Visual Studio .NET compatibility notes =========================================== Please see the release.txt release notes for bugfix and feature information about this release. =========================================== Changes for NET compatibility - The Chart.Series(xx) read-only property has been replaced by a Function method (affects only code written in VC++ and similar languages that make direct reference to Get_ and Set_ of properties). The new Series method (called Series) changes visibly by removal of the property 'Get_' element of the Function. The change is required due to a current MS.NET import restriction causing non-import of ActiveX properties that have an index parameter (only affects the root level of controls !). For a VB application no code change is necessary. Please see the following notes for other environments. The original property has been hidden in the interface and renamed to aSeries keeping its existing Dispid to support backward compatibility with applications compiled with previous releases of TeeChart 5. - The TChart OnSeriesBeforeAdd method uses a boolean variable called 'Continue'. "continue" is a keyword in C# (the language used to interim compile TeeChart namespace information in .NET). This had caused an import problem with the earlier releases of Visual Studio .NET. As a precaution we have chosen to rename the parameter to 'MoreValues' for the TeeChart Pro ActiveX Control. Notes on use: ------------- - Constant names in NET require full reference by default: eg. AxTChart1.AddSeries(TeeChart.ESeriesClass.scLine) Upgrading existing projects: ---------------------------- Upgrading existing Visual Studio projects works without manual intervention in code for most simple projects. Notable points relating to import: VISUAL BASIC project: ===================== - Designtime saved content of a Chart does not always successfully import to a NET project. We recommend you open the project first in its current environment (eg. Visual Basic v6) and provoke a change in the Chart and resave the project. That will update the saved frx Chart information data to v5.0.3. Then save the Chart content as a tee file by right-clicking the Chart and selecting 'Export'. Some projects 'may' then import the saved Chart correctly without further steps required. If the Chart content doesn't import successfully then right-click on the Chart and import the saved tee file. If the project fails to import, clear the Chart content after saving it to tee (remove and replace the Chart with an empty one) and re-import following the above step to later import the saved tee file. - Calls to interfaces not supported. In Visual Studio v6 and prior versions, it was possible to connect components by interface. eg. TeeCommander.Chart=TChart1 This is no longer possible. You should use the integer link: eg. TeeCommander.ChartLink=TChart1.ChartLink - Colour definition requires update TeeChart colours map as UInt32 when imported to NET. The colour definition when applied takes the following form: .Labels.Font.Color = System.Convert.ToUInt32(System.Drawing.ColorTranslator.ToOle(System.Drawing.Color.Cyan)) - Some event syntax is incorrect on import. Notably the Mouse events which are 'duplicated' by default NET appointed events. If you find event syntax to be incorrect, modify the syntax as follows: eg. Private Sub TChart1_OnMouseUpEvent(ByVal eventSender As System.Object, _ ByVal eventArgs As AxTeeChart.ITChartEvents_OnMouseUpEvent) _ Handles TChart1.OnMouseUp 'do something End Sub - Some form object (eg. Checkbox) events may fire before the Chart is loaded. That didn't occur in VB6 and will require a workaround in VB.NET if Chart properties are referenced in this way at Form load. eg. taken from VB Drag Points example: 'Check1.CheckStateChanged may fire when form is intialized Private Sub Check1_CheckStateChanged(ByVal eventSender As System.Object, _ ByVal eventArgs As System.EventArgs) _ Handles Check1.CheckStateChan ' switch 2D / 3D view... TChart1.Aspect.View3D = Check1.CheckState ' enable scroll-bar only in 3D... HScroll1.Enabled = Check1.CheckState End Sub In the above event the View3D line will fail as the Chart isn't yet loaded when the event is called. An option to workaround it may be to set a boolean 'OK_To_Run' variable to set after the first Chart Repaint. eg. OK_To_Run false on load and set to true in Form_Load event after Chart is populated, etc. Private Sub Check1_CheckStateChanged(ByVal eventSender As System.Object, _ ByVal eventArgs As System.EventArgs) _ Handles Check1.CheckStateChan ' switch 2D / 3D view... If OK_To_Run = True Then TChart1.Aspect.View3D = Check1.CheckState End if ' enable scroll-bar only in 3D... HScroll1.Enabled = Check1.CheckState End Sub Microsoft recommend a similar step (add a IsInitializing property to the Form). We'll be taking a closer look at these issues to see if we can recommend less demanding steps to resolve them. VISUAL C++ project: ===================== The Series declaration has changed. The easiest way to upgrade the project is to import TeeChart classes before upgrading the project to .NET. 1. All references to 'GetSeries(xx)' should be changed to 'Series(xx)' That will call the new Series method that returns the Series Interface (just as the predecesor property did). The Series property has been name changed to aSeries, retaining its DispId to support existing compiled applications. 2. The following is handled automatically if you import the TeeChart classes. For reference, the following changes occur to the Series declaration. *Note you should not need to do anything if you import TeeChart to your project. a) In the TChart.h Class header file the GetSeries declaration changes to: CSeries Series(long SeriesIndex); b) In the TChart.cpp Class impl. file the GetSeries declaration changes to: CSeries CTChart::Series(long SeriesIndex) { LPDISPATCH pDispatch; static BYTE parms[] = VTS_I4; InvokeHelper(0x14, DISPATCH_METHOD, VT_DISPATCH, (void*)&pDispatch;, parms, SeriesIndex); return CSeries(pDispatch); } Projects should then compile without issue. =========================================== Use of Strong Named Assemblies =========================================== If you compile Strong Named Assemblies then imported ActiveX Controls must also be Strong Named. The Utilities folder contains a Strong Name compiled version of: \Utilities\VS.NET\Strong Named DLLs - AxInterop.TeeChart.dll - TeeChart.dll They may be used to replace the automatically generated AxInterop.TeeChart.dll and Interop.TeeChart.dll created when TeeChart AX is added to a Windows Form. You should remove auto-generated dlls from the references list in the project Solution Explorer and from the Obj folder of the project and Debug or Release Bin folder. Then copy in the new Dlls to Obj and Bin folders and reference the new Dlls from their Obj folder location. =========================================== Please send us details about any other issues found to: http://www.teechart.net/support/modules.php?name=Forums Many thanks ! =========================================== http://www.steema.com support: http://www.teechart.net/support/modules.php?name=Forums -------------------------------------------
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值