4.3 Navigating Code with the Project Window

One of the most powerful features of BugHunter is the ability to quickly find code using the Project window. Try double clicking anywhere in the Project tree and investigate which code windows will open.

Find Definitions and Instances of Signals, Variables, or Components:

•Double click on the instance name in the Project window to open an editor that is scrolled to the location where the instance is declared.

•Double click on the Type name in the Project window to open an editor that is scrolled to the definition.

•Also if a signal is currently being watched, choosing the watch menu again will scroll the Stimulus and Results diagram to display the signal (see Section 2.3 Watching Signals and Component Waveforms).

•If you need to also set the scope, then right click on the module instance. The Goto menus set the scope to that instance and then jumps to the requested location.

Find Include Files:

•After the project is Built, the User Source Files folder in the Project window shows the components and the files that are included by that file.

•Double clicking on an include file in the project window will open up that file in an editor window.

•Double clicking on a module will bring you to the definition of that component.

Find Files that were brought in through the Library path:

•When instantiated module definitions are not located in the User Source Files, the simulator will search the library path for the missing modules. If such files are found, they will be placed in the Compiled Library Files folder under the Simulated Models tree.

Finding a Project Window object associated with a given code segment

•Right click on an object in a compiled source code editor window and choose Find in Project Window from the context window.
•The focus will shift to the Project window and highlight the associated object in the tree.