5.9.8. Menu Reference¶

This reference section describes all Gravis menu entries. In this section, the terms clicked node, clicked edge and clicked element (and in the View Box also clicked view) refer to the object the mouse is over when the context menu is opened. The term current view is the view shown in the active graph window.

If a menu entry can be bound to a keyboard shortcut its operation name appears next to it in its description below. This name can be used to change or assign a keyboard shortcut, see Keyboard shortcuts for details.

5.9.8.1. Main Menu¶

File menu¶

New graph File.NewGraph: Creates a new, empty Graph without any views and with a standard schema for C and C++.
New view… File.NewView: Opens a dialog in which a new view name can be entered and then creates a new empty view with that name.
Open… File.Open: Opens either a graph (RFG) or view (GXL) file. When opening a view file, a new empty graph is created and the view is imported into that graph.
Reload graph… File.Reload: Reloads the currently opened RFG graph from file. If the currently opened graph was modified, the user is prompted to confirm the reload, as it will discard any unsaved changes.
Open recent: Shows a list of the most recently opened files for easy access.
Import views… File.ImportViews: Imports one or more views from a GXL file into the current graph using the view names stored in the file. If a view name is already used, a numeric suffix is appended to make it unique.
Import recent: Shows a list of the most recently imported GXL files for easy access.
Save graph File.Save: Saves the current graph, overwriting the file it was loaded from.
Save graph as… File.SaveAs: Saves the current graph under a new name.
Close graph File.CloseGraph: Closes the current graph. If the graph was modified, there is a prompt allowing it to be saved before closing. Please note that this only applies to actual changes to the RFG, not to layout changes in a graph window.
Graph properties… File.GraphProperties: Shows the attributes of the current graph and allows them to be edited.
Source base path… File.SetBasepath: Shows the base path at which Gravis looks for source files and allows the base path stored in the graph to be overridden.
Run Python script… File.RunPythonScript: Runs a Python script on the current graph.
Run recent script: Shows a list of the most recently run Python scripts for easy access.
Quit File.Quit: Quits Gravis.

Edit menu¶

Run analysis… Edit.RunAnalysis

Opens the analysis window from which an analysis to be executed can be selected.

Architectural mapping

Opens a mapping window (see Section Mapping Window) using the currently assigned roles. The Hierarchy view is always shown as a tree. The Architecture view can be represented as a graph or as a tree:

Architecture as tree… Edit.Mapping.ArchitectureAsTree: The Architecture view is shown as a tree.
Architecture as graph… Edit.Mapping.ArchitectureAsGraph: The Architecture view is shown as a graph.

Architecture pipeline… Edit.ArchitecturePipeline

Opens the Pipeline Setup dialog. It allows loading an architecture pipeline configuration file in order to view and execute the pipeline in Gravis. See Architecture Pipeline Execution.

Recent pipelines

Shows a list of the most recently opened pipeline configurations for easy access.

View menu¶

Increase UI font size View.IncreaseFontSize: Makes the main user interface font larger.
Decrease UI font size View.DecreaseFontSize: Makes the main user interface font smaller.
Original UI font size View.OriginalFontSize: Resets the main user interface font to its original startup size.

These menu entries affect user interface text, e.g., text shown in the View Box, in tree diagrams, in violation lists, in panels like the Node/Edge Types windows, but not labels or notes shown in graphical diagrams.

Increase label font size View.IncreaseLabelFontSize: Makes the font used for graphical diagram labels larger.
Decrease label font size View.DecreaseLabelFontSize: Makes the font used for graphical diagram labels smaller.
Original label font size View.OriginalLabelFontSize: Resets the font used for graphical diagram labels to its original startup size.

These menu entries affect node and edge labels shown in graphical diagrams. They affect all graphical diagrams in the current session.

Window¶

Reset “don’t show again” dialogs Window.ResetDontShowAgainDialogs: Makes Gravis forget about all choices made for “don’t show again” checkboxes in dialogs, allowing all dialogs to be shown again.
Tabs position: Changes the position of the tabs in the central tabbed area (top, bottom, left or right).
Persistent palette visibilities: If ticked, the visibility states of the palette windows (as indicated in the palettes section below this menu entry) are preserved across sessions, which allows switching off individual toolbars permanently for the current user.

The final two sections in the menu are the palettes section and the windows section.

The palettes section lists all dockable palette windows and allows each of them to be shown or hidden. These are:

Node Types: Shows the node types hierarchy.
Edge Types: Shows the edge types hierarchy.
Toolbox: Shows the available tools.
Quick Finder/Zoom/Statistics: Toolbar with the Quick Finder, the Zoom Bar with quick access icons for entries from the Zoom menu, and the Statistics Bar.
Selection Toolbar: Quick access toolbar for entries from the Select menu.
Marking Toolbar: Quick access toolbar for entries from the Mark menu.
Edit/Hide/Show Toolbar: Quick access toolbar for entries from the Edit and Hide and Show menus.

The windows section lists all opened windows for quick reference. Choosing a window entry activates the window.

Help¶

About Help.About: Shows version information about Gravis.
User manual Help.UserManual: Opens the Gravis user manual in a web browser.

5.9.8.2. Context Menu in the View Box¶

Layout¶

If the context menu was opened over the layout column, the menu shows the following entries related to the clicked layout:

Open ’<layout name>’: This is equivalent to double-clicking: It opens the view with the given layout.
Rename layout…: Opens a dialog box in which a new name for the layout can be entered.
Delete layout…: Deletes the layout.
Make default layout: Makes the clicked layout the default layout and moves it next to the view name. The former default layout takes the place of the clicked layout.
Copy layout to: Copies the layout to a target view that can be selected from a submenu. This only makes sense if the target view contains roughly the same nodes as the view from which the layout is copied (or a superset of the nodes). One example where this is useful is to copy layouts from an architecture view to the result view of an architecture analysis run.

Open¶

Hierarchical…: Opens a hierarchical graph window for the view.
Flat…: Opens a flat graph window for the view.
Tree…: Opens a tree window for the view.
With new layout…: Creates a new persistent layout and opens a hierarchical graph window for this layout.
Violations…: Only available if the view is the result view of an architecture check (see Section Performing Architecture Analysis) and the options indicated that the result view should contain violating edges. Opens a window showing a list of architecture violations together with their causing edges.
Conformances…: Only available if the view is the result view of an architecture check and the options indicated that the result view should only contain conforming edges (see Section Performing Architecture Analysis). Opens a window showing a list of architecture conformances together with their causing edges.
Result edges…: Only available if the view is the result view of an architecture check and the options indicated that the result view should contain both violating and conforming edges (see Section Performing Architecture Analysis). Opens a window showing a list of violations and conformances together with their causing edges.
Mapping with architecture as tree…: Only applicable if the Mapping role has been set. Opens a mapping window for the view, which allows nodes from the Hierarchy view to be mapped to nodes in the Architecture view. Both the architecture view and the hierarchy view are displayed as in a tree window.
Mapping with architecture as graph…: Only applicable if the Mapping role has been set. Opens a mapping window for the view, which allows nodes from the Hierarchy view to be mapped to nodes in the Architecture view. The architecture view is displayed as in a hierarchical graph window and the hierarchy view is displayed as in a tree window.
Extract selection (flat)…: Opens a window containing the selected elements of the clicked view in flat mode.
Extract marking (flat)…: Opens a window containing the marked elements of the clicked view in flat mode.

Note

The marking may contain elements that are not present in the clicked view. Those elements are not shown in the opened window.

Edit views¶

View properties…: Opens a View information window for each of the selected views showing the attributes of the view and allowing them to be edited.
Rename…: Renames the clicked view.
Delete view(s): Deletes the selected view or views.
Delete selection: Deletes the selected elements in the clicked view.
Delete marking: Deletes the marked elements in all views. If you want to delete the marking in a single view only, use Select marking in that view, then delete the selection.
New selection identity: Applies unique artificial linkage names to the selected nodes in this view. This is only useful for architecture nodes, not for nodes from source code analysis. When reusing a node in a different context it prevents it from being accidentally merged with an existing node. Shows a warning if there are selected nodes with real source code related linkage names.
Copy view…: Creates a copy of the clicked view.
Union…: Creates the union of the clicked view with another view selectable from a drop down menu.
Intersection…: Creates the intersection of the clicked view with another view selectable from a drop down menu.
Difference…: Creates the difference view of the clicked view and another view selectable from a drop down menu, containing all elements present in the clicked view that are not present in the view chosen from the menu.
Symmetric difference…: Creates the symmetric difference view of the clicked view and another view selectable from a drop down menu, containing all elements only present in one of the views but not both.
Copy selection to…: Copies the selected elements of the clicked view to a target view selectable from a drop down menu. The attached nodes of each selected edge are included, too, even if they are not part of the selection. This operation guarantees to copy all selected elements (and possibly some unselected ones that are required to support the selected elements).
Copy strict selection to…: Copies the selected elements of the clicked view to the view selectable from a drop down menu. Only copies a selected edge if both its attached nodes are selected, too. This operation guarantees to copy only selected elements (but maybe not all of them if some require other elements that are not selected).
Copy selection from…: Copies the selected elements of the view selected from the drop down menu to the clicked view. The attached nodes of each selected edge are included, too, even if they are not part of the selection. This operation guarantees to copy all selected elements (and possibly some unselected ones that are required to support the selected elements).
Copy strict selection from…: Copies the selected elements of the view selected from the drop down menu to the clicked view. Only copies a selected edge if both its attached nodes are selected, too. This operation guarantees to copy only selected elements (but maybe not all of them if some require other elements that are not selected).

Select¶

Same as the Select submenu of graphical windows, see Section Select.

Mark¶

Same as the Mark submenu of graphical windows, see Section Mark

Set role¶

Sets the role of a view. The view roles are used to derive default parameters for analysis and mapping operations.

None: Revoke role.
Hierarchy: Sets role Hierarchy for the view. Used in conjunction with Architecture analysis and Mapping.
Architecture: Sets role Architecture for the view. Used in conjunction with Architecture analysis and Mapping.
Mapping: Sets role Mapping for the view. Used in conjunction with Architecture analysis and Mapping.
Base: Set role Base for the view. Used in conjunction with Architecture analysis and Mapping.

Export as GXL…¶

Export the selected views as a GXL file that can be imported into RFGs. When exporting, the user must select the views whose attributes should be exported as well. Typically, attributes should be exported for all views that are no mapping views.

Run Python script…¶

Runs a Python script on the current view.

Run recent script¶

Shows a list of the most recently run Python scripts for easy access.

5.9.8.4. Context Menu in Graph Windows¶

Open¶

Element information…: Opens an Element information window for the clicked element. See Section Information Windows.
Show source code…: Opens a source code window for the clicked element. See Section Source Code Windows.
Extract selection (flat)… Open.ExtractSelectionFlat: Opens a window containing the selected elements of the current view in flat mode.
Extract marking (flat)… Open.ExtractMarkingFlat: Opens a window containing the marked elements of the current view in flat mode.

Edit¶

Rename…: Only available if there is a clicked node: Opens a dialog into which a new name for the node can be entered.
Reverse edge: Only available if there is a clicked edge: Reverses the edge’s direction, i. e., swaps its source and target nodes. If the edge occurs in more than one view, there is an extra confirmation step.
Delete node/edge: Deletes the clicked node/edge.
Delete selection Diagram.Edit.DeleteSelection: Deletes the elements that are selected in the current view.
Delete marking Diagram.Edit.DeleteMarking: Deletes the marked elements (in all views). If you want to delete the marked elements in a single view only, use Select marking in that view, then delete the selection.
New selection identity Diagram.Edit.NewSelectionIdentity: Applies unique artificial linkage names to the selected nodes in this view. This is only useful for architecture nodes, not for nodes from source code analysis. When reusing a node in a different context it prevents it from being accidentally merged with an existing node. Shows a warning if there are selected nodes with real source code related linkage names.

Mapping¶

This entry is only shown if the current window is a Mapping window.

Select mapped nodes: Selects the nodes that are the mapping partners of the clicked node in the other view (mapping or architecture view).
Select mapped descendants: Selects all nodes in the subtree of the clicked node that have their own mapping and expands the hierarchy to reveal them.
Unmap node (flat): Removes any mapping to/from the clicked node.
Unmap node (deep): Removes any mapping to/from the clicked node and all descendants.
Unmap selection (flat) Mapping.UnmapSelection: Removes any mapping to/from all selected nodes in the clicked view (mapping or architecture view).
Unmap selection (deep) Mapping.UnmapSelectionDeep: Removes any mapping to/from all selected nodes and all descendants in the clicked view (mapping or architecture view).

Select¶

All the operations with names starting with Select are additive, i. e., they only select additional elements and never make the selection smaller. They look at selected elements in the current view only and only select elements in the current view.

Select children of node: Only shown if the menu was opened on top of a node. Selects all immediate children of the node.
Select attached nodes Diagram.Select.SelectAttachedNodes: Selects all endpoints (source and target nodes) of all edges that are selected.
Select source nodes Diagram.Select.SelectSourceNodes: Selects the source nodes of all edges that are selected.
Select target nodes Diagram.Select.SelectTargetNodes: Selects the target nodes of all edges that are selected.
Select attached edges Diagram.Select.SelectAttachedEdges: Selects all edges that have a selected endpoint (source or target node).
Select incoming edges Diagram.Select.SelectIncomingEdges: Selects all edges directed at selected nodes, i.e., edges whose target nodes are selected.
Select outgoing edges Diagram.Select.SelectOutgoingEdges: Selects all edges starting from selected nodes, i.e., edges whose source nodes are selected.
Select connecting edges Diagram.Select.SelectConnectingEdges: Selects all edges between selected nodes.
Select backward closure Diagram.Select.SelectBackwardClosure: Selects the source nodes of all incoming edges of the selected nodes and repeats this until no more nodes are added to the selection. Computes all nodes from which the selected nodes can be reached.
Select forward closure Diagram.Select.SelectForwardClosure: Selects the target nodes of all outgoing edges of the selected nodes and repeats this until no more nodes are added to the selection. Computes all nodes that can be reached from a selected node.
Select two-way closure Diagram.Select.SelectTwoWayClosure: Selects the source nodes of all incoming edges and all target nodes of all outgoing edges of the selected nodes and repeats this until no more nodes are added to the selection. In graph-theoretical terms, this computes the connected components to which the selected nodes belong, interpreting the RFG as an undirected graph.
Select ancestors Diagram.Select.SelectAncestors: Selects all parents, parents of parents, etc. of the selected nodes.
Select children Diagram.Select.SelectChildren: Selects all immediate children of the selected nodes.
Select marking Diagram.Select.SelectMarking: Selects the marked nodes.
Select top-level nodes Diagram.Select.SelectTopLevelNodes: Selects the root nodes of the node hierarchy.
Select by query… Diagram.Select.SelectByQuery: Opens a Query dialog to select nodes by their properties, see Section Query-based operations.
Select all Diagram.Select.SelectAll: Selects all nodes and edges.
Deselect nodes Diagram.Select.DeselectNodes: Deselects all nodes.
Deselect edges Diagram.Select.DeselectEdges: Deselects all edges.
Deselect by query… Diagram.Select.DeselectByQuery: Opens a Query dialog to deselect nodes by their properties, see Section Query-based operations.
Deselect all Diagram.Select.DeselectAll: Deselects all nodes and edges.
Invert selection Diagram.Select.InvertSelection: Toggles the selection status of all nodes and edges.
Clip selection to visible Diagram.Select.ClipSelectionToVisible: Leaves only elements selected that are visible in the current window, i. e., deselects nodes and edges that are currently hidden (see Section Hiding Elements), that have a type that is currently hidden (see Section The Node and Edge Types palettes) or that are inside a collapsed container. It does not matter whether a node or edge is outside the area currently shown in the window, i.e., just scrolled away. Such elements are still considered visible.

Mark¶

Mark selection Diagram.Mark.MarkSelection: Marks all selected elements.
Mark by query… Mark.MarkByQuery: Opens a Query dialog to mark nodes by their properties, see Section Query-based operations.
Mark all in view Diagram.Mark.MarkAllInView: Marks all elements in the current view only.
Mark all in graph Mark.MarkAllInGraph: Marks all elements in the entire graph.
Unmark nodes Mark.UnmarkNodes: Unmarks all nodes.
Unmark edges Mark.UnmarkEdges: Unmarks all edges.
Unmark by query… Mark.UnmarkByQuery: Opens a Query dialog to unmark nodes by their properties, see Section Query-based operations.
Unmark all Mark.UnmarkAll: Unmarks all nodes and edges in the entire graph, leaving the marking completely empty.
Clip marking to view Diagram.Mark.ClipMarkingToView: Leaves only elements marked that are present in the current view.
Clip marking to visible Diagram.Mark.ClipMarkingToVisible: Leaves only elements marked that are visible in the current window, i. e., unmarks nodes and edges that are currently hidden (see Section Hiding Elements), that have a type that is currently hidden (see Section The Node and Edge Types palettes) or that are inside a collapsed container. It does not matter whether a node or edge is outside the area currently shown in the window, i.e., just scrolled away. Such elements are still considered visible.

Hide and show¶

Hide node/edge: Hides the node/edge over which the context menu was opened.
Hide selection Graph.Hide.HideSelection: Hides all selected elements.
Hide by query… Graph.Hide.HideByQuery: Opens a Query window (see Section Query-based operations) to define the set of elements to be hidden.
Unhide selection Graph.Hide.UnhideSelection: Causes all selected elements that were previously hidden by a “Hide” operation to reappear. Some selected elements may still remain hidden if they are hidden due to other reasons, e. g., because they have a type that is dynamically hidden (see Section The Node and Edge Types palettes).
Unhide by query… Graph.Hide.UnhideByQuery: Opens a Query window (see Section Query-based operations) to define the set of elements to be unhidden.
Unhide all Graph.Hide.UnhideAll: Causes all nodes and edges that were previously hidden by a “Hide” operation to reappear. Some elements may still remain hidden if they are hidden due to other reasons, e. g., because they have a type that is dynamically hidden (see Section The Node and Edge Types palettes).
Add selection to diagram Graph.Hide.AddSelectionToDiagram: Only available in subset windows: Adds the selected nodes and edges to the set of elements shown in the subset window.
Remove selection from diagram Graph.Hide.RemoveSelectionFromDiagram: Only available in subset windows: Removes the selected nodes and edges from the set of elements shown in the subset window.

Visualization¶

Shrink node to fit: Only available when clicking into the expanded area of a node. Shrinks the expanded size of the node so it just encloses the children (with a small extra margin).
Shrink node to fit (deep): This works like Shrink node to fit, but it shrinks all expanded children first (recursively) to allow the node to shrink even more.
Remove overlaps Visualization.RemoveOverlaps: This operates on the area over which the menu was opened, either the graph background (top-level) or the expanded area of a node. Within this area, it pushes nodes away that overlap with other nodes, so the overlaps are removed.
Remove overlaps (deep) Visualization.RecursiveRemoveOverlaps: This works like Remove overlaps, but removes overlaps inside any expanded children first (recursively), so invoking this at the top level removes overlaps at all nesting levels of the graph.
Position and size…: Only shown if the clicked element is a node. Opens a dialog that allows the position and size of the node to be set numerically. Only allows the size to be edited for expanded nodes. See Expanded area size.
Node symbol size… Visualization.NodeSymbolSize: Opens a dialog that allows the size of the node symbols to be set in pixels. The given size is a global setting for the diagram/layout. It is used for top-level nodes. Nested nodes are shown with smaller symbols. The node symbol size is stored in saved layouts. The Default button in the dialog resets the size to the default used for new layouts.
Base font size…: This entry is only available for notes (or any other kind of node that displays text in the middle of its expanded area). It opens a dialog that allows you to set the base font size used to display textual content. In the case of HTML content the font size you enter is used as the base font size for body text. Other elements like headings can have different sizes that are derived from the base font size. The base font size is stored in saved layouts.
Node color…: Only shown if the clicked element is a node or an expanded node background. Opens a dialog that allows the expanded background color for that individual node to be overridden. See Expanded area color.
Put node to back: Only shown if the clicked element is a node. Moves the clicked node to the back in stacking order.
Focus on node: Only shown if the clicked element is a node. Makes the clicked node and its environment stand out from the crowd by showing all other nodes dimmed.
Focus on source node: Only shown if the clicked element is an edge. Makes the source node of the clicked edge and its environment (attached edges and neighboring nodes) stand out from the crowd by showing all other nodes dimmed. Also scrolls the source node into view if necessary.
Focus on target node: Only shown if the clicked element is an edge. Makes the target node of the clicked edge and its environment (attached edges and neighboring nodes) stand out from the crowd by showing all other nodes dimmed. Also scrolls the target node into view if necessary.
Focus on selection Visualization.FocusOnSelection: Makes the selection and its environment (attached edges and neighboring nodes) stand out from the crowd by showing all other nodes dimmed.
Stop focus Visualization.StopFocus: Cancels a running focus operation and restores the visual appearance of all elements to normal.
Expand to show selected Visualization.ExpandToShowSelected: In a hierarchical window, this expands the required nodes to make all selected elements visible.
Expand selected nodes Visualization.ExpandSelectedNodes: In a hierarchical window, this expands all visible selected nodes. If you want to expand invisible selected nodes, too, use Expand to show selected first.
Collapse selected nodes Visualization.CollapseSelectedNodes: In a hierarchical window, this collapses all visible selected nodes. If you want to collapse invisible selected nodes, too, use Expand to show selected first.
Expand to show marked Visualization.ExpandToShowMarked: In a hierarchical window, this expands the required nodes to make all marked elements visible.
Expand marked nodes Visualization.ExpandMarkedNodes: In a hierarchical window, this expands all visible marked nodes. If you want to expand invisible marked nodes, too, use Expand to show marked first.
Collapse marked nodes Visualization.CollapseMarkedNodes: In a hierarchical window, this collapses all visible marked nodes. If you want to collapse invisible marked nodes, too, use Expand to show marked first.
Mute edges Visualization.MuteEdges: Shows all edges in gray instead of the type-specific colors to improve clarity.
Semi-transparent edges Visualization.TransparentEdges: Makes all edges semi-transparent to improve clarity.
Edges behind nodes Visualization.EdgesBehindNodes: Displays edges behind nodes to improve clarity. Mostly useful for large flat windows. In hierarchical windows, this causes edges to/from nodes inside expanded parent nodes to be shown behind the expanded parent area, which makes it difficult to find the endpoints of such edges.
Show lifted edges Visualization.ShowLiftedEdges: Shows lifted summary edges (see Section Summary Edges (“Lifting”)), if available in this view. If unticked, lifted edges are not shown.
Semi-transparent node backgrounds Visualization.TransparentBackgrounds: Makes expanded node backgrounds semi-transparent, so it is easier to see whether other nodes are hidden underneath.
Show node names Visualization.ShowNodeNames: If ticked, displays the name of each node (its Source.Name attribute) underneath the node symbol.
Show edge labels Visualization.ShowEdgeLabels: If ticked, displays labels next to edges depending on the configuration.
Show attributes Visualization.ShowAttributes: If ticked, displays icons for various boolean attributes, e.g., Element.Is_Static overlaid over node symbols.
Edge bundling… Visualization.EdgeBundling: Opens a dialog to set the edge bundling threshold and to enable/disabling edge bundling, see Multiple Edges and Edge Bundling.

Zoom¶

Zoom to 100% Zoom.ZoomTo100: Sets the zoom factor to 100%.
Zoom to visible graph Zoom.ZoomToGraph: Adjusts the zoom factor and scroll bars to show the whole visible graph in the window.
Zoom to selection Zoom.ZoomToSelection: Adjusts the zoom factor and scroll bars to show all visible selected elements in the window.
Zoom to marking Zoom.ZoomToMarking: Adjusts the zoom factor and scroll bars to show all visible marked elements in the window.
Zoom in Zoom.ZoomIn: Increases the zoom factor.
Zoom out Zoom.ZoomOut: Decreases the zoom factor.

Layout operations¶

Layout operations change the positioning of nodes in the window. The operations in the Stretch and tighten, Flip and Rotate menus adjust the existing layout, the remaining operations arrange all nodes from scratch.

Stretch and tighten

Move nodes closer together or space them out.

Stretch XY Graph.Layout.StretchXY: Spaces out nodes more generously both horizontally and vertically.
Tighten XY Graph.Layout.TightenXY: Moves nodes closer together both horizontally and vertically.
Stretch X Graph.Layout.StretchX: Spaces out nodes more generously in horizontal direction.
Stretch Y Graph.Layout.StretchY: Spaces out nodes more generously in vertical direction.
Tighten X Graph.Layout.TightenX: Moves nodes closer together in horizontal direction.
Tighten Y Graph.Layout.TightenY: Moves nodes closer together in vertical direction.

Flip

Reflect (mirror) node positions.

Flip X Graph.Layout.FlipHorizontally: Reflects node positions horizontally.
Flip Y Graph.Layout.FlipVertically: Reflects node positions vertically.

Rotate

Rotate node positions.

Tilt left Graph.Layout.TiltLeft: Rotates the displayed nodes slightly in counter-clockwise direction. This is useful if many node labels overlap due to nodes being in a row next to each other, e.g., after a Grid or Sugiyama layout. Tilting the nodes (in either direction) removes those overlaps.
Tilt right Graph.Layout.TiltRight: As the previous entry, but the rotation is in clockwise direction.
Rotate left Graph.Layout.RotateLeft: Rotates by 90 degrees in counter-clockwise direction
Rotate right Graph.Layout.RotateRight: Rotates by 90 degrees in clockwise direction
Rotate by… Graph.Layout.RotateBy: Opens a dialog into which an arbitrary angle of rotation can be entered.

Simple

Simple layouts

Grid Graph.Layout.Grid: Arranges the nodes in a rectangular grid.
Connected grid Graph.Layout.ConnectedGrid: The connected components are arranged side by side, each as a column, sorted by component size, largest first.
Step Graph.Layout.Step: Similar to Grid, but places each node in a row slightly lower than its left neighbor.
Sawtooth Graph.Layout.Sawtooth: Similar to Grid, but moves every other node slightly down. This alternating vertical positioning gives more space to node labels.
Vertical lineup Graph.Layout.VerticalLineup: Place all nodes in a vertical line (column).
Horizontal lineup Graph.Layout.HorizontalLineup: Place all nodes in a horizontal line (row).
Horizontal sawtooth Graph.Layout.HorizontalSawtooth: As Horizontal lineup, but moves every other node slightly down. This alternating vertical positioning gives more space to node labels.
Circular Graph.Layout.Circular: Arranges all nodes in a circle outline.
Circular filled Graph.Layout.CircularFilled: Arranges all nodes in a filled circle.

Tree and DAG

Layouts that are best suited for acyclic graphs.

Context sensitive Graph.Layout.ContextSensitive: Chooses a layout depending on the structure of the displayed nodes and edges and applies it. This is the default layout applied to newly expanded nodes.
Sugiyama Graph.Layout.Sugiyama: Applies a tree layout. Chooses a root node and then displays each level of the graph as a row.

Spring

Layouts that are based on physics simulations representing edges as springs.

Spring-electrical Graph.Layout.SpringElectrical

An iterative layout approach that simulates a setup in which nodes repel each other like particles with the same electrical charge and edges act as springs that pull their endpoints together.

In contrast to most other layouts, Spring-electrical is sensitive to the existing layout it finds, so the results can be improved by changing node positions and running the layout again, e. g., if some nodes have become tied in a knot. Similarly, if Spring-electrical gives up due to running out of time while the layout still looks unfinished, you can simply run the operation again to improve it.

Components

Layouts that treat whole connected components as atomic units and lay them out. These are useful for post-processing the results of Sugiyama, Spring-electrical or Connected grid, which simply arrange the connected components they find side by side.

Component grid 8:9 Graph.Layout.ComponentGrid89: Moves connected components around in such a way that the resulting aspect ratio of the diagram is as close to 8:9 as possible.
Component grid 4:3 Graph.Layout.ComponentGrid43: As above, but tries to achieve a 4:3 ratio.
Component grid 16:9 Graph.Layout.ComponentGrid169: As above, but tries to achieve a 16:9 ratio.

Selection layout¶

As Layout operations, but the chosen layout is applied to the selected nodes only. Most layouts that rearrange all nodes attempt to reuse the existing area covered by the nodes as closely as possible. So, if the nodes were arranged in a wide rectangle, applying a Circular layout results in a wide ellipse. If this is not intended, then the target area can be extended by moving one of the selected nodes to increase the area covered by the selected nodes before invoking the operation.

The operations names for the operations on the Selection layout menu are derived from those on the Layout operations menu by appending Selection to the name, e. g., Graph.Layout.GridSelection for Layout selection → Simple → Grid.

Layout Storage¶

Update layout ’layout name’ Graph.LayoutStorage.UpdatePersistentLayout: Updates the saved layout from the current state of the window. Only shown if the current window has a persistent layout applied.
Revert layout ’layout name’ Graph.LayoutStorage.RevertPersistentLayout: Reverts the layout from the most recently saved state, i.e., discards all changes since the layout was updated. Only shown if the current window has a persistent layout applied.
Apply/Switch layout: Offers a submenu of persistent layouts that can be applied (called “Switch” if the current graph window has a persistent layout already, else “Apply”). Layouts that have not been saved yet or that are already open are shown grayed out on the submenu.
Create new layout… Graph.LayoutStorage.CreatePersistentLayout: Creates a new persistent layout based on the current state of the window. Opens a window in which you can enter the name for the new layout. The new layout then becomes the one that is currently edited in the window.
Export layout… Graph.LayoutStorage.ExportLayout: Saves the layout of the current window to a file that can be loaded in a future session to restore the current layout. Node positions are not stored in the RFG, so saving and loading the layout is the only way to preserve the currently shown layout of the view for future use. You can use persistent layouts to simplify the task of managing your layout files.
Import layout… Graph.LayoutStorage.ImportLayout: Loads a previously stored layout and applies it to the window. Nodes are matched by name ( Linkage.Name, if present, else Source.Name), so this will not have much of an effect if the layout was saved for a different view or even a different graph. It is also expected that the node hierarchy matches that of the view for which the layout was saved. Nodes that are not inside the same parent as when the layout was saved will not be moved.
Import recent: Leads to a submenu listing recently exported/imported layout files for quick access. The status bar shows the full path of the file while the pointer is over an entry.
Save layout as PNG… Graph.LayoutStorage.SaveAsPNG: Saves the currently shown layout as a bitmap file using the current zoom factor.
Save layout as PDF… Graph.LayoutStorage.SaveAsPDF: Saves the currently shown layout as a scalable vector PDF file. This always saves the representation at 100% scaling, irrespective of the current zoom factor.
Save layout as SVG… Graph.LayoutStorage.SaveAsSVG: Saves the currently shown layout as a scalable vector graphics file in SVG format. This always saves the representation at 100% scaling, irrespective of the current zoom factor.

Run Python script…¶

Runs a Python script on the current window. The script has access to the view shown in the window and the graph element (node or edge) over which the context menu was opened. If the menu was opened over a node, the script has access to its graphical representation and it can check whether the click was over the node symbol or the node’s expanded background.

Operation name: File.RunPythonScript

Run recent script¶

Shows a list of the most recently run Python scripts for easy access. The selected script is run on the current window as described above.

5.9.8.5. Context Menu in Tree Windows¶

Open¶

Node information…: Open a Node Information window for the clicked node.
Show source code…: Open a source code window for the clicked node.

Edit¶

Rename…: Renames the clicked node, i. e. changes the value of attribute Source.Name.
Delete node: Deletes the clicked node from the view. All attached edges are deleted as well.
Delete selection (Diagram.Edit.DeleteSelection): Deletes the selected elements from the view. All attached edges are deleted as well.

Mapping¶

This entry is only shown if the current window is a Mapping window. It is the same as the Mapping submenu of graphical windows, see Section Mapping.

Select¶

Same as the Select submenu of graphical windows, see Section Select.

Mark¶

Same as the Mark submenu of graphical windows, see Section Mark.

Visualization¶

Expand to show selected Visualization.ExpandToShowSelected: Expands nodes so that all selected nodes are visible.
Expand selected nodes Visualization.ExpandSelectedNodes: Expands all visible selected nodes. If you want to expand invisible selected nodes, too, use Expand to show selected first.
Collapse selected nodes Visualization.CollapseSelectedNodes: Collapses all visible selected nodes. If you want to collapse invisible selected nodes, too, use Expand to show selected first.
Expand to show marked Visualization.ExpandToShowMarked: Expands nodes so that all marked nodes are visible.
Expand marked nodes Visualization.ExpandMarkedNodes: Expands all visible marked nodes. If you want to expand invisible marked nodes, too, use Expand to show marked first.
Collapse marked nodes Visualization.CollapseMarkedNodes: Collapses all visible marked nodes. If you want to collapse invisible marked nodes, too, use Expand to show marked first.
Expand all Visualization.ExpandAll: Expands all nodes.
Collapse all Visualization.CollapseAll: Collapses all nodes.
Case sensitive comparison Visualization.CaseSensitiveComparison: Sorts nodes case sensitively.
Group by node type Visualization.GroupByType: Groups nodes by their type first before sorting by name.

5.9.8.6. Context Menu in the Violations/Conformances List¶

The context menu over an entry in the Violations or Conformances List (see Section The Violations List) created by Architecture Analysis (see Section Performing Architecture Analysis) is sensitive to the column in which the click happened: If it happened over a column showing a node, then the following operations are available:

’<Node name>’ node information…: Opens the Node Information window (see Section The Node Information Window) for the clicked node.
’<Node name>’ source code…: Opens the source code window (see Section Source Code Windows) for the clicked node.
Mark node ’<Node name>’: Marks the given node.

The following entries refer to the causing edge of the violation/conformance and are available independent of the column over which the click happened:

Mark architecture elements: Marks the elements in the architecture that are involved with this violation/conformance, i. e., the two architecture component nodes and the Divergence/Convergence/Absence edge between them.
Mark causing elements: Marks the source code elements that are involved with this violation/conformance, i. e., the causing edge and its endpoints.
Mark architecture and causing elements: Marks both architecture elements and causing elements as described above.
Causing edge information…: Opens the Edge Information window (see Section The Edge Information Window) for the causing edge.
Causing edge source code…: Opens the source code window (see Section Source Code Windows) for the causing edge. This shows the source position at which the violation/conformance happened, e.g., the location of a routine call that violates (or conforms to) the architecture.
Run Python script… File.RunPythonScript: Runs a Python script on the current window. The script has access to the view shown in the window and the graph element over which the context menu was opened. This is always the causing edge shown in the clicked row, independent of the clicked column (even if the click was in a column showing a node).
Run recent script: Shows a list of the most recently run Python scripts for easy access. The selected script is run on the current window as described above.
Export as CSV…: Exports the violations and/or conformances associated with the view as a CSV file (using semicolons as field separators, suitable for importing into spreadsheet software on a German system) including an initial row of column headers.

Caution

This exports the results as computed by Architecture Analysis, not just the results shown in the window. After computing both conformances and violations, both kinds are exported, even if only the one or the other kind is shown in the window.

5.9.8.7. Adding Scripts to Menus, Shortcuts and Events¶

Python scripts can be added as new entries to 27 different Gravis menus and submenus and/or associated with a keyboard shortcut or an event like the creation of a node by the user. To add a script to Gravis, it needs to be placed in a directory named gravis_scripts somewhere in the configuration hierarchy, i. e., in a directory listed in BAUHAUS_CONFIG or the directory .bauhaus in the user’s home directory. The script files need to have a .py extension.

The comment header of the script specifies the target menu(s), the menu label to display, an optional icon, and an optional status line help message (for fixed menus only, not for context menus). The comment header contains key/value pairs separated by colons. The keys are case insensitive, leading and trailing white space is ignored. The first non-empty non-comment line terminates the header.

This is an example of a valid comment header:

# Menu label: Select all functions
# Menu help: Selects all function nodes in the current view
# Menu icon: select\_all\_functions.png
# Menu contexts: Diagram.Select, View.Select

The key Menu label defines the label to show on the menu entry. If there is a Menu icon entry, it defines the filename of the icon to show next to the label. If this key is present, then a file of the given name must be located in the same directory as the script. The icons can be in PNG or SVG format (with .png and .svg extensions respectively).

The key Menu contexts is obligatory. It contains a list of contexts in which this menu entry appears. These contexts are essentially menu names. Almost all Gravis menus can accommodate extra scripted menu entries.

Valid values for Menu contexts are:

Context	Gravis menu
`File`, `Edit`, `Window`, `Help`	main menus
`View`	context menu over `View Box`
`View.Open`, `View.Edit`, `View.Select`, `View.Mark`	submenus of the above
`Diagram`	context menu over graphical or tree windows
`Diagram.Open`, `Diagram.Edit`, `Diagram.Select`, `Diagram.Mark`, `Diagram.Visualization`	submenus of the above
`Graph`	context menu over graphical window
`Graph.Open`, `Graph.Edit`, `Graph.Select`, `Graph.Mark`, `Graph.Visualization`, `Graph.Hide`, `Graph.Zoom`, `Graph.Layouts`, `Graph.Selection layout`, `Graph.Layout storage`	submenus of the above
`Tree`	context menu over tree windows
`Tree.Open`, `Tree.Edit`, `Tree.Select`, `Tree.Mark`, `Tree.Visualization`	submenus of the above
`Edge List`	context menu over edge list windows
`Analysis Results List`	context menu over an edge list window showing the results of architecture analysis

The Diagram contexts represent the context menus of windows showing graph elements, i. e., graphical windows, tree windows and edge list windows (including analysis result windows), so Diagram is a shortcut for Graph, Tree, Edge List. Edge list windows (including analysis result windows) are special in that they do not have any submenus, so they do not support the submenu contexts. Therefore, Diagram.Select is a shortcut just for Graph.Select, Tree.Select.

Invoking scripts via keyboard shortcuts and events¶

The two special context types Key:<Shortcut> and Event:<Name> can be used instead of – or in addition to – the menu contexts described above.

Key:<Shortcut> defines a global keyboard shortcut for the script. The syntax corresponds to the shortcut names shown in the menus, e. g., Ctrl+X, Shift+F2, etc. When invoked via a shortcut the script behaves as if invoked from the active diagram, if there is one, so both get_primary_view() and get_clicked_view() return the diagram’s view and diagram-specific calls like layout operations work. If the current window is a mapping viewer or not a diagram window at all, the script behaves as if run from a global context, i.e., get_clicked_view() returns None.

Event:<Name> associates the script with a named event. Supported events are: ArchitectureAnalysisComplete, ArchitectureAnalysisStarting(7.0.1), EdgeCreated, GraphCreated, GraphicalDiagramOpened(7.0.1), GraphLoaded(7.0.1), NodeCreated, OpeningMappingDialog(7.0.1), ViewCreated.

The GraphCreated event is triggered when a new empty graph is created by the user. It behaves as if invoked from the context menu over the empty View Box.

The GraphLoaded event is triggered when a graph or view file is opened by the user. It behaves as if invoked from the context menu over empty space in the View Box.

The ViewCreated event is triggered when a new empty view is created by the user. It behaves as if invoked from the context menu over the newly created view in the View Box, so get_clicked_view() returns the new view.

The GraphicalDiagramOpened event is triggered after a graphical diagram was opened by the user. The script behaves as if invoked from the context menu over the newly created graphical diagram. This event is also triggered for a graphical architecture diagram in a mapping dialog and for a graphical result view opened by architecture analysis.

The Node/EdgeCreated events are triggered when a node or an edge is created by the user in a graphical window. The script behaves as if invoked from the context menu over the newly created object, so the created object can be retrieved via get_clicked_node() (or get_clicked_edge() respectively), and get_clicked_view() returns the view in which it was created.

The event OpeningMappingDialog is triggered just before the mapping dialog is opened by the user. It behaves as if invoked from the context menu over empty space in the View Box.

The event ArchitectureAnalysisStarting is triggered just before architecture analysis is run by the user. The script is called before the mapping view is validated, so the mapping can be enhanced by the script. It behaves as if invoked from the context menu over the architecture view in the View Box, so get_clicked_view() returns the architecture view about to be checked.

The event ArchitectureAnalysisComplete is triggered after architecture analysis was run by the user. The script behaves as if invoked from the context menu over the result window. If both a result list and a graphical result view were opened, the result window is the graphical result view. If no result window was opened, the script behaves as if invoked from the context menu over the result view in the View Box. In all these cases, get_clicked_view() returns the analysis result view. get_script_context() returns Window if there is a result window, else View. In the Window case get_graphical_root() can be used to check for a graphical window.

5.9.9. Customizing Gravis¶

Many aspects of the way in which Gravis operates can be adapted and enhanced via the Gravis configuration. You can find the Gravis rule with various options in the Tools aspect in the graphical configuration interface.

Note

Configuration changes only come into effect after quitting and restarting Gravis.

5.9.9.1. Visualization options¶

The way Gravis displays graphical diagrams is controlled by the graph_style option in the Gravis rule. For instance, you can set the background color of graph windows (default: white) via the option graph_style.background_color. By default, node and edge labels are shown in black, but this can be changed via the option graph_style.default_label_color. You can define the colors and shapes of nodes via graph_style.node_types and the color, thickness, dash pattern and arrow types/sizes of edges via graph_style.edge_types. Both are dictionaries that map node/edge type names to a hierarchy of structured settings. You can leave any of the child settings at None (unspecified), which makes the given type inherit this property from its parent in the type hierarchy as shown in the Gravis Node/Edge Type panels.

By default, most settings of most types are None (unspecified). That allows you to set properties for whole subtrees of the type hierarchy. For instance, if you set Source_Dependency.width to 2.0 in graph_style.edge_types, then all edge types in the subtree of Source_Dependency, e.g., Static_Call and Variable_Use are shown 2 pixels wide. You can still override the width of individual types by setting a specific value there.

Custom Node and Edge Types¶

The graph_style.node_types and graph_style.edge_types dictionaries contain entries for all predefined node and edge types. In addition to editing these entries, you can add new entries for any custom node and edge types you want to use by clicking on the New entry... button in the node/edge_types edit dialog and entering the name of your custom type. After restarting Gravis, if a loaded graph contains a node/edge type of the given name or a type of that name is created in the graph, the settings of this entry are used to visualize it.

If a graph contains node/edge types that are not mentioned in the graph_style.node/edge_types dictionaries, their visualization settings are inherited from their parents in the type hierarchy and the __default__ entry as the implicit parent of all top-level types.

Adding SVG Icons¶

Gravis defines a set of predefined node shapes. In addition, you can use any SVG graphic as a node shape for existing node types or custom node types. The shapes sub-option of the entries in the graph_style.node_types dictionary accept either the name of a predefined node shape or the filename of an SVG file (as an absolute path or relative to the directory containing the configuration file).

Configuring an SVG shape in the GUI. — Using the graphical configuration interface to configure a custom node type to use an SVG icon.¶

The size and position of the icon in the SVG file is not important. Gravis scales it to make its size match that of the predefined node shapes.

Adding custom icons without configuration changes (legacy mechanism)¶

Gravis has a legacy mechanism to look for custom icons for node types that have no shape configuration in node_types, either because they do not appear in the dictionary or because their shape option is set to None. It looks for files with a .svg extension in the directory custom_icons inside any configuration layer, i. e., inside any directory listed in BAUHAUS_CONFIG or inside the directory .bauhaus in the user’s home directory. The found files are associated with node types using their names, so the file $(HOME)/.bauhaus/custom_icons/MyType.svg is used for nodes of type MyType (and its subtypes in the type hierarchy as long as they have no explicit shape configuration). This mechanism is deprecated and may be removed in a future version of Gravis.

Node and Edge Labels¶

Gravis can show labels at the top and bottom of nodes and at six different positions around edges: at the top and bottom near the source node, at the top and bottom in the middle of the edge, and at the top and bottom near the target node. For each node/edge type, each of these two/six positions can show nothing, a fixed string or a string that depends on the presence and contents of an attribute. For instance, the option label_top in the Routine entry of graph_style.node_types controls which label is shown at the top of Routine nodes (or any sub-types of Routine, for which this key is not explicitly overridden). The option label_middle_top in the UML Relation entry in graph_style.edge_types controls which label is shown above UML Relation edges in the middle between the start and the end node.

The value of these label options is a label specification, which is either just the key of an attribute to display or a list of comma-separated key=value pairs that define various aspects of the label, including its display style. Comma and backslash characters in a value must be quoted with a backslash character. Available label specification keys are:

attr=name

Specifies the key of an attribute to display. If the attribute is not present, the default is shown, if the key default is specified, else no label is shown. For attributes other than boolean flags, the attribute value is shown, optionally, between prefix and suffix if these keys are specified. If the attribute is a boolean flag, the redundant value true is never shown, but instead only prefix is shown, which must be specified in this case, else nothing is shown at all.
bold=flag

Specifies whether the label should be shown in a bold font.
default=string

Specifies a string to be shown if the specified attribute is not set. If no attr key is specified, the default string is always shown.
italic=flag

Specifies whether the label should be shown in an italic font.
size=+/-number

Specifies the relative font size to be used. A positive value makes the label appear larger than the default label font size, a negative values makes it appear smaller. The increment/decrement is measured in points.
prefix=string

Specifies a string to be shown before the attribute value. Only shown if the attribute is set. Optional, except when attr refers to a boolean flag attribute, in which case this key is required.
suffix=string

Specifies a string to be shown after the attribute value. Only shown if the attribute is set. Not shown for boolean flag attributes.

Either attr or default must be present for a label setting to have any effect at all.

Example label specifications:¶

attr=UML.Stereotypes,bold=true,size=-1

shows the contents of the attribute UML.Stereotypes in a bold font and 1pt smaller than the normal label font size, or nothing if the attribute is not set.
attr=Metric.Lines.LOC,prefix=LOC=,default=(no LOC)

shows the contents of the integer attribute Metric.Lines.LOC prefixed by LOC=, or (no LOC) if the attribute is not set.
default=Association,italic=true

shows the label Association in an italic font unconditionally for each node/edge type for which this label is configured.
attr=Element.Is_Optional,prefix=optional

shows optional if Element.Is_Optional is set, else nothing.
attr=Element.Is_Optional,prefix=optional,default=mandatory

shows optional if Element.Is_Optional is set, else mandatory.

5.9.9.2. Keyboard shortcuts¶

Gravis offers keyboard shortcuts for many menu entries. If there is a shortcut for a menu entry it is shown next to it. It is possible to change the existing shortcuts and to assign shortcuts to most of the menu operations that do not yet offer a shortcut.

To add or change keyboard shortcuts add a file named gravis_shortcuts.txt to any configuration layer, i. e., either a directory listed in BAUHAUS_CONFIG or the directory .bauhaus in the user’s home directory. If there is more than one such file standard layering rules apply, so changes made in more local layers override those made in more global layers. The .bauhaus directory in the user’s home directory is considered the most local layer.

The gravis_shortcuts.txt file associates operation names with keyboard shortcuts, e. g.:

# my personal shortcuts
Graph.LayoutStorage.SaveAsPNG      Ctrl+F2
Graph.LayoutStorage.SaveAsPDF      Ctrl+F3     # next to "SaveAsPNG" on the keyboard
Diagram.Edit.DeleteSelection       # clear shortcut to avoid accidents

You can find the operation names in the menu reference section above.

Use any number of whitespace characters to separate the operation name from the shortcut. Shortcut are specified using English key names (Ctrl, Shift, etc.) independent of the computer’s locale settings. Leaving out the shortcut definition clears any existing shortcut for the given operation. Comments are introduced by a hash character and extend to the end of the current line.

If the same operation occurs more than once in a file the last change in the file wins.

The command clear on its own on a line clears all shortcuts assigned so far, allowing you to start setting up all shortcuts from from scratch. That can be useful to avoid conflicts between newly assigned shortcuts and predefined shortcuts.

Conditional blocks¶

It is possible to define platform-specific shortcuts using ifeq/else/endif constructs similar to GNU make:

ifeq ($(PLATFORM),Windows)
   File.Reload                            F5
else
   File.Reload                            Ctrl+R
endif

The else branch is optional. Use ifneq instead to test for inequality. Conditional constructs can be nested.

$(PLATFORM) is a pseudo-variable that resolves to Windows, Linux or macOS depending on the current platform. Any other variable name is looked up as an environment variable. A non-existing environment variable expands to the empty string.

Conflict resolution¶

Each operation can only have a single shortcut, and each possible shortcut can only be assigned to a single operation. The first requirement is always satisfied: As described above later changes override earlier ones, so if the same operation appears more than once in a shortcuts file, the last change in the most local layer wins.

A similar logic is also true for shortcuts appearing more than once on the right hand side: If a shortcut that was already mentioned before is assigned to a different operation the association with the earlier operation is removed. Again, the last use in the most local layer wins. These conflicts are not very obvious so they result in a warning.

Conflict resolution also takes menu scripts into account that are bound to keyboard shortcuts (see Adding Scripts to Menus, Shortcuts and Events). Menu scripts are considered more local than shortcuts files, so if the same shortcut is assigned in a shortcuts file and in a menu script, the menu script wins, no matter in which layers the definitions are. This kind of conflict also results in a warning.

Additional operations¶

In addition to the operation names shown next to menu entries in this chapter there are the following non-menu operations that can be bound to keyboard shortcuts:

Diagram.RenameNode to rename the node under the pointer (default: F2)
Tools.Navigate (default: F3), Tools.Select (default: F4), Tools.Mark (default: F5), Tools.Node (default: F6), Tools.Edge (default: F7), Tools.Hierarchy (default: F8), Tools.Zoom (default: F9), Tools.Scroll (default: F10), Tools.Mapping (default: F11) to select a tool
Visualization.ToggleEdgeBundling to toggle the edge bundling visualization option (default: Ctrl+Shift+B)

5.9.10. Command-line parameters¶

Usage:

gravis [options] <input file(s)>

There can be at most one RFG input file (extension .rfg) and any number of GXL input files (extension .gxl). The RFG file, if specified, is loaded first, then the GXL files are imported into the loaded RFG. If no RFG file is specified but one or more GXL files, then the GXL files are imported into an empty RFG.

Options:

--script <script filename>: Runs the given Python script at startup (after loading input files).
--script-param <parameter>: Adds a parameter to be passed to the Python script (only useful in conjunction with --script).
--noscript: Disable Python scripting.
--quit: Causes Gravis to quit after startup (mainly useful in conjunction with --script), enables non-interactive mode.
--font <font name>: Specifies the font to be used in the user interface.
--font-size <font size>: Specifies the font size in pt to be used in the user interface (in conjunction with --font). 0 for system default.
--ignore_geometry: Prevents window position and size information stored during the previous session from being loaded. Useful if the information has become corrupted and causes the window to be opened off-screen.
--basepath <path>: Specifies the base path used for source code lookup.
--no_platform_override: Do not override the platform to offscreen for non-interactive Linux/macOS use.
--no_translate: Prevents translation files from being loaded and forces the English UI to be shown.
--translate <locale>: Overrides the system locale for finding translation files. If this option is not specified, the locale name is read from the environment variable AXIVION_UI_LANGUAGE, and if that variable is not set, the system locale is used to determine the preferred UI language.

In addition to these options, the common options of Axivion Suite tools are supported (see Tool Reference).

5.9.8. Menu Reference¶

5.9.8.1. Main Menu¶

File menu¶

Edit menu¶

View menu¶

Window¶

Help¶

5.9.8.2. Context Menu in the View Box¶

Layout¶

Open¶

Edit views¶

Select¶

Mark¶

Set role¶

Export as GXL…¶

Run Python script…¶

Run recent script¶

5.9.8.3. Context Menu over tabs¶

5.9.8.4. Context Menu in Graph Windows¶

Open¶

Edit¶

Mapping¶

Select¶

Mark¶

Hide and show¶

Visualization¶

Zoom¶

Layout operations¶

Selection layout¶

Layout Storage¶

Run Python script…¶

Run recent script¶

5.9.8.5. Context Menu in Tree Windows¶

Open¶

Edit¶

Mapping¶

Select¶

Mark¶

Visualization¶

5.9.8.6. Context Menu in the Violations/Conformances List¶

5.9.8.7. Adding Scripts to Menus, Shortcuts and Events¶

Invoking scripts via keyboard shortcuts and events¶

5.9.9. Customizing Gravis¶

5.9.9.1. Visualization options¶

Custom Node and Edge Types¶

Adding SVG Icons¶

Adding custom icons without configuration changes (legacy mechanism)¶

Node and Edge Labels¶

Example label specifications:¶

5.9.9.2. Keyboard shortcuts¶

Conditional blocks¶

Conflict resolution¶

Additional operations¶

5.9.10. Command-line parameters¶