Tagging Tab
. When the cursor is in the prototype, pressing
Ctrl
+
Dot
will navigate to the func-
tion and vice versa. If you do not set one of these options, you will be prompted with the
Select
a Tag Dialog
the first time you navigate from a symbol to its definition.
•
Auto-close visited files
- SlickEdit Core can automatically close a visited file, one that was
opened through symbol navigation but not edited. Click
Window
→
Preferences
, expand
SlickEdit
and click
General
in the tree, then double-click the
General
setting. On the General
Options dialog, select the
General Tab
, then select the option
Automatically close visited
files
.
Navigating Between Multiple Instances
If more than one instance of the definition or reference is found, the Select a Tag dialog is displayed, from
which you can select the instance to navigate to. To go to the next occurrence, press
Ctrl
+
G
or use the
find_next
command. To go to the previous occurrence, press
Ctrl
+
Shift
+
G
or use the
find_prev
com-
mand.
Alternatively, press
Ctrl
+
Down
(
next_tag
command) or
Ctrl
+
Up
(
prev_tag
command) to place the curs-
or on the next or previous symbol definition.
Using the Find Symbol View
The Find Symbol view (
Search
→
Find Symbol
) is used to locate symbols (tags) which are declared or
defined in your code. It allows you to search for symbols by name using either a regular expression, sub-
string, or fast prefix match. See
Find Symbol View
for descriptions of the options that are available.
More Symbol Navigation Methods
There are several other methods for navigating to symbols:
• The
Symbols View
shows the symbols for all tag files. Right-click in the view window and select
Find
Tag
to search for a specific symbol. You can also use the
cb_find
command to find the symbol under
the cursor and display it in the Symbols view.
• At the SlickEdit
®
Core command line, use the
f
command and completion keys (
Space
and
?
) to enter
a tag name. For example, if tagging the C run-time library, type
f str?
on the command line for a list of
tag names starting with "str" (such as
strcpy
,
strcmp
, etc.).
• To navigate to a Slick-C
®
symbol, you can use the
fp
command (a shortcut for
find_proc
). If editing a
Slick-C macro, then enter the
push_tag
command (
Ctrl
+
Dot
) to find the symbol at the cursor. The
push_tag
command actually calls the
find_proc
command with the symbol name at the cursor to per-
form the task.
Begin/End Structure Matching
Begin/End Structure Matching moves the cursor from the beginning of a code structure to the end, or vice
versa. This works for languages using curly braces "{ }", "begin" and "end", or any other defined begin/end
pairs.
Code Navigation
77
Summary of Contents for Corev3.3 for Eclipse
Page 1: ...Think Slick Corev3 3 for Eclipse...
Page 2: ......
Page 3: ...SlickEdit Core v3 3 for Eclipse...
Page 5: ......
Page 6: ......
Page 14: ...xii...
Page 20: ...xviii...
Page 22: ...xx...
Page 23: ...Chapter 1 Introduction 1...
Page 41: ...Chapter 3 User Interface 19...
Page 61: ...Chapter 4 User Preferences 39...
Page 80: ...BODY BODY HTML HTMLEOF Restoring Settings on Startup 58...
Page 82: ...60...
Page 83: ...Chapter 5 Context Tagging 61...
Page 97: ...Chapter 6 Editing Features 75...
Page 124: ...Code Templates 102...
Page 238: ...Figure 6 49 Test Parsing Configuration Example 1 C Refactoring 216...
Page 241: ...Figure 6 51 Test Parsing Configuration Example 3 Reviewing Refactoring Changes 219...
Page 250: ...228...
Page 251: ...Chapter 7 Language Specific Editing 229...
Page 328: ...306...
Page 329: ...Chapter 8 Tools and Utilities 307...
Page 350: ...328...
Page 351: ...Chapter 9 Macros and Macro Programming 329...
Page 360: ...338...
Page 361: ...Chapter 10 SlickEdit Core Dialogs 339...
Page 375: ...Find and Replace View 353...
Page 491: ...Chapter 11 Appendix 469...
Page 567: ......
Page 568: ......