WorkspaceManager_Cmd-ConfigureConfigure_AD

Applied Parameters: ObjectKind=MessageView|Action=GroupByNone

Summary

This command is used to turn off grouping in the Messages panel.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Group By » None command from the context menu.

Use

After launching the command, message grouping will be turned off in the Messages panel, resulting in a flat listing of all messages.

Applied Parameters: ObjectKind=MessageView|Action=GroupBySource

Summary

This command is used to group messages by their Source, in the Messages panel.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Group By » Source command from the context menu.

Use

After launching the command, messages in the Messages panel will be grouped by their Source. The source of a message is the server or engine that performed the task when the catalyst for a message was encountered (e.g. the Compiler).

Applied Parameters: ObjectKind=MessageView|Action=GroupByClass

Summary

This command is used to group messages by their Class, in the Messages panel.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Group By » Class command from the context menu.

Use

After launching the command, messages in the Messages panel will be grouped by their Class. The class of message depends on the source of the message - the server or engine that performed the task when the catalyst for a message was encountered (e.g. the Compiler). For example, classes of message from the Compiler can include Warning, Error, and Fatal Error, while classes of message from the Situs Autorouter include Routing Status and Situs Event.

Applied Parameters: ObjectKind=MessageView|Action=GroupByDocument

Summary

This command is used to group messages by their Document, in the Messages panel.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Group By » Document command from the context menu.

Use

After launching the command, messages in the Messages panel will be grouped by their Document - this is the source document for which the message has been generated. This could be, for example, a source schematic sheet on which a primitive has been detected by the Compiler to be causing a logical violation. Or perhaps the PCB document, upon which autorouting is currently in progress, with messages coming in from the Situs Autorouter with respect to events and routing status.

Applied Parameters: ObjectKind=MessageView|Action=CrossProbe

Summary

This command is used to cross-probe (where possible) from the selected message in the Messages panel, to the object responsible for the message in the associated document.

Access

This command is accessed from the Messages panel by right-clicking on the entry for the message of interest, and choosing the Cross Probe command from the context menu.

Use

First, ensure that the cursor is above the message that you wish to cross-probe, in the Messages panel.

After launching the command, you will be taken directly to the object on the associated document. The following scenarios illustrate examples of cross-probing behavior within a PCB project:

• Scenario 1- running a DRC on your PCB design document may create violation messages with the Source field entry of Advanced PCB. Launching this command will cross-probe directly to the offending object on the document.
• Scenario 2 - compiling the source schematic documents of a PCB project may create violation messages with the Source field entry of Compiler. Launching the command from such a message will cross-probe directly to the offending object(s) on the relevant document in the main design window.

Tips

1. Double-clicking on an a message in the Messages panel will also perform a cross-probe.
2. When cross-probing to a PCB document, ensure that the relevant PCB document is the active document in the design window, otherwise cross-probing will occur, but you will not jump to the document. The offending object(s) will be automatically zoomed and centered (where possible) in the design window, but no other highlighting (filtering/masking/dimming) will be applied.
3. When cross-probing to a schematic document:
   1. The document will be made active if it is not already, or unhidden and made active if it was previously in hidden mode.
   2. The visual display of a cross-probed object on a schematic document in the main design workspace, is dependant on the highlighting options defined on the System - Navigation page of the Preferences dialog. These options include zooming, selecting and masking, the latter of which causes all other objects on the document to become dimmed, leaving only the offending object fully visible.
   3. The filtering applied when cross-probing from the Messages panel is temporary. Clicking within the design workspace will clear the filter. As such, you are not prevented from selecting or editing design objects that fall outside the scope of the filter.
   4. The extent of 'dimming' applied when the masking highlight option is enabled can be manually adjusted using the Dim slider bar - accessed by clicking the Mask Level button, at the bottom-right of the main design window.
4. For a Compiler-generated message, more information regarding the object(s) involved in the violation can be seen in the Details region of the Messages panel. Cross-probing to an offending object can also be performed from there.

Applied Parameters: ObjectKind=MessageView|Action=CrossProbeNext

Summary

This command is used to move to the next message (down) in the Messages panel, and if the message supports cross-probing functionality, will cross-probe to the object responsible for the message in the associated document.

Access

This command can be accessed by:

• Right-clicking on the currently selected message entry in the Messages panel, and choosing the Cross Probe Next Message command from the context menu.
• Using the Shift+Ctrl+F3 keyboard shortcut.

Use

After launching the command, the message immediately below the currently selected message - in the Messages panel - will become selected, and you will be taken directly to the object on the associated document (where cross-probing for that message is supported).

Tips

1. Double-clicking on an a message in the Messages panel will also perform a cross-probe.
2. When cross-probing to a PCB document, ensure that the relevant PCB document is the active document in the design window, otherwise cross-probing will occur, but you will not jump to the document. The offending object(s) will be automatically zoomed and centered (where possible) in the design window, but no other highlighting (filtering/masking/dimming) will be applied.
3. When cross-probing to a schematic document:
   1. The document will be made active if it is not already, or unhidden and made active if it was previously in hidden mode.
   2. The visual display of a cross-probed object on a schematic document in the main design workspace, is dependant on the highlighting options defined on the System - Navigation page of the Preferences dialog. These options include zooming, selecting and masking, the latter of which causes all other objects on the document to become dimmed, leaving only the offending object fully visible.
   3. The filtering applied when cross-probing from the Messages panel is temporary. Clicking within the design workspace will clear the filter. As such, you are not prevented from selecting or editing design objects that fall outside the scope of the filter.
   4. The extent of 'dimming' applied when the masking highlight option is enabled can be manually adjusted using the Dim slider bar - accessed by clicking the Mask Level button, at the bottom-right of the main design window.
4. For a Compiler-generated message, more information regarding the object(s) involved in the violation can be seen in the Details region of the Messages panel. Cross-probing to an offending object can also be performed from there.

Applied Parameters: ObjectKind=MessageView|Action=CrossProbePrevious

Summary

This command is used to move to the previous message (up) in the Messages panel, and if the message supports cross-probing functionality, will cross-probe to the object responsible for the message in the associated document.

Access

This command can be accessed by:

• Right-clicking on the currently selected message entry in the Messages panel, and choosing the Cross Probe Previous Message command from the context menu.
• Using the Shift+Ctrl+F4 keyboard shortcut.

Use

After launching the command, the message immediately above the currently selected message - in the Messages panel - will become selected, and you will be taken directly to the object on the associated document (where cross-probing for that message is supported).

Tips

1. Double-clicking on an a message in the Messages panel will also perform a cross-probe.
2. When cross-probing to a PCB document, ensure that the relevant PCB document is the active document in the design window, otherwise cross-probing will occur, but you will not jump to the document. The offending object(s) will be automatically zoomed and centered (where possible) in the design window, but no other highlighting (filtering/masking/dimming) will be applied.
3. When cross-probing to a schematic document:
   1. The document will be made active if it is not already, or unhidden and made active if it was previously in hidden mode.
   2. The visual display of a cross-probed object on a schematic document in the main design workspace, is dependant on the highlighting options defined on the System - Navigation page of the Preferences dialog. These options include zooming, selecting and masking, the latter of which causes all other objects on the document to become dimmed, leaving only the offending object fully visible.
   3. The filtering applied when cross-probing from the Messages panel is temporary. Clicking within the design workspace will clear the filter. As such, you are not prevented from selecting or editing design objects that fall outside the scope of the filter.
   4. The extent of 'dimming' applied when the masking highlight option is enabled can be manually adjusted using the Dim slider bar - accessed by clicking the Mask Level button, at the bottom-right of the main design window.
4. For a Compiler-generated message, more information regarding the object(s) involved in the violation can be seen in the Details region of the Messages panel. Cross-probing to an offending object can also be performed from there.

Applied Parameters: ObjectKind=MessageView|Action=MoreInfo

Summary

For a Compiler-generated message in the Messages panel - that flags a violation (warning, error, fatal error) associated with a Net in the design - this command is used to jump straight to the relevant point in the schematic - for the offending object - and place a Specific No ERC directive configured to suppress that warning/error. The No ERC object is a design directive that can operate in two modes. In this specific mode, the directive is configured to target and suppress the warning or error conditions causing the violation, while allowing any other warning or error to be detected and reported.

Access

This command is accessed from the Messages panel by right-clicking on the entry for the message of interest, and choosing the Place Specific No ERC for this violation command from the context menu.

Use

First, ensure that the cursor is positioned over the message for the violating object in the Messages panel.

After launching the command, a No ERC directive will appear floating on the cursor, pre-configured to suppress the violation(s). Simply position the cursor at the relevant point of the object, and click, or press Enter, to effect placement.

Additional actions that can be performed during placement – while the No ERC object is still floating on the cursor – are:

• Press the Tab key to access the No ERC dialog, from where properties for the No ERC object can be changed on-the-fly.
• Press the Spacebar to rotate the No ERC object anti-clockwise or Shift+Spacebar for clockwise rotation. Rotation is in steps of 90°.
• Press the X or Y keys to mirror the No ERC object along the X-axis or Y-axis respectively.

Tips

1. Rather than deleting a No ERC directive, it can be simply made inactive (disabled in the eyes of the Compiler). This state can changed by toggling the directive's Active property - either through the No ERC dialog, or on the SCH Inspector panel, or SCH List panel.
2. A Specific No ERC directive can be quickly switched to be a Generic No ERC directive, either through the No ERC dialog, or by toggling the Suppress Specific Violations property, on the SCH Inspector panel, or SCH List panel.
3. All No ERC directives - used across the entire project - can be reviewed and edited through the NoERC Manager dialog. From here, you can move through the list of nets with directives applied, and edit any number of No ERC directives. When editing is complete, changes are applied through an Engineering Change Order (ECO).
4. Suppressed violations can be displayed on the Messages panel by enabling the Report Suppressed Errors in Messages Panel option, on the Error Reporting tab of the Options for Project dialog. This feature can be used in the final stages of design to ensure that no critical errors have been inadvertently suppressed.
5. By default, all design directives are included during printing. To control this, disable directives that you do not want included on your printouts in the Schematic Print Properties dialog.
6. While attributes can be modified during placement (Tab to bring up associated properties dialog), bear in mind that these will become the default settings for further placement unless the Permanent option on the Schematic – Default Primitives page of the Preferences dialog is enabled. When this option is enabled, changes made will affect only the object being placed and subsequent objects placed during the same placement session.

Applied Parameters: ObjectKind=MessageView|Action=ClearAll

Summary

This command is used to clear all messages that are currently displayed in the Messages panel.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Clear All command from the context menu.

Use

After launching the command, all messages in the Messages panel will be cleared.

Tips

1. Clearing messages does not necessarily mean the messages have been resolved. The same unresolved messages will be listed after performing the same command that led to the messages being generated initially. Message clearance is more of a visual aid when resolving errors in the design, allowing you to manually remove messages as you feel they have been resolved. The instigating command must be launched again to obtain an up-to-date picture of any violations that still exist.
2. Clearing all messages is particularly useful when you don't want any previous messages, from any other sources, to confuse messages that have been generated from the last command.
3. With respect to PCB/Compiler/Comparator-specific messages, if the associated document is closed, the corresponding message entries will be automatically cleared from the panel. For example, if you run a DRC Check on a PCB document, any violation messages listed in the Messages panel for that document will be cleared from the panel, if the document is closed.

Applied Parameters: ObjectKind=MessageView|Action=ClearSelected

Summary

This command is used to clear all currently selected messages in the Messages panel.

Access

With the required messages selected in the Messages panel, this command is accessed by right-clicking over a message in that selection, and choosing the Clear Selected command from the context menu.

Use

First, ensure that all messages that you wish to clear, are selected in the Messages panel.

After launching the command, all selected messages in the panel will be cleared.

Tips

1. Clearing messages does not necessarily mean the messages have been resolved. The same unresolved messages will be listed after performing the same command that led to the messages being generated initially. Message clearance is more of a visual aid when resolving errors in the design, allowing you to manually remove messages as you feel they have been resolved. The instigating command must be launched again to obtain an up-to-date picture of any violations that still exist.
2. With respect to PCB/Compiler/Comparator-specific messages, if the associated document is closed, the corresponding message entries will be automatically cleared from the panel. For example, if you run a DRC Check on a PCB document, any violation messages listed in the Messages panel for that document will be cleared from the panel, if the document is closed.

Applied Parameters: ObjectKind=MessageView|Action=ClearClass

Summary

This command is used to clear all messages from the Messages panel, that are of the same class as the currently selected message.

Access

This command is accessed from the Messages panel by right-clicking over the required initial message, and choosing the Clear Class command from the context menu.

Use

First, ensure that the cursor is positioned over a message belonging to the class of messages that you wish to clear, in the Messages panel.

After launching the command, all messages of this class in the panel will be cleared.

Tips

1. Clearing messages does not necessarily mean the messages have been resolved. The same unresolved messages will be listed after performing the same command that led to the messages being generated initially. Message clearance is more of a visual aid when resolving errors in the design, allowing you to manually remove messages as you feel they have been resolved. The instigating command must be launched again to obtain an up-to-date picture of any violations that still exist.
2. With respect to PCB/Compiler/Comparator-specific messages, if the associated document is closed, the corresponding message entries will be automatically cleared from the panel. For example, if you run a DRC Check on a PCB document, any violation messages listed in the Messages panel for that document will be cleared from the panel, if the document is closed.

Applied Parameters: ObjectKind=MessageView|Action=SaveAll

Summary

This command is used to save the current list of messages in the Messages panel, to file.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Save command from the context menu.

Use

After launching the command, the Save Message List To File dialog will appear. Use this dialog to browse to a particular destination in which to save the file, and to give the file a new name (if required). The saved file will include all messages that are currently presented in the Messages panel.

Tips

By default, the name of the file will have the format: Altium Designer Message List at <Date> <Time>.Txt.

Applied Parameters: ObjectKind=MessageView|Action=SaveSelection

Summary

This command is used to save selected messages in the Messages panel, to file.

Access

With the required messages selected in the Messages panel, this command is accessed by right-clicking over a message in that selection, and choosing the Save Selection command from the context menu.

Use

First, ensure that all messages that you wish to save to file, are selected in the Messages panel.

After launching the command, the Save Message List To File dialog will appear. Use this dialog to browse to a particular destination in which to save the file, and to give the file a new name (if required). The saved file will include only those messages that are currently selected in the Messages panel.

Tips

By default, the name of the file will have the format: Altium Designer Message List at <Date> <Time>.Txt.

Applied Parameters: ObjectKind=MessageView|Action=ExportToReport

Summary

This command is used to export the list of messages currently presented in the Messages panel, as a HTML-based report.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Export To Report command from the context menu.

Use

After launching the command, a HTML-based report will be created - MessageListReport.html - and opened as the active document in the main design window. The report contains all messages currently listed in the Messages panel. Each message in the report is hyperlinked to the associated source document. If the message involves a design primitive that is causing a violation, clicking the hyperlink will effectively cross-probe to that object on the associated document upon which it resides.

Tips

1. The report is generated in the same location as the project file.
2. When cross-probing to a PCB document, the document will be made active if it is not already, or unhidden and made active if it was previously in hidden mode. The offending object(s) will be automatically zoomed and centered (where possible) in the design window, but no other highlighting (filtering/masking/dimming) will be applied.
3. When cross-probing to a schematic document:
   1. The document will be made active if it is not already, or unhidden and made active if it was previously in hidden mode.
   2. The visual display of a cross-probed object on a schematic document in the main design workspace, is dependant on the highlighting options defined on the System - Navigation page of the Preferences dialog. These options include zooming, selecting and masking, the latter of which causes all other objects on the document to become dimmed, leaving only the offending object fully visible.
   3. The filtering applied when cross-probing from the report is temporary. Clicking within the design workspace will clear the filter. As such, you are not prevented from selecting or editing design objects that fall outside the scope of the filter.
   4. The extent of 'dimming' applied when the masking highlight option is enabled can be manually adjusted using the Dim slider bar - accessed by clicking the Mask Level button, at the bottom-right of the main design window.

Applied Parameters: ObjectKind=MessageView|Action=CopyToClipboard

Summary

This command is used to copy the selected messages - in the Messages panel - to the Windows clipboard.

Access

With the required messages selected in the Messages panel, this command can be accessed by:

• Right-clicking over a message in that selection, and choosing the Copy command from the context menu.
• Using the Ctrl+C keyboard shortcut.

Use

First, ensure that all messages that you wish to copy to the clipboard are selected in the Messages panel.

After launching the command, the selected messages, and header information, will be copied to the Windows clipboard.

Applied Parameters: ObjectKind=MessageView|Action=Print

Summary

This command is used to preview, and print, a report containing all messages currently listed in the Messages panel.

Access

This command is accessed from the Messages panel by right-clicking anywhere within the panel, and choosing the Print command from the context menu.

Use

After launching the command, the Report Preview dialog will appear, with a report containing all current messages in the Messages panel already loaded. Use the various controls in the dialog to adjust the view of the report.

Click the Print button to launch the standard Windows Print dialog, from where you can determine what is printed and to which printing device the job is sent.

If you want to export the report, click the Export button to open the Export Report From Project dialog. Use this dialog to determine where, by what name and in which format, the exported report will be saved. The report can be exported in the following supported formats:

• Microsoft Excel Worksheet (*.xls)
• Adobe PDF (*.pdf)
• Rich Text (*.rtf)
• Web Page (*.htm; *.html).
• Web Layer (CSS) (*.htm; *.html)
• JPEG Image File (*.jpg)
• Windows Bitmap File (*.bmp)
• TIFF Image File (*.tif)

Tips

1. By default, the name of an exported file will have the format: Altium Designer Message List at <Date> <Time>.<Extension>, where <Extension> will depend on the file format you have chosen.

Applied Parameters: ObjectKind=MessageView|Action=CrossProbeDetails

Summary

This command is used to cross-probe from the selected entry in the Details region of the Messages panel, to the indicated object responsible for the Compiler-generated violation.

Access

This command is accessed from the Details region of the Messages panel by right-clicking on the entry for the object of interest, and choosing the Cross Probe command from the context menu.

Use

First, ensure that the cursor is above the violating object to you wish to cross-probe, in the Details region of the Messages panel.

After launching the command, you will be taken directly to the object on the associated source document.

Tips

1. Double-clicking on an an object's entry in the Details region of the Messages panel will also perform a cross-probe.
2. Cross-probing can also be performed from the parent message entry (which will already be selected) in the main listing of messages in the Messages panel.
3. When cross-probing to the associated source schematic document:
   1. The document will be made active if it is not already, or unhidden and made active if it was previously in hidden mode.
   2. The visual display of a cross-probed object on a schematic document in the main design workspace, is dependant on the highlighting options defined on the System - Navigation page of the Preferences dialog. These options include zooming, selecting and masking, the latter of which causes all other objects on the document to become dimmed, leaving only the offending object fully visible.
   3. The filtering applied when cross-probing from the Messages panel is temporary. Clicking within the design workspace will clear the filter. As such, you are not prevented from selecting or editing design objects that fall outside the scope of the filter.
   4. The extent of 'dimming' applied when the masking highlight option is enabled can be manually adjusted using the Dim slider bar - accessed by clicking the Mask Level button, at the bottom-right of the main design window.

Applied Parameters: ObjectKind=MessageView|Action=CopyToClipboardDetails

Summary

This command is used to copy the selected entry(ies) - in the Details region of the Messages panel - to the Windows clipboard.

Access

With the required entry(ies) selected in the Details region of the Messages panel, this command can be accessed by:

• Right-clicking over the entry (or entry in a selection of entries) and choosing the Copy command from the context menu.
• Using the Ctrl+C keyboard shortcut.

Use

First, ensure that all detail message entries that you wish to copy to the clipboard are selected in the Details region of the Messages panel.

After launching the command, the selected entry(ies), and 'Details' header, will be copied to the Windows clipboard.