Copying or Moving Graphical Items

Graphical items of a block diagram can be added to the same diagram, another diagram of the same component, or a diagram of another component, via cut, copy and paste. ASCET uses its own internal clipboard for graphical information, so these operations have no effect on the Windows clipboard.

You can cut/copy/paste all kinds of graphical items: elements, operators, included components, method-/process-local elements, etc. However, keep in mind the following restrictions:

• Graphical items can be pasted only to the currently loaded diagram.

• Method-/process-local elements can be pasted only to a single method or process at a time.

  Elements copied/cut from different source methods/processes are pasted to the same target method or process.

• Pasting an element or included component to the same diagram creates a new graphical occurrence of the same object, not a new object.
• Pasting a method-/process-local element to the same diagram and the same method/process/runnable creates a new graphical occurrence of the same element, not a new element.
• You cannot paste elements to a method/process/runnable that does not support additional elements (e.g., a CT block method, or automatically generated runnables in an SWC).

• Only those elements are pasted that are allowed in the target component and the target method/process/runnable.

  You cannot, e.g., paste a return value into a process, a state into a block diagram class, etc.

The following happens when you paste graphical items, depending on where you paste:

A. Same Component, Same Diagram

All graphical elements are pasted. Sequence calls are reset.

B. Same Component, DifferentDiagram

The behavior depends on the conflicts found during paste, and to the solutions you select.

• no conflicts

  All graphical elements are pasted to the currently loaded diagram.

  Sequence calls of method-/process-/runnable-local elements are adjusted to the target method/process/runnable the elements belong to. Possible adjustments are:

  • different method name
  • different (or reset) sequence number if the old numbers are in use

  Sequence calls of other elements are reset.

• Name conflicts

  All graphical elements are pasted to the currently loaded diagram.

  Sequence calls of method-/process-/runnable-local elements are adjusted to the target method/process/runnable the elements belong to. Possible adjustments are:

  • different method name
  • different (or reset) sequence number if the old numbers are in use

  Sequence calls of other elements are reset.

  If you selected the respective solution, the conflicting element names are changed.

  If necessary, the visual properties (e.g., read/write access pins) are changed to reflect property changes.

  Note
  A name conflict occurs if a method-/process-/runnable-local element (argument or local variable) in the target diagram and method has the same name and type as a pasted method-/process-/runnable-local element.

• Type conflicts

  All graphical elements are pasted to the currently loaded diagram.

  Sequence calls of method-/process-/runnable-local elements are adjusted to the target method/process/runnable the elements belong to. Possible adjustments are

  • different method name
  • different (or reset) sequence number if the old numbers are in use.

  Sequence calls of other elements are reset.

  If you selected the respective solution, the following adjustments can be performed:

  • Conflicting element names are changed.
  • Visual properties (e.g., read/write access pins) are changed to reflect property changes.
  • The graphical item is changed to reflect the type change (e.g., array vs. scalar element).
  • Connection lines are updated to reflect type changes and/or invalid connections (e.g. connections between cont and log).

  Note
  A type conflict occurs if a method-/process-/runnable-local element in the target diagram and method has the same name and a different type as a pasted method-/process-/runnable-local element.

C. Different Component

The behavior is basically the same as for "same component, different diagram".

In addition, it is checked if pasting is allowed at all. If it is not, an error message opens and pasting is canceled.

If pasting is allowed, it is checked if the pasted elements are allowed in the target component and method/process/runnable. If at least one pasted element is not allowed (e.g., a return value in a process), another error message opens that lists the elements that cannot be pasted. You can continue pasting the allowed elements, or cancel the procedure.

A schematic view of the procedure for B and C is given in Flow Chart: Copying or Moving Graphical Items.

See also

Flow Chart: Copying or Moving Graphical Items

Copying/Moving Items in the Same Diagram (BDE)

Copying/Moving Items Between Diagrams (BDE)