Code Editor Context Menu
When working on a file with a code editor, you can access a number of options through the context menu. Right-click on a text string to display the menu.
Topics
|
|
|
Options
|
The options on the menu can vary depending on which editor you are using, but should include some or all of the following:
• | Go to Declaration locates the declaration of a symbol in the source code |
• | Go to Definition locates the definition of a symbol in the source code (applicable to languages where symbols are declared and defined in separate places, such as C++ or Delphi) |
• | Search for '<string>' - displays a submenu that enables you to locate the search string in a range of locations: |
• | Find in Project Browser finds the object containing the selected text in the Project Browser |
• | Search in Open Files opens the Execution Analyzer File Search facility, then searches for the selected text string in other code files that are open of the same type and in the same folder as the current file, displaying the results in Tree View; you can change the folder path, search text and file type as required within the File Search window |
• | Search in Files performs the same search as Search in Open Files, except that the search is in all comparable files whether they are open or not |
• | Search in Model performs an Element Name search in the Model Search facility, and displays the results on the Model Search tab |
• | EA User Guide displays the description of the code item in the Enterprise Architect User Guide |
• | Google displays the results of a search on the text from a Google search |
• | MSDN displays the results of a search on the text in the Microsoft Developer Network (MSDN) |
• | Sun Java SE displays the results of a search on the text in the Sun Microsystems 'Sun Search' facility |
• | Wikipedia displays any entry on the object on the Wikipedia web site |
• | Koders displays the results of the search for the text string on Koders.com |
• | Set Debugger to Line - (if the debugger is executing and has reached a breakpoint) moves the execution point to the current line; ensure that you do not skip over any code or declarations that affect the next section of code being debugged |
• | Display Variable - (if the debugger is executing) opens the Locals window and highlights the local variable for the current point in the code |
• | Create Use Case for '<string>' - displays the Create Use Case For Method dialog, through which you create a Use Case for the method containing the text string |
• | Breakpoint - displays a submenu of options for creating a breakpoint or recording marker on the selected line of code |
• | Open (Close) IME - opens the Input Method Editor to enable you to enter text in your selected foreign language script (such as Japanese); you set the keyboard language using the Windows Control Panel - Regional and Language Options facility |
• | Line Numbers - (Script Editor only) shows or hides the code line numbers on the left hand side of the editor screen |
The remaining six context menu options provide simple editing functions.
|
Find In Files
Model Search
Pre-Defined Searches
View the Local Variables
Create Use Case For Method
Set Record Markers
|
Script Editor
|
If you select the Search for '<string>' context menu option while working in the Script Editor, a slightly different submenu displays.
The Search in Scripts option opens the Execution Analyzer File Search facility, setting the Search Path field to Search in Scripts and the Search Text field to the selected text, then searching all scripts for the text string and displaying the results of the search in Tree View.
|
Script Editor
|
Notes
• | The options in the lower half of the menu (after Search in Model) are configurable; you can add new search tools or remove existing ones by editing the searchProviders.xml file in the Sparx Systems > EA > Config folder - this file is in OpenSearch description document format |
Learn more
The material ("material" includes all pages, documents and on-line graphics) on this web site is protected by copyright law. (C) 1998-2011 Sparx Systems Pty Ltd.