gsphelp  Copying, Moving and Deleting Components

<< Click to Display Table of Contents >>

Navigation:  GSP components > Components general >

gsphelp  Copying, Moving and Deleting Components

Previous pageReturn to chapter overviewNext page

Apart from copying components from the libraries when building new models, components can be moved and copied on the model panels and to and from other model panels. This allows copying components including specific component data from other engine models, enabling the user to create model projects serving as libraries similar to component libraries with predefined template components.

 

On a model panel, the user can move a selected component by just dragging it across the white area of the panel.

As with normal Windows operation, pressing the Ctrl button while dragging makes a copy of the component. With the Ctrl key pressed, components can also be copied from other model panels.

 

Also, the (Windows-) customary copy, cut and paste commands can be used (available in the Edit menu on the model panel and as keyboard shortcuts (Ctrl-C, Ctrl-X and Ctrl-V), which work with an invisible "component clipboard" for copying and moving operations.

 

When multiple components are selected, these operations apply to all selected components.

GSP automatically repositions components on the form to prevent invisible components located outside the forms. Use the scroll bars to scroll the model panel if necessary or resize the model panel. In case component overlap results after a copy or move action, the modeler will be visibly notified.

 

The Delete command in the Edit menu, pop-up menu or invoked by pressing the Delete key, removes the selected components. Not all components can be deleted, the option may therefore be disabled. Note that deleting components, unless there is no parent component, just moves the component to the deleted list where it is ignored by the program. There is an option to restore the component through the Deprecated components window (double-click entry in the list).

 

Since the case management features are incorporated in the modeling environment, additional constraints are set on moving and deleting components. Note that a component of a Configuration or a Case can have an ancestor, deleting a child must be inhibited to ensure a proper model structure since this structure is based on inheritance.

 

Moving of Configuration type components is inhibited in a Case model, since this results in a change of the configuration of the engine layout. Note that the Case model is an instance of the Configuration with a sole existence to run the configuration as is. In order to provide the case simulation of input, specific case control components can be used alongside the normal (numerical) data input fields.