Complete the following steps:

Contents of procsearch.e:

#include 'slick.sh'

 

_command int proc_search(...) name_info(','VSARG2_READ_ONLY|

                                 VSARG2_REQUIRES_EDITORCTL|

                                 VSARG2_MARK)

{

    // Save the original cursor position to restore later.

    typeless original_position;

    save_pos(original_position);

 

    // Prompt the user for a search string, and search options.

    _str result = show('-modal _textbox_form',

                    'Search Function',  // Dialog box caption.

                    TB_RETRIEVE_INIT,   // Flags.

                    '',                 // Use default text box width.

                    '',                 // Help item.

                    '',                 // Button list.

                    'procsearch',       // Retrieve name.

                    'Search string:',   // First prompt.

                    'Options:ixcs');    // Second prompt and default.

    if ( result=='' ) {

       // If the user clicked the Cancel button, just return.

       return(COMMAND_CANCELLED_RC);

    }

 

    // The results from the text boxes.

    _str search_string=_param1;

    _str search_options=_param2;

 

    int status=select_proc(); // Select the current proc.

    if ( status ) {

       // In rare cases select_proc can fail if a procedure is too complex.

       // If select_proc failed, show an error messages, return the cursor to the

       // original position, and return.

       _message_box(nls("select_proc failed"));

       restore_pos(original_position);

       message(get_message(status)); 

       return(status); 

    }

    lock_selection();   // Lock the selection.

 

    begin_select();     // Move the cursor to the beginning of the selection.

 

    status=find(search_string,'m':+search_options);  // Find the text that the

                                                     // user specified using the

                                                     // options specified. We 

                                                     // prepend the 'm' option

                                                     // since we know we are

                                                     // searching in a selection.

 

    if ( status ) {

       // If the search string was not found, deselect and return the cursor to

       // the original position. 

       deselect();

       restore_pos(original_position);

    }

 

    // Just return the status. This will leave the proc selected so that

    // find_next works.

    return(status);

}

The save_pos() call at the beginning of the macro saves the current cursor position information. This function places the cursor in its original position if necessary.

The show() function launches a dialog box. In this case, the show() function launches a general purpose dialog box named _text box_form. The dialog box _text box_form prompts the user for one or more strings. After the first argument, the remaining arguments to show() pass to the on_create dialog box. In this case, there are several arguments.

The second argument to show() is the caption for the on_create dialog box.

The next argument is a set of flags. In this case, the only flag specified is TB_RETRIEVE_INIT. The TB_RETRIEVE_INIT flag tells the dialog box to initialize itself by retrieving the last values filled in for this dialog box.

Use the next three arguments to specify text box width, help, and a button list. These particular arguments are unused in this example, which is why they are shown here as ''.

The retrieve name is a unique name used to retrieve the values that were previously filled in for this dialog box. Any remaining arguments are interpreted as prompts for the user. Default values can be given by specifying the prompt as prompt:defaultvalue. The first prompt is the search string, and the second is for search options. The options have default ixcs, meaning case-insensitive, and exclude comments and strings. See the following section for a list of command line search options.

After the call to show, verify that the result is ''. If so, then the user clicked the Cancel button, so we return. Otherwise, SlickEdit® must obtain the values that the user provides. These values are returned in global variables _param1.._param N. In this case, our search string is returned in _param1, and the search options are in _param2. These are saved in local variables.

SlickEdit calls select_proc to select the current function. If select_proc returns a non-zero status, then it failed, so it is returned. In rare cases, select_proc can fail if a function is too long, or has preprocessing that keeps it from correctly identifying the end of the function.

Next, lock_selection() is called, and then begin_select() is called to move to the beginning of the selection.

Now, we can call find() with the search string and the search options from the user. Insert m at the beginning of the options string to specify search only in the selection.

Finally, check the status from find. If the string is not found, clear the function and restore the original cursor position.

Command line search options include the characters listed in the table below.

The table below contains functions for reading and modifying buffers. This table focuses on one particular category of the API, those functions that allow you to programmatically traverse and modify buffers. These powerful functions enable you to take tasks that you can do manually, and create a macro to perform the same tasks in seconds.

The table below contains functions that can be used for navigating buffers.

Escape backslashes if, for every slash in a directory name, you actually need two for the compiler to handle the directory name or string properly.

Example:

_command escape_slash(){

    _str myLine;

    get_line(myLine); // Set string szLine to the current line.

    myLine = stranslate(myLine, "\\\\", "\\"); // Replace slash with double

                                               // slashes.

    replace_line(myLine); // Replace the line in the buffer.

}

The above command accepts the following line of code:

myDirectory = "C:\Data\Corporate\Internal";

and replaces it with:

myDirectory = "C:\\Data\\Corporate\\Internal";

Print or debug statements can be used to debug. These statements need to have supporting comments or they must be deleted. The following example shows a simple function that loops through your entire file. It contains supporting comments for all of the lines that have a printf statement:

_command comment_printf(){

    _str curLine;

    top(); // Go to top of buffer

    up();  // Get to the top line

    while ( !down() ) {                    // Loop until end of file.

       get_line( curLine );                // Get the current line.

       if( pos( "printf", curLine ) ){     // Search for a printf.

 

          _begin_line();                   // If printf exists, move cursor to the

                                           // first column.

 

          _insert_text( // );              // Add a comment.

       }

    }

}

The function uses many of the buffer modifications and navigation macros. It loops line-by-line through the file, checks for a string, and adds a comment when necessary. Modify this macro to meet your needs. For example, if you want the lines deleted instead of commented, replace the _insert_text() call with delete_line(). Also, check to see if the comment characters already exist before you add the comment text. Instead of calling _begin_line, call begin_line_text_toggle'this places the cursor at the first non-space character of a line. Next, check if you are in a comment by calling _in_comment().

SlickEdit® includes a line number toggle option to turn line numbers on and off for each edit window. This option is located on the View menu (Display → Line Numbers). By default, all files are displayed without line numbers. When you enable them, they are enabled throughout sessions until you disable them. SlickEdit also provides an option to enable line numbers on a language-specific basis (Window → SlickEdit Preferences → Languages → [Language Category] → [Language] → General).

To automatically turn on line numbers for all files that are opened or created in SlickEdit regardless of the language, you will need to write a macro, as outlined in the subsequent sections:

#include "slick.sh" 

 

void _buffer_add_ViewLineNumbers()

{

    p_LCBufFlags|=VSLCBUFFLAG_LINENUMBERS;

    p_line_numbers_len = _default_option(VSOPTION_LINE_NUMBERS_LEN);

}

The number of lines of code in your workspace, projects, or files is often used to measure and analyze performance, and can be determined by using a macro.

This example describes a macro, linecount.e, that loops through all projects in the current workspace and all files within each project in the current workspace, and then displays a report in a new editor window.

You can obtain linecount.e from the SlickEdit Web site at www.slickedit.com in the Slick-C® Documentation section. Line numbers referenced in the subsections below: