Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

componenteditor - Tool

	Package	synthesis
	Module	componentmodels

Postscript file available

A graphical user interface for displaying & editing a component.

include "componenteditor.g"

Constructors

componenteditor	Create an componenteditor tool

Functions

dismiss	Shut down the GUI
done	Shut down the componenteditor tool
get	get the component currently being edited
gui	Start up the GUI
use	Supply a component to be edited
which	return the index of this component

Description

The componenteditor is a graphical user interface that allows the user to view & modify components. To use it you need to be in a windows environment ie., the display environment must be set prior to starting up AIPS++.

The componenteditor can be in one of two states, view mode or edit mode.

View Mode

The component editor always starts up in view mode. In this mode you cannot change any of the fields in the component. View mode is useful for browsing a component. To switch to Edit mode you press the Edit button just below the menu bar.

Edit Mode

In edit mode you can modify the component. Be aware that the editor reads all input from the screen in edit mode so it is important to display all numbers with sufficient precision. To switch to back to view mode press the View button just below the menu bar.

You can always tell which mode you are in because the entry field backgrounds are grey (and input is disabled) while in view mode, but white in edit mode.

There are a variety of buttons and pull-down menus for specifying the units and reference frames for various aspects of the component. In edit mode these specify how the numerical value is to be interpreted. In view mode they control the units, reference frame and precision of the displayed numerical values. Buttons that do not make sense in view mode, eg. those to change a components shape, are disabled in view mode.

When editing fields in this GUI it is suggested you press return at the end of each field. This will force the GUI to parse the current line and redisplay what it has read. However some effort is made to ensure that displayed fields are synchronised with the internal data even if you do not press return. This is down by redisplaying the data whenever a button is pressed. However the data is not redisplayed on every keystroke.

The componenteditor window is split up into seven fundamental frames. I'll describe these in the following sections.