UltraWinChart--VisualStudio.NET环境下丰富的客户端图表_visualstudio.net绘制图表资源-CSDN文库

共2个文件

htm：1个

exe：1个

5星 · 超过95%的资源需积分: 50 61 浏览量 2006-03-16 00:00:00 上传评论收藏 6.27MB ZIP 举报

摘要 UltraWinChart与ASP.NET 中UltraWebChart 一样，提供了丰富的对象模块，可视化的显示大量以及各种分类信息，为Windows Forms应用程序带来前所未有的方便。UltraWinChart内置了大量的图形备选项，包含了设计时各种选项，以及内置的美学增强功能。使得图表数据具有前所未有的心动、精美和专业。组件列表技术特性应用场景适用于.NET环境下图表显示应用程序运用优势 2D/3D图表类型 — ;;; ;;; ;;; ;;; 包含了所有主要的图表类型：Bar, Column, Line, Area, Pie, Scatter, Bubble, HeatMap, Candle, HiLow, and OpenClose Financial等等。智能化显示功能 — ;;; ;;; ;;; ;;; UltraWinChart独有的IntelliRend™;;;技术，大大提高了使用效率和可用性。我们将每一种便利，直观的设计理念，高级开发人员控件都融入于UltraWinChart之中。数据绑定和非绑定模式 — ;;; ;;; ;;; ;;; 使用DataSource属性，可从数据库或数组中读取图表。内部的过滤让可提供的数据模式于所需绘制的图表选择类型相匹配。更可让开发者在图表绘制中调整行和列的包含/非包含的情况。强大的美学增强— 图表不仅仅采用点阵表示，最重要的是数据的外观显示。为了轻松的显示您的图表，UltraWinChart提供了内置的增强功能： 1）边缘圆滑过渡-边缘圆滑过渡的显示图表图像，生成高级数据显示，并自动圆滑边缘和颜色转换。 2）alpha混合和透明 — UltraWinChart提供了完整的alpha混合和透明控件，而且可以全球设置。 3）背景图象 —可以在图表的背景中显示一些公司的数据信息，例如公司的logo标志和“机密”的水印记号。 4）增强的颜色模式 —可避免显示多余的点或杂乱的图表项。 5）创新的分层设计 — UltraWinChart提供了分层设计，并可自动混合这些分层，以达到最佳的视觉效果。 6）图标符号 —UltraWinChart可生成大量的图标集，完全控制图标的外观。标签 - 高级工具使用提示帮助—可完全定制工具提示，提供了优雅的停靠并显示了对细节的注重。设计时超级方便 —能够真正帮助开发者实现RAD（实时应用程序开发）。UltraWinChart 提供了高级的用户界面属性编辑器，所见即所得的图表设置，加上与所选图表相关联的上下文属性以及设计时绑定到一个DataSet。支持Windows事件 —提供了丰富的无缝集成的事件集，监测用户与图表数据的交互。数据高亮显示—当鼠标移动，移上或点击时，图表项中的数据将会自动高亮显示，提供给应用程序的用户丰富强大的交互功能。强调细节—UltraWinChart 加强了细节部分，其中包括RAD设计时配置、自动数据缩放和数据高亮显示、高级工具使用提示帮助、完全可自定义的图标符号、标签、打印等等。开发环境 ";;;Microsoft Visual Studio .NET Microsoft Visual Basic .NET";;; ";;;Microsoft Visual C++ .NET Microsoft Visual C# .NET";;; .NET Common Language Runtime V1.0 支持平台标准报价 5,450 元人民币 * 以上报价仅供参考，具体以厂商正式报价为准。电话 021-58549800 Email: tools@sh.grapecity.com http://www.grapecity.com/china

资源推荐

资源详情

资源评论

收起资源包目录

ultrawinchart20_trial.zip （2个子文件）

Readme.htm 10KB

UltraWinChart20Trial.exe 6.7MB

<html> <head> <meta http-equiv=Content-Type content="text/html; charset=windows-1252"> <meta name=Generator content="Microsoft Word 10 (filtered)"> <title>Infragistics UltraWinChart Readme</title> <style>  </style> </head> <body lang=EN-US link=blue vlink=blue> <div class=Section1> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=3 width="100%" noshade color=black align=center> </div> UltraWinChart(TM) .NET Windows Forms Control v2.00.5000.78.01 - June, 2003 (C) Copyright Infragistics, Inc., 2001-2003 Windsor Corporate Park, 50 Millstone Road, Building 200 - Suite 150, East Windsor, NJ  08520 USA Voice (609) 448-2000, Fax (609) 448-2017, <a href="http://www.infragistics.com/">http://www.infragistics.com</a>   <div class=MsoNormal align=center style='text-align:center'> <hr size=3 width="100%" align=center> </div> This document contains release notes for UltraWinChart. Be sure to read through the help file topics for important information on how to best use UltraWinChart. <div class=MsoNormal align=center style='text-align:center'> <hr size=3 width="100%" noshade color=black align=center> </div> .NET Framework Compatibility: All included assemblies have been built against the Microsoft .NET framework RTM build. You must have the RTM build of the framework installed for the product to work. Updating Projects to Work with Version 2 Controls This topic provides important information about updating exisitng projects to work with the Version 2 Infragistics controls. Version 2 controls are the .NET DLL files for Infragistics products that have been updated to reference the Version 2 Shared and Win common assemblies. <a name=overview></a>Version 2 Update Overview The names of the assembly files for the Version 2 controls have been changed. They now have ".v2" appended to their names. So for example, the version 1 UltraWinGrid control assembly was distributed in a file called Infragistics.Win.UltraWinGrid.dll. The Version 2 UltraWinGrid assembly is named Infragistics.Win.UltraWinGrid.v2.dll. This naming convention allows both version 1 and version 2 controls to coexist in the Visual Studio toolbox. The version 2 controls will display a red triangle in the upper left corner of their toolbox icons to distinguish them from the Version 1 versions. In order to make version upgrading as painless as possible the internal namespaces have not been changed. This means that you do not have to change any of your code when updating projects from Version 1 to Version 2. However, since all the controls share the common framework assemblies, this also means that none of the Version 1 controls can coexist with Version 2 controls in the same project. For example, you cannot have a Version 2 UltraWinGrid control in the same project as a Version 1 UltraWinListbar control. <a name=procedure></a>Procedure for Updating Projects To convert an existing project to use version 2 of the controls, perform the following steps: 1.      Make a backup copy of the project first. 2.      Open the project and in the solution explorer expand the 'References' item. Take note of all the 'Infragistics...' references present. This will include at least the Win and Shared assemblies, and possibly other assemblies as well depending on the product. 3.      Remove all the old 'Infragistics...' references. Then add the references back in again, using the corresponding '.v2' assemblies. If the V2 versions do not appear in the list (as indicated by the '.v2' names) then installation of your Version 2 assembly was not completed properly. You should re-run the setup program to correct this problem. 4.      Rebuild the project. If you get a 'Could not transform licenses file...' error, double-click on it and modify the assembly names by appending '.v2' as in the example below: Infragistics.Win.UltraWinGrid.UltraGrid, Infragistics.Win.UltraWinGrid.v2, Version=1.0.5005.15, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb 5.      If you get 'Resource transformation ...' errors, click on the "Show All Files" button at the top of solution explorer. This should add expansion indicators next to the form files. Expand the offending form(s) and open the associated .resx files. You will need to delete the offending entries. Unfortunately, the error messages don't indicate which entries are bad. However, for beta 1 toolbars projects we know that entries named 'resource.Settings', 'resource.Settings1' etc. need to be deleted. Also old grid projects may have entries with 'DisplayLayout' in the name. These should be deleted. We have also found some Appearances persisted into old project .resx files; these should be deleted also. However, entries with names like 'Appearancex.Image' are vali

评论收藏

内容反馈