- 博客(0)
- 资源 (9)
- 收藏
- 关注
TeeChart Pro Activex Control v2018
===========================================
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
-------------------------------------------
2018-05-10
TeeChart2018ActiveX_0_2_9Eval3264
===========================================
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
-------------------------------------------
2018-05-10
TeeChart Pro Activex Control v5
===========================================
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.
2018-05-10
LJH_C++程序一般需依次经过的几个步骤
经过编辑、编译、连接和运行四个步骤。编辑是将C++源程序输入计算机的过程,保
存文件名为cpp。编译是使用系统提供的编译器将源程序cpp生成机器语言的过程,目标文件为obj,由于没有得到系统分配的绝对地址,还不能直接运行。连接是将目标文件obj转换为可执行
程序的过程,结果为exe。运行是执行exe,在屏幕上显示结果的过程。
2017-09-21
Visual Studio 2010 操作技巧系列:常用功能心得笔记
Visual Studio 2010的操作技巧文章在每个人都会拿到的资料库里,不过似乎不是很多人看过,因此决定将文章放到部落格上供大家参考学习,要做好开发工作绝对不能不熟悉每天都在使用的开发工具,对工具的掌握度越高,相对的工作效率也就越高,也越能够专注在更有创造力的事情上!
2015-06-24
C/C++语言贪吃蛇在VC6.0和VC2010环境下运行
在设计这个程序中我主要学会了如何运用以下有关C语言和C/C++的知识
1)函数定义是要做到顾名思义是很重要的,它对读程序的人正确认识程序
十分重要,在修改这个程序的过程中也能很快找到程序各模块的作用,大大增
加了程序的可读性。
2)分析函数先从main()函数入手。Main()函数是C/C++源程序编译时的开始,
从main()函数开始读函数可将其他函数的功能理解得更透彻。
3)在做程序的时候先列框架,将这个程序所要达到的目的(功能)分析出
来,选择正确的数据结构然后在将程序模块化,按照模块编写函数更加简单合理。
4)我还了解了很多的库函数的作用,如字符串函数中有很多对字符串进行
处理的函数,起功能我都有所了解。
5)学会了有关头文件的使用方法,及系统调配问题的解决方法等。
6)了解到了注释的重要性。
2015-01-10
贪吃蛇VC6.0和VC2010环境下运行
在设计这个程序中我主要学会了如何运用以下有关C语言和C/C++的知识
1)函数定义是要做到顾名思义是很重要的,它对读程序的人正确认识程序
十分重要,在修改这个程序的过程中也能很快找到程序各模块的作用,大大增
加了程序的可读性。
2)分析函数先从main()函数入手。Main()函数是C/C++源程序编译时的开始,
从main()函数开始读函数可将其他函数的功能理解得更透彻。
3)在做程序的时候先列框架,将这个程序所要达到的目的(功能)分析出
来,选择正确的数据结构然后在将程序模块化,按照模块编写函数更加简单合理。
4)我还了解了很多的库函数的作用,如字符串函数中有很多对字符串进行
处理的函数,起功能我都有所了解。
5)学会了有关头文件的使用方法,及系统调配问题的解决方法等。
6)了解到了注释的重要性。
2015-01-10
空空如也
TA创建的收藏夹 TA关注的收藏夹
TA关注的人