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.
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.
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.
Currently Sigasi HDT does not support the renaming of overloadable identifiers. Contact support@sigasi.com if you are interested in this feature.
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.)
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
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 GUI.
Ignored resource are decorated with a 
-icon in the project
explorer view.
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 preferences: 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 general 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.
If the updates are not automatically fetched from the Sigasi update server you are probably behind a firewall or proxy server. You can configure HDT’s proxy settings in Window‣Preferences‣General‣Network connections. If you can not add a firewall exception for our update site, the fall back solution 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).
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 features 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.