Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Sigasi Team
1 Introduction 3
3 Setting up a project 7
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Starting a new project from scratch . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Pointing to an existing VHDL project . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.4 Importing a project from an archive . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4 VHDL Libraries 9
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.2 VHDL library concepts in Sigasi HDT . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3 External libraries usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.4 Library configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.5 Library configuration use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 User Interface 13
5.1 Project views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2 Project view usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3 Project exploration and navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 VHDL-specific editing 15
6.1 Block selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.2 Align . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.3 Move lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.4 Indent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.5 Fix Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8 Autocompletion 19
i
8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.2 Autocompletion interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
8.3 Autocompletion based on the VHDL language . . . . . . . . . . . . . . . . . . . . 19
8.4 Autocompletion based on the design context . . . . . . . . . . . . . . . . . . . . . 20
9 Refactoring 21
9.1 The refactoring interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
9.2 Available refactorings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
11 Preferences 31
12 Troubleshooting 33
13 Keyboard shortcuts 35
13.1 Top 11 keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.2 Keyboard shortcut reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Index 39
ii
Sigasi HDT User Manual
Contents:
CONTENTS 1
Sigasi HDT User Manual
2 CONTENTS
CHAPTER
ONE
INTRODUCTION
Sigasi HDT is the compelling next-generation development environment for VHDL designers.
Sigasi HDT is an intelligent development environment (IDE). It differs from other develop-
ment tools in that it contains an ultra-fast VHDL parser and compiler that runs transparently
in the background. At any given moment as you make modifications, the tool fully under-
stands the design in terms of VHDL concepts. This technology makes it possible to support a
wide range of powerful features:
Intelligent navigation Navigate to any VHDL object in the design by selecting it in a hierar-
chical view. Or directly navigate from an object to its declaration.
Instant error reporting Get immediate feedback on errors introduced by a modification.
Quickfixes Fix errors by using a quickfix proposed by the tool.
Intelligent code completion Use the tool to assist in completing VHDL constructs based on
its knowledge of the design.
Refactoring Use the tool to make sophisticated code transformations that maintain the behav-
ior of the design.
All these features create a novel user experience that greatly improves productivity.
The last feature that was mentioned, refactoring, is Sigasi HDT’s most innovative and powerful
functionality. Refactoring is a modern software development technique. Sigasi HDT imple-
ments it for digital hardware design.
Refactoring makes a new level of automation available to the designer. You can use it to make
code clearer and more reusable, to find bugs, and to prepare code for adding new functionality.
Examples of refactorings are:
• intelligent rename of VHDL objects over the whole design
• making all modifications to add or remove a port in a single action
• making all modifications to add or remove a connection in a single action
• modifying design hierarchy
• making code technology independent
Refactoring is a large topic on itself. For that reason, we have written a dedicated book about
it: The VHDL Refactoring Book (in The VHDL refactoring book).
3
Sigasi HDT User Manual
4 Chapter 1. Introduction
CHAPTER
TWO
2.1 Installation
Sigasi HDT is distributed online or on a CD-ROM. To install it, first find the right archive for
your platform according to the following table:
Platform Archive name
Linux HDT-linux-<version>.zip
Windows HDT-win32-<version>.zip
Mac
Choose or create a folder where you want to install the software, and unpack the archive there.
The archive contains a single top-level folder called hdt. Inside the hdt folder there is an
application startup file, also called hdt. Start the application by executing the hdt startup file.
2.2 Configuration
Sigasi HDT stores its projects on the file system in one or more workspaces.
When you start the tool for the first time, it will suggest to create a workspace for
Sigasi HDT has an automated update system. When updates are available, you are
notified by a pop-up window called Updates Available in the bottom right corner:
5
Sigasi HDT User Manual
THREE
SETTING UP A PROJECT
3.1 Introduction
Your work with Sigasi HDT is organized as a project. A project is a collection of VHDL files
that belong together. Sigasi HDT understands the VHDL units defined in the files, and the
relationships between them.
Your first step with Sigasi HDT is to set up a project. There are a number of ways to do this:
• Starting a new project from scratch
• Converting an existing VHDL folder into a HDT project
• Importing a HDT project from an archive
Each of these methods is discussed in detail in the following sections.
To create a new project, select File → New → VHDL Project. Then give your project a name.
By default, the Use default location checkbox is checked, which means that new projects will
be located in the workspace folder. Alternatively, you can uncheck the checkbox and choose
an arbitrary location for your project instead.
After creating a new project, you can add existing files by dragging them from your filesystem
into the project explorer. New files can be added by clicking File → New → VHDL file.
If you have an existing VHDL project, you can easily start working on it with Sigasi HDT.
To create a new HDT project from you existing VHDL project, use File → New → Point to
existing VHDL project. Then, select the top level folder of your existing VHDL project. Sigasi
HDT will add a few hidden project files to your folder, and the project is ready to be used from
Sigasi HDT.
7
Sigasi HDT User Manual
Sigasi HDT projects can be shared with others using file archives. All project-related settings
are stored in two hidden files in the project folder. Therefore, you can just create an archive of
the entire top level folder (File → Export → General → Archive file) and send it to someone else.
To import a project from an archive, point Sigasi HDT to the project by clicking: File → Import
→ General → Existing projects into Workspace. Next select Select archive file:, browse to your
project archive, and press Finish.
FOUR
VHDL LIBRARIES
4.1 Introduction
VHDL libraries are a very powerful albeit slightly complex feature of the VHDL language.
Sigasi HDT tries to make it easy and straightforward to configure and use them.
In this chapter, we assume that the basic concepts of VHDL libraries are understood. We will
explain how they are implemented in Sigasi HDT.
We will also present some use case about how to set up VHDL libraries with Sigasi HDT to
organize your projects.
When you define a library as external, you indicate that it is read-only. This has a number
of advantages. First, you cannot accidentally change files that are not in the current project.
Moreover, Sigasi HDT will preprocess the files and cache their contents for quick access. This is
especially important for certain third party libraries that contain huge amounts of information.
When an external library is modified by some action outside of the project, the cache becomes
out of date. The next time the project is fully compiled, the external library will be recompiled
by Sigasi HDT.
9
Sigasi HDT User Manual
Warning: Sigasi HDT currently does not inform you when an external library cache is out
of date. To trigger a full recompile of the project, press F6.
Also, a software update may render the cache out of date. To reset the cache, select Window
→ Preferences → Libraries and press reset cache.
4.4.1 Introduction
Like with any VHDL tool, Sigasi HDT needs to know where the libraries are located on the file
system. In this section, we will describe how library configuration works in Sigasi HDT.
To examine the VHDL library configuration, select Project → Properties → Libraries. Per VHDL
library, three attributes are listed:
At- Meaning
tribute
name The name of the library.
loca- Library location in the form type:/path. type is project for a project library, file
tion for an external library, and resource for a built-in library. path specifies the path
of the library’s folder on the file system.
ex- Files and folders that are excluded from the library.
cludes
The library location folder is used by Sigasi HDT as the top of a search tree for VHDL files.
This means that all subfolders are considered recursively.
By default, the standard VHDL libraries std and IEEE are configured as built-in resource
libraries. Moreover, library work is defined as a project library with the top-level project di-
rectory as its location.
The library configuration described in the previous section is fully editable. You can use the
add button to add a new library and the remove button to remove an existing library. Further-
more, with the edit button a library’s attributes can be modified as follows:
A convenient way to configure a new library is by using a quickfix. Start by typing the li-
brary declaration of the new library in your code. Sigasi HDT will flag an error and propose
the quickfix Define undefined library. If you choose the quickfix, the library configuration
window will open with the new library ready to be defined further.
Recall that a library’s location folder is used as the top of a search tree for VHDL files.
Sometimes you may want to use a subfolder of a library location as the location of another
library. Sigasi HDT lets you do this without a problem. Just specify the subfolder as the
location for the new library. All files found in the subfolder tree will become part of that
library instead of the original one.
Note that the order of the library configurations does not matter. When assigning files to
libraries, Sigasi HDT will use the most specific location definition.
Sometimes it may be convenient to have multiple locations to search for library files. In Sigasi
HDT, you can add multiple entries for the same library, each with a different location. All
locations will be considered when looking for VHDL files.
You can even use mix project and external locations for the same library. However, this is not
recommended practice, with the possible exception of the special library work.
4.5.1 Introduction
Libraries are a powerful but somewhat underutilized feature of VHDL. Sigasi HDT makes it
easy to set them up and take advantage of them. In this section, we describe a number of use
cases for working with libraries in Sigasi HDT.
Some projects may only need standard libraries and library work. In that case, no additional
library configuration is needed. You can just go ahead with the default configuration.
Many projects use third party libraries. These should be defined as external libraries.
A number of popular third party libraries are the following:
Vendor Library Install dir example
Xilinx unisim C:\Xilinx\10.1\ISE\vhdl\src\unisims
Xilinx XilinxCoreLib C:\Xilinx\10.1\ISE\vhdl\src\XilinxCoreLib
Xilinx simprim C:\Xilinx\10.1\ISE\vhdl\src\simprims
Altera altera_mf C:\altera\81\quartus\libraries\vhdl
As an example, we will show how to configure the Xilinx library XilinxCoreLib as an ex-
ternal library. Add the following line to your vhdl file:
Library XilinxCoreLib;
When you save, a quick fix icon occurs next to the new line. Select the quickfix Define
undefined library. The library configuration window pops up, with the XilinxCoreLib
library marked as undefined.
Select the library location and press edit. A library definition window pops
up. Select Select external folder to define the library as external. Then
browse to \vhdl\src\XilinxCoreLib in the Xilinx installation to de-
fine the path of the library’s folder, and click OK. A pathname similar to
C:/Xilinx/10.1/ISE/vhdl/src/XilinxCoreLib will appear. Click OK. As the
library is external, the specified folder is scanned for all vhdl files. All these files are
preprocessed and cached for quick access.
In many organizations, new projects reuse older ones. Moreover, some projects may be set up
as IP projects for which reusability is the primary design goal.
It is good practice to use libraries to organize reusable projects. Libraries improve design
clarity and avoid name clashes between design units from different projects.
Only the current project should be defined as a project library. The reusable projects that it
refers to should be defined as external libraries. As external libraries are read-only, such a
set-up makes the project’s purpose clear and avoids mistakes.
Sometimes it is required to maintain multiple variants of a design unit. For example, an entity
definition may need to be slightly different depending on the target technology. Although they
are different, you may want to refer to the “same” entity by the same name. Conceptually, such
a problem can be solved by defining the same identifier in different namespaces.
VHDL libraries can emulate namespaces. For example, you could define a library MY_PROJ for
the common design units of a project. In addition, you could define libraries for technology-
dependent design units, for example MY_PROJ_XILINX and MY_PROJ_ALTERA. The set-up
gives you the required flexibility and clarifies the purpose of all design units.
FIVE
USER INTERFACE
When you open a project in Sigasi HDT, a number of views are presented in
the user interface. Here is a typical screenshot, with the views highlighted:
The hierarchy view and the outline view are alternative views on similar information. You
can switch between them by using the tabs in the containing window. You can also resize the
views by dragging the view separators or reorganize them by dragging the tab label.
13
Sigasi HDT User Manual
The outline and hierarchy view are automatically synchronized with the editor every time the
file is saved. The project explorer view can also be linked with the editor by clicking the link
View Menu ( ) and then Customize view. You can then select a filter whose matching files
are hidden in the project explorer view.
Sigasi HDT offers powerful techniques to explore a project and navigate through it.
Hovering To find the declaration of a given identifier, hold your mouse pointer over it. After
about a second, a popup shows you the name and datatype of the signal. This technique
is called hovering.
Highlighting If you click on an identifier, it is highlighted. In addition, all other occurrences
of the identifier that refer to the same object are highlighted. Note that this highlighting
is intelligent: it is not based on the identifier’s string value, but on the object that the
identifier refers to.
Navigate to a declaration You can easily navigate to the declaration of any port, signal, entity,
etc. Place the cursor on the identifier, right-click and select Open Declaration. The edi-
tor immediately switches to the line that declares the object. Since this operation is so
commonly used, it is assigned to the shortcut key F3.
Finding object occurrences To look for occurrences of a given identifier in different files, place
your cursor on the identifier and right-click. Now select Search References. A search win-
dow will appear on the bottom of your workbench, displaying all occurrences of the
selected identifier. You can easily navigate through all occurrences by clicking the Show
Next Match arrow and the Show Previous Match arrow in the search result view. Note
that all occurrences are highlighted and marked with a small arrow at the left border of
the editor for easy recognition.
SIX
VHDL-SPECIFIC EDITING
In addition to the powerful features of an Eclipse editor, Sigasi HDT supports a number of
advanced editing features which are specifically useful for VHDL editing. These are described
in this chapter.
Block selection is an alternative for standard (paragraph) selection. Block selection mode dif-
fers from standard selection mode in that it allows to select rectangular regions, or to set the
cursor over multiple lines. Block selection is ideal for selecting vertical regions, for example a
column of a table or all port names in a port map.
To toggle between normal and block selection modes use Alt+Shift+A or Edit → Toggle Block
Selection
6.2 Align
You can align the current selection with Edit → Align. Aligning is done by looking at a common
delimiter string in consective lines. The supported delimiter strings are: <= , := => :
Blank lines and comment lines are ignored. Both tabs and spaces are supported.
You can easily move lines up and down by pressing Alt+Up and Alt+Down.
6.4 Indent
You can easily clean up the indentation and remove trailing whitespaces in the current selec-
tion, by pressing Ctrl+I.
15
Sigasi HDT User Manual
VHDL is case insensitive. However, for clarity’s sake it is best to keep the case of identifiers
and keywords consistent throughout the project.
By right-clicking in the editor window, you can access the Fix Case refactoring. This action
cleans up the case of the keywords and indentifiers in your file as follows:
• keywords are in lowercase
• enumeration literals are in uppercase
• constants are in uppercase
• the case of other objects is fixed according to their declaration
SEVEN
Sigasi HDT has reasonable defaults for the severity level of reported problems. How-
ever, the severity level of certain classes of problems is configurable for additional flexi-
bility. The configuration interface is available in Window → Preferences, Errors/Warnings.
7.3 Linting
Sigasi HDT provides info about potential problems in the design. The following problems are
reported:
Unused declaration
17
Sigasi HDT User Manual
7.4 Quickfixes
EIGHT
AUTOCOMPLETION
8.1 Introduction
Sigasi HDT provides powerful autocompletion capabilities. This means that the tool can help
you to complete identifiers and constructs as you are working on the code. Like other tools, the
tool provides autocompletion based on the VHDL language. However, it goes much further. It
also provides autocompletion based on the design context. It can provide this additional level
of intelligence as it knows all objects that have been declared in the design.
Autocompletions may come from different sources, as will be discussed in the following sec-
tions. However, the user interface to initiate them is always the same. At any point as you are
entering code, you can press CTRL-SPACE and the tool will suggest appropriate autocomple-
tions.
Some autocompletions are templates which require further user input. In such a case, the
editor goes into a special template editing mode after the autocompletion has been performed.
You can use TAB to cycle through the items that have to be modified or completed. When
done, you can press ENTER to return to the normal editing mode. The cursor will be placed at
an appropriate position to continue working.
As you are typing code, Sigasi HDT can autocomplete any VHDL keyword.
Sigasi can help you to declare VHDL objects, using autocompletion based on templates. There
are templates for the declaration of the following VHDL objects:
• function
• procedure
19
Sigasi HDT User Manual
• process
• type: enum, file, range, array, record
• signal, constant, variable
• component
• entity
• architecture
• entity/architecture pair
• package
After the autcompletion, the editor will be into templating editing mode.
Sigasi HDT uses its knowledge of the design to provide intelligent autocompletions that can
boost productivity tremendously.
8.4.1 Identifiers
The tool knows which objects are appropriate and which identifiers are visible at any given
point in the code. As you start typing and ask for an autocompletion, it will therefore suggest
the appropriate identifiers as autocompletion candidates.
20 Chapter 8. Autocompletion
CHAPTER
NINE
REFACTORING
The basic interface to access a refactoring is to right click on a selected identifier or a line in a
view. Depending on the selection and the view, a list of appropriate refactorings is shown.
For example, the Rename refactoring is available for an identifier in the editor view. Other
refactorings are available in the outline view and the hierarchy view.
For background info, see Add Generic (in The VHDL refactoring book) in The VHDL Refactoring
Book (in The VHDL refactoring book).
For background info, see Add Port (in The VHDL refactoring book) in The VHDL Refactoring Book
(in The VHDL refactoring book).
For background info, see Change Positional To Named Association (in The VHDL refactoring book)
in The VHDL Refactoring Book (in The VHDL refactoring book).
For background info, see Connect Instance (in The VHDL refactoring book) in The VHDL Refactor-
ing Book (in The VHDL refactoring book).
21
Sigasi HDT User Manual
For background info, see Encapsulate Concurrent Statements (in The VHDL refactoring book) in
The VHDL Refactoring Book (in The VHDL refactoring book).
Tip: The encapsulate refactoring is often used to avoid code duplication. To detect code
duplication you can use the internal compare function. To compare two files: select the two
files in the project explorer, right-click and select Compare With→Each Other.
9.2.7 Rename
For background info, see Rename (in The VHDL refactoring book) in The VHDL Refactoring Book
(in The VHDL refactoring book).
22 Chapter 9. Refactoring
CHAPTER
TEN
10.1 Introduction
Sigasi HDT supports a number of ways to integrate external tools, with varying degrees of
automation. The simplest case is to add a menu item to start an external tool from within
Sigasi HDT. This is done by creating an external tool configuration. You can also arrange for
an external tool to be run automatically when a Sigasi HDT project is rebuilt. This is done
by creating a builder. Finally, Sigasi HDT supports automatic Makefile generation for completely
automating the integration.
Select Run → External tools → External Tools Configurations to get started, or use the -icon.
23
Sigasi HDT User Manual
An external tool configuration as described in the previous section makes it easy to run an
external tool, but you still have to do so explicitly. For some programs, such as the make
utility, it makes sense instead to do this automatically upon a change in your project. This
functionality can be accomplished by a builder. We will show how to create a builder for a
Modelsim Makefile as an example.
To create a builder, right-click your project and select Properties → Builders.
Click New... and the builder configuration window will pop up:
checkbox.
After configuration, the new builder will appear in the builder list.
With a builder as described in the previous section, a program such as make can run automat-
ically whenever your project changes. However, when you make a significant change to your
project, the makefile itself may become obsolete and require nontrivial changes. To solve this
problem, Sigasi HDT can automatically create and update a makefile for you.
Sigasi HDT can generate makefiles for a number of targets, including Modelsim vsim, Xilinx
Isim, and ghdl.
For example, to set up makefile generation for ModelSim, first verify that the Model-
Sim commands vcom and vlib are on your system path. Right-click on your project
in the Project Explorer and select Properties. Makefile generation can be configured
in the Makefiles category. Enable Mentor Modelsim (vsim) and confirm with Apply.
ELEVEN
PREFERENCES
In the menu Window → Preferences you can change the default settings of HDT. E.g. in VHDL
→ Editor you can change the syntax highlighting colors and in VHDL → Templates you can
change or add templates for autocompletion.
31
Sigasi HDT User Manual
TWELVE
TROUBLESHOOTING
I want a clean restart If you ever suspect that the state of your project is inconsistent in Sigasi
HDT, you can always force a complete clean compilation by selecting Project → Rebuild
Project, or by just pressing F6. You can also reset the external library cache by selecting
Window → Preferences → Libraries and pressing reset cache.
The user interface is unresponsive If the user interface of Sigasi HDT is unresponsive, you
can always interrupt the internal compilation process by pressing the stop button in the
progress view. To activate the progress view, select Window → Show View → Other... →
General → Progress, or click the tiny conveyor belt icon , on the right side of the status
bar.
The editor displays old contents of a file If you edit a file outside of HDT with an external
editor, HDT will normally notice the changes and ask you what to do. If it doesn’t, you
can refresh the editor’s content by pressing F5 or by right-clicking a file or a project in
the project explorer and selecting Refresh.
HDT says “Element cannot be renamed”? Currently Sigasi HDT does not support the re-
naming of overloadable identifiers. Contact support@sigasi.com if you are interested
in this feature.
What version am I running? You can check if you have the latest update by clicking on help
–> About Sigasi HDT –> Plugin details. The version number contains the date of the
release. (For example, version 1.0.0.20081218... was released on December 18, 2008.)
How much local history will be stored? Sigasi HDT stores multiple copies of your file so that
you can compare your current version with the version you saved an hour ago.
You can define how much disk space is used for storing local history in Windows →
Preferences, select General → Workspace → Local History.
For more information on local history, check out
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.platform.doc.user/gettingStarted/qs-
55.htm
HDT analyzes VHDL files that I don’t need By default, HDT assumes that all VHDL files are
part of the project. However, some projects may contain multiple files with older or
alternative definitions of a VHDL object. In such a case you will want HDT to ignore
certain files.
To exclude files (or directories) from analysis, you can use the library configuration prop-
erty page (see Library configuration).
Ignored resource are decorated with a -icon in the project explorer view.
33
Sigasi HDT User Manual
How can I change the font size? Sometimes you want extra small fonts, so that you can fit
more content on your screen. Another time you may want extra large fonts, so that you
can use a beamer and your audience can see what you are doing.
Most fonts, including the font that is used by the editors, can be controlled in the pref-
erences: Window→Preferences Fonts are controlled in General→Appearance→Colors and
Fonts. The font of the editors are in Basic→Text font.
Some fonts cannot be controlled in this preference page. These fonts are defined by gen-
eral system settings, and are used for writing the menu names, the Project Explorer view
and the Outline and Hierarchy views. On Windows, you can change these fonts by
changing your font settings in the Windows Control Panel. On Linux, these fonts are
controlled by a settings file: ${HOME}/.gtkrc-2.0 . You can change the font by adding a
line like:
gtk-font-name = “Sans 10”
You have to restart Sigasi HDT before these changes take effect.
I don’t get automatic updates If the updates are not automatically fetched from our update
server (https://update.sigasi.com) you are probably behind a firewall or proxy server.
You can configure HDT’s proxy settings in Window→Preferences→General→Network con-
nections. If you can not add a firewall exception for our update site, the fall back so-
lution is to download the complete application from our website. You can completely
replace your old installation; all settings are stored in your workspace (the default is
workspace-sigasi in your home directory).
I get a warning about single-file mode When you open a VHDL file with File→Open File,
Sigasi HDT warns that you are editing in single-file mode. In this mode, Sigasi HDT
does not understand your code as a VHDL design, and therefore its productivity fea-
tures are not available. Single-file mode can be useful to edit files outside regular project
work, but normally you should open VHDL files through a project. To learn how to set
up a project, see Setting up a project.
THIRTEEN
KEYBOARD SHORTCUTS
As you become more experienced with Sigasi HDT, you will find that there are a number of
actions that you perform quite often. At some point, you may feel that the GUI-based approach
becomes too slow for these actions. For that reason, Sigasi HDT provides a number of keyboard
shortcuts. They are a great way to boost your productivity even more. 1
In this chapter, we describe the available keyboard shortcuts.
35
Sigasi HDT User Manual
10. Toggle Block Selection (Shift+Alt+A) Switch between regular and block selection
mode.
11. Quick Access (Ctrl+3) Ctrl+3 is the shortcut to use, when you forgot the shortcut
you actually need. With Quick Access you can quickly find open editors, available
perspectives, views, preferences, wizards, commands, etc. Simply start typing the
name of the item you wish to invoke.
13.2.2 Quickfixes
13.2.3 Autocompletion
13.2.5 Files
13.2.6 Navigation
13.2.10 Views
A K
Altera keyboard
library, 11 shortcuts, 34
associations
refactoring, 21 L
autocomplete library
component, 20 Altera, 11
instantiation, 20 IEEE, 9
autocompletion, 18 std, 9
Xilinx, 11
C linting, 17
component Linux
autocomplete, 20 installation, 5
connect instance
refactoring, 21 M
Mac OS X
E installation, 5
editing, 14 makefile, 28
encapsulate
refactoring, 21 N
external tools, 22 navigation, 14
G P
generics ports
refactoring, 21 refactoring, 21
project, 6
I import, 6
IEEE setup, 6
library, 9
import Q
project, 6 quickfix, 18
installation
Linux, 5
R
Mac OS X, 5 refactoring, 20
Windows, 5 associations, 21
instantiation connect instance, 21
autocomplete, 20 encapsulate, 21
interface generics, 21
refactoring, 20 interface, 20
ports, 21
rename, 22
39
Sigasi HDT User Manual
rename
refactoring, 22
S
setup
project, 6
shortcuts
keyboard, 34
single : preferences, 29
std
library, 9
T
troubleshooting
FAQ, 31
U
updates, 5
V
views, 13
W
Windows
installation, 5
X
Xilinx
library, 11
40 Index