Revision as of 18:24, February 14, 2017 by Bonniem (talk | contribs) (Show Advanced Properties)
Jump to: navigation, search

Hiding File Types and Blocks

You can hide Composer file types by using base Eclipse functionality in Composer.  This may be desired when certain functionality is not applicable to your environment.  For example, when using Voice capabilities, and VXML is used but not CCXML, you may wish for the CallControlXML file type to be hidden from the File > New menu. The following steps may be used:

  1. Select Window > Customize Perspective. The Customize Perspective  dialog appears.
  2. Click the Shortcuts tab.
  3.  Expand Composer and check Others.
  4. In the list of shortcuts, uncheck <file-type>, where <file-type> is the type to be hidden.
  5. Click OK.
  6. Repeat for other perspectives if desired.

This customization is specific to the workspace. If you use other workspaces, you must customize them as well. This is base Eclipse behavior where customization is saved within the workspace.

Hiding Diagram Building Blocks

You can also customize the palette of diagram-building blocks. Right-click a block category (such as Flow Control) and select Customize. You can then hide and unhide blocks in that category.

Hiding/Displaying the Palette

Should you accidentally cause the palette to disappear, click the Hide/Show Palette triangle.

100px.png


Show Advanced Properties

When creating a diagram in Composer perspective, this button appears on the right side of the Composer GUI, between the palette of blocks and the Properties view.

Comp814ShowAdvProp.jpg

Certain block properties are hidden by default from the Palette. If you have permission you can use the Show Advanced Properties button to display/hide these properties.

Moving the Location of a View

To move a view to another location, hold down the cursor next to the view name until you see a red circle with a slash in the middle. Keep holding down the cursor, move the view to the desired location, and release the mouse button.







Comments or questions about this documentation? Contact us for support!