Command Template Editor
Insert 
History Operation Custom
Input (Part Level)
Show Me the Command Template
Editor
icon allows you to select different types of
pick filtering. When
you select one of these popup options, the appropriate Options
string is filled in for you. Refer
to the Tips & Techniques
(for Advanced Users) section below for more information.
Pick OK
from the Command Field Form when
you're done. The
field definition for Plane will
be added to the Command Template Editor.
Refer to
the Tips & Techniques
section below for more information.
Repeat this procedure for each
Required and Optional input field that you want the command template to
define.
Pick OK to accept the template and close the editor. See below for additional editor options.
Command Template Editor
Options
Name
- This is the name of the command template file (my_template.t).
During
the Insert Custom Input command, the input defined
by the command template is logged with a history operation of the same
name.
Description - Enter a description for the Custom Input here. It will appear when you Open the custom input in the History Manager.
Procedure - Accept the default input for this field. Advanced users should refer to the Tips & Techniques section below for more information.
Other - Accept the default input for this field.
Validate - This option "compiles" the command template and displays an error message if it cannot do so. The template is also validated when you pick OK from the Command Template Editor.
Import, Export - These options can be used to load an existing template file (*.t) or to save (*.t) the template currently defined in the Command Template Editor. Refer to the Tips & Techniques section below for more information.
OK - This accepts the command template and closes the editor.
Cancel - This cancels the command template and closes the editor.
|
If the form will not close during the Insert Custom Input command If the Command Input Form is redisplayed as soon as you pick OK, it means that a field on the form is not defined properly. Check the message area for an indication of the problem. |
|
Why you should Export from the Command Template Editor It's a good idea to Export your template (using a ".t" extension) for future re-use or modification. Once you create a Custom Feature from a template, there is currently no way to recall the version of the template saved with the Custom Feature. |
Tips & Techniques (for
Advanced Users)
|
Advanced users and the "Options" field A
macro/OpenVX advanced user can hand-edit the Options field using any of
the template options described in the OpenVX
documentation. If
you want to specify selection of an insertion plane, the Class should
be set to entity and you should pick the Reference Plane option using
the |
|
Advanced users and the "Procedure" field A macro/OpenVX advanced user can hand-edit the Procedure field to use the editor to design command templates for their OpenVX applications. The Procedure field defines the name of the OpenVX function(idx_in, idx_out) called after the template data has been gathered. For a Custom Feature, this field should always be CustomOp. |
