Skip to content
DVT e Language IDE for VS Code User Guide
25.2.13 (31 July 2025)
⌘ K
DVT e Language IDE for VS Code User Guide
25.2.13 (31 July 2025)
  • Installation
    • System Requirements
    • Install DVT for VS Code from Marketplace
    • Install DVT for VS Code from VSIX
    • Install DVT for VS Code Using a Pre-Packed Distribution
    • Set the License
  • User Interface
    • VS Code User Interface
    • DVT IDE for VS Code User Interface
  • Predefined Projects
  • Project Templates
    • What is a project template?
    • How to generate code from a project template
    • Template Configuration
  • Build Configurations
    • Project Natures
    • Non-top files
    • default.build
    • Auto-config
    • Simulator Log-config
    • Emulating compiler invocations
    • Multiple .build Files
    • Compatibility Modes
    • Paths
    • Strings
    • Comments
    • Environment Variables
    • Including Other Argument Files
    • Build Persistence
    • All Build Directives
    • e Language Test Files
    • e Language SPECMAN_PATH
    • SystemVerilog OVM or UVM Library Compilation
    • Xilinx Libraries Compilation
    • Intel(Altera) Quartus Libraries Compilation
    • Questa Libraries Compilation
    • Use of External Programs
  • Compile Checks
    • Compile Waivers
    • Semantic Checks
  • Content Assist (Autocomplete)
    • Snippets
  • Snippets
    • Snippets in Content Assist
    • Snippet Scope
    • Create new snippet
  • Hyperlinks
  • Show Usages
  • Show Readers or Writers
  • Show Instances
  • Show Constraints
  • Show Emitters
  • Peek Exploration
  • Refactoring
  • Syntax Coloring
  • Database Out of Sync Notification
  • Tooltips
    • Comments Formatting
  • Workspace Symbols
  • Views
    • Compile Order View
    • Compiled Files View
    • Diagnostics View
    • Outline View
    • Problems View
    • Verification Hierarchy View
  • Quick Search in Views
    • CamelCase
    • Simple Regex
    • Hierarchical Search
    • Search for Members
    • Search Port in Verification Hierarchy
  • Content Filters
    • Content Filters XML syntax
    • Filtering by Element Type
    • Content Filters Examples
    • Predefined Content Filters
  • External Tools Integration
  • UVM Support
    • UVM Content Filters
    • UVM Verification Hierarchy
  • Scripts
    • dvt_code.sh
    • dvt_ls.sh
    • evip2dvt.sh
  • Custom Scripts
  • SCM Checkout Hook
  • Memory Monitor
  • Application Notes
    • Flow Integration
    • Environment Variables
    • Encrypted VIP Support
    • Output and logging
    • Understanding DVT IDE memory usage
  • Handy VS Code Documentation Pointers
  • What is New?
  • How to Report an Issue?
  • Legal Notices
  • Third Party Licenses
  • Q & A
    • Can I deactivate DVT support for a workspace even though one of my workspace folders contains a .dvt directory?
    • Unable to write program user data
    • Some files are missing from the VIPs transformed with evip2dvt.sh
DVT e Language IDE for VS Code User Guide
/
Hyperlinks

Hyperlinks

Hyperlinks are available for all classes, modules, methods, fields, signals, macros, etc. in the source code files that DVT analyzes in your project.

Go to Declaration

Place editor cursor over an identifier and use the Go to Declaration command to go to the declaration of the element.

../../_images/open_declaration.gif

Go to Definition

Place editor cursor over an identifier while holding down Ctrl. The identifier becomes a hyperlink, which jumps to the definition of the element.

You can also use the Go to Definition command.

../../_images/open_definition.gif

Go to Type definition

Place editor cursor over an identifier and use the Go to Type Definition command to go to the type definition of the element.

../../_images/open_type.gif

Hyperlinks in Comments

You can define hyperlinks in comments using the @link or @see pragmas, for example:

// @link uvm_pkg::run_test
// For more details @see spi_if.miso and @see spi_if.mosi

Hover the hierarchical id specified after the pragma with the mouse cursor while holding down Ctrl and Click to go to the element’s declaration.

The hierarchical identifier following @link or @see is of the form:

[<package_name>::<type_name>.<inner_type_name>.]<element_name>

where <element_name> must be a type (class, struct, module, entity, interface, etc.) or a type member (method, field, event, signal, port etc.).

../../_images/hyperlinks_in_comments.gif

Jump to an Imported File

Place the mouse cursor over an imported file while holding down Ctrl. The identifier becomes a hyperlink, which jumps to the file.

../../_images/jump_to_an_imported_file.gif

Jump to a Macro Definition

Place the mouse cursor on a macro while holding down Ctrl. The identifier becomes a hyperlink, which jumps to the macro definition.

../../_images/jump_to_a_macro_definition.gif
Create new snippet
Show Usages

On this page

  • Go to Declaration
  • Go to Definition
  • Go to Type definition
  • Hyperlinks in Comments
  • Jump to an Imported File
  • Jump to a Macro Definition

© 2005-2025 AMIQ EDA s.r.l. (AMIQ). All rights reserved. DVT 25.2.13 (31 July 2025). Built with Sphinx 8.1.3