﻿This example is provided as an illustration "as is", and Agilent Technologies makes
no warranty of any kind with regard to this example.


This product includes ANTLR software version 2  (http://www.antlr2.org/)
License term is available at http://www.antlr2.org/doc/csharp-runtime.html


Some Notes on this Example
--------------------------
If there is compilation error on missing Agilent.Vee.AddInView.dll,
please add the DLL reference by follow steps below:
1. Remove Agilent.Vee.AddInView reference. Right click on Agilent.Vee.AddInView
    and select Remove.
2. Add a reference to Agilent.Vee.AddInView in {VEE Install direction}:\ AddInViews.
    Typically it is C:\Program Files\Agilent\VEE Pro 9.3\AddInViews\Agilent.Vee.AddInView.dll. 
    In 64 bits OS, it could be C:\Program Files (x86)\Agilent\VEE Pro 9.3\AddInViews.
3. Rebuild the solution, there should be no compilation error.


EVO known limitations
---------------------
1.	If an EVO terminal is changed dynamically, it will no longer be shown in the Watch Window. 
	For example, a user is watching EVO A’s terminals in the Watch Window. When the terminal 
	is changed dynamically, EVO A previously watched terminals will be removed from the Watch Window. 
2.	Dynamic terminal changes should only be used in VEE program development and not after 
	it is deployed as a runtime or imported into other VEE program. For example, General vTools 1.0 
	Reporting Graph component is used in a VEE program. At the program runtime, user is not allowed 
	to change the number of traces. In another example, a VEE program containing a public 
	User Function using the General vTools 1.0 Reporting Graph component and the Reporting Graph 
	component is added to Panel. The User Function is then imported to a new VEE program. 
	At this point of time, user is able to change the number of input traces but unable to 
	modify the view-only imported User Function. Running the program will cause complication.
3.	After an EVO terminal is changed dynamically, the entire terminal data container is cleared. 
	For example, for General vTools 1.0 Reporting Graph component, initially there is one data input 
	which is Data 1. After the program is run, Data 1 terminal information with its data container 
	is created and viewable. Ifthe terminal is changed dynamically, Data 1 terminal data information 
	is cleared although the terminal name remains the same.
4.	After an EVO terminal is changed dynamically, the EVO position will move slightly to the 
	bottom-left.
5.	During program development, when there are changes to the EVO, the asterisk symbol is shown at the
	title bar. However, while running a VEE program, the asterisk symbol is not shown although there 
	are changes on the EVO object. 
6.	If an EVO object is configured to have no icon, the icon border is still visible until the 
	program is saved and reopened. 
7.	The EVO UI area is out of VEE control. Thus, it may be difficult to move the EVO object in 
	Panel View. To move an EVO in Panel View, right-click on its border and select Move.


© Copyright 2012 Agilent Technologies, Inc.