When you are working in the Message Flow editor, you can decide how your nodes are aligned within the editor view.
This option is closely linked to the way in which your nodes are arranged. Again, the default for this is left to right, which means that the in terminal of a node appears on its left edge, and its out terminals appear on its right edge. You can also change this characteristic of a node by rotating the icon display to right to left, top to bottom, and bottom to top.
Before you start
To complete this task, you must have completed the following task:
To modify the way in which nodes and connections are displayed in the editor:
For example, if you have changed from a left to right display (the default) to a right to left display, each node in the flow has now also changed to right to left (that is, the in terminal now appears on the right edge, the out terminals appear on the left edge).
If you change the alignment of the message flow, or the arrangement of an individual node, or both, these settings are saved when you save the message flow. They are applied when another user accesses this same message flow, either through a shared repository or through shared files or import and export. When you reopen the message flow, you see these changed characteristics. The alignment and arrangement that you have selected for this message flow have no impact on the alignment and arrangement of any other message flow.
In the Message Brokers Toolkit Version 5.1 you can adjust the zoom by right-clicking
in the editor view and clicking Zoom in or Zoom
out. Alternatively, you can use the drop-down list on the editor
toolbar to specify a zoom percentage.
You can also access the editor toolbar to select other options related to the display and arrangement of nodes, for example, snap to grid. These are defined in Message Flow editor.
Related concepts
Message flows
Related tasks
Creating a message flow
Defining message flow content
Adding a node
Connecting nodes
Related reference
Built-in nodes
Message Flow editor
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac02300_ |