CooCox - User Guide
CooCox - User Guide
2 2011-3-4 page 1
Index:
1. CoIDE Quick Start ....................................................................................................................................................... 4
2. Builder Guide ............................................................................................................................................................ 21
2.1 New Concepts .................................................................................................................................................. 21
2.1.1 Terminology Note ................................................................................................................................. 21
2.1.2 CoIDE Features..................................................................................................................................... 22
2.2 User Interface .................................................................................................................................................. 23
2.2.1 Menus and Actions................................................................................................................................ 23
2.2.2 Views .................................................................................................................................................... 26
2.2.3 Toolbar .................................................................................................................................................. 30
2.3 Project Management ........................................................................................................................................ 31
2.3.1 Creating project..................................................................................................................................... 31
2.3.2 Editing code .......................................................................................................................................... 37
2.3.3 Project Configuration............................................................................................................................ 43
2.3.4 Building project .................................................................................................................................... 47
2.3.5 Saving project to another location ........................................................................................................ 49
2.3.6 Opening an existing project .................................................................................................................. 51
2.4 Component Examples ...................................................................................................................................... 56
2.4.1 Viewing example .................................................................................................................................. 56
2.4.2 Adding example to project .................................................................................................................... 63
2.4.3 Sharing example ................................................................................................................................... 66
2.4.4 Managing example ................................................................................................................................ 72
2.5 Component Management ................................................................................................................................. 81
2.5.1 Upload a Component ............................................................................................................................ 81
2.5.2 Modify your Component ...................................................................................................................... 91
2.5.3 Delete a component .............................................................................................................................. 97
3. Debug Guide ............................................................................................................................................................ 102
3.1 Debug Configurations .................................................................................................................................... 102
3.1.1 Debugger............................................................................................................................................. 104
3.1.2 Download............................................................................................................................................ 105
3.2 Controlling debug execution .......................................................................................................................... 106
3.3 Breakpoints &Watchpoints ............................................................................................................................ 108
3.3.1 Adding Breakpoints & Watchpoint ..................................................................................................... 108
3.3.2 Removing Breakpoints & Watchpoints ............................................................................................... 110
3.3.3 Enabling and Disabling Breakpoints & Watchpoints .......................................................................... 112
3.4 Debug View ................................................................................................................................................... 114
3.4.1 Disassembly view ............................................................................................................................... 114
3.4.2 Breakpoints View ................................................................................................................................ 115
3.4.3 Registers view ..................................................................................................................................... 117
3.4.4 Memory View ..................................................................................................................................... 119
3.4.5 Variables View .................................................................................................................................... 121
3.4.6 Expressions view ................................................................................................................................ 123
3.4.7 Debug View ........................................................................................................................................ 124
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 3
2. Select chip, for example: NUC100LE3AN, the right side of CoIDE will display the corresponding
information of the chip.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 6
3. Check the components which you want to use, for example, check GPIO component. CoIDE will
promote you to create a new project.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 7
4. Input the project's name, CoIDE will create a project contained startup code and main.c file for
you. The components you selected in third step will be added to your project, too.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 8
5. Click GPIO in repository view, the detailed descriptions of GPIO component will show in help view.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 9
6. Click GPIO in component view, you can find there are some examples for this component.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 10
7. Click “add” to copy the existing example to your project. For example, add “BlinkExp”.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 11
11. Select Nulink or CoLinkEx as the adapter according to that you use.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 15
14. After launching debug successfully, CoIDE will come into debug mode.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 18
15. The initial debug UI only shows a few debug windows, you can open the other debug windows
through view menu.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 19
2. Builder Guide
Component
In CooCox CoIDE, reusable code is called component. A component can be a library, a collection of source files
and so on. It must provide useful functions, be easy to understand and use, and most importantly, can work
correctly. Each component has its corresponding code snippets, usage, documentation and comments.
Dependence
If component A calls the content of component B (known as Compilation Dependence), or component A can not
correctly execute without component B (known as Application Dependence), We call component A depends on
component B. When you check component A, CoIDE will automatically check the dependence components of
component A. One component can depend on several components, and also can be depended by multiple
components.
Code Snippet
Code Snippet is also known as example code, it is an extension of component. If the component is
object-oriented, the code snippet will be application-oriented. Example, a PIO driver can be known as a
component, a function using PIO driver to achieve LED flashing can be known as a code snippet. The code
snippet is generally very short, but the features are not restricted. It can be automatically inserted into the
code.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 22
CoIDE can be used for code editing, code browsing, compiling, linking, debugging, project management, it also
can be used to obtain components, to share components and to exchange ideas.
Component Network
Component Network contains a large amount of free components, the components are provided by CooCox and
CooCox users. CooCox has provided RTOS, flash manager, embedded database, protocol stack and other
components which are all free and open. Everyone can use these components and upload their own
components.
In embedded application development, if there is no suitable libraries, development work will become very
complicated. Once you have the suitable libraries, anything will be manipulated in your hands. CooCox CoIDE
Component Network contains a large amount of free components, users can choose suitable components
according to your own needs, and use the component code snippets to build application more quickly. With a
large number of components and detailed component documentation, programming will be as simple as
building block.
Component Documentation
Each component has a detailed documentation (displayed in the Help View), including component description,
component dependency relationship, component source files, usage of the component, comments and so on.
CoIDE automatically generates documentation for source files. If the code comment style is consistent with
doxygen, the documentation will be very detailed. And the detailed documentation allows you to use the
component more quickly.
Interaction
In order to help users to solve the problems encountered in development process, CoIDE provides a powerful
interaction function. In CooCox CoIDE, every thing can interact, such as chip, component, peripheral, register,
code snippet and so on, users can even ask questions directly to solve their problems.
Development Environment
CoIDE is based on the Eclipse development platform, it has the following features:
Integrated CDT editor: You can edit and browse the code; it is a full-featured editor.
Integrated Sourcery G++ Lite tool chain: Using gcc tool chain, which is efficient and stable.
A clear interface: Menus and toolbar are simple, clear and easy to use.
GUI Setting: Dialogs for all settings.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 23
Save the content of the current editor. Disabled if the editor does not
Save Ctrl + S
contain unsaved changes.
Save As... Save the content of the current editor under a new name.
New Project Create a new Project and close the current project.
Open Project... Show a dialog that can be used to select an existing project.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 24
Upload Open the Login dialog box, you can upload Component after
Component login with coocox account.
2.2.2 Views
Component View
This view displays all the components of the current project selection. If
you click a component in this view:
The Help view will display the properties of the clicked component,
such as the component source files, source files documents,
dependent components, usage and comments.
The Code Snippet View will display all code snippets of the
component.
The Project View will highlight the component source files.
Project View
This view displays all files of the file system under your project directory,
including C source files (*.c, *.h), assembly source files (*.s), project
configuration files (build.xml), linker script files (*.ld), library files (*.a), etc.
In this view you could do the following operations:
Open files in the editor view
Open project configuration interface
Close the current project
Create new projects, files, or folders
Manage existing files (copy, paste, delete, move or rename)
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 27
Repository View
This view consists of Manufacturers page, Chip page and Component page. In this view, you can view chip
components and manage your local or network components. When you check a component, the component and
other components depended by the checked component will be automatically checked, and the source files will
be automatically added to the project. This view can be opened by menu command View->Repository. In this
view you could do the following operations:
Help View
This view displays all information about the selected component, including:
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 28
In the Components View, click the component to open this view, this view will display all code snippets of the
clicked component. In this view you can do the following things:
Click view to view code snippet and the comments.
Click add to insert the code snippet into the project.
View more example for the chip you selected.
Upload a code snippet.
Manage your own code snippets.
Add comments.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 29
Project Explorer: Shows all of the file system's files under your project directory.
Editor: The C/C++ editor view provides specialized features for editing C/C++ related files.
Outline: Displays the structure of the file currently open in an editor.
Search: Shows the results of searches for files or text.
Console: Displays your program's output, as well as the output from your build tools.
2.2.3 Toolbar
Toolbar Actions
New Project Create a new Project and close the current project.
Last Edit Location Go to the location where you have modified last time. Ctrl + Q
2. Type a name for your project. For example, in the Project name field, type “MyFirstProject”.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 33
5. Check a component. For example, select “pio”. CoIDE will automatically check the components which the
checked component depends on.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 36
CoIDE integrates CDT Editor which is a part of CDT project of Eclipse. This section describes how to edit code in
CoIDE, if you want to get more help, you can visit eclipse cdt project home.
To edit code using CoIDE, you could perform as follows:
2. Type file name for the new file and then click Finish button.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 39
4. If necessary, right click at the left edge of editor, select Show Line Numbers to enable the function or
disable.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 41
5. If necessary, right click at the left edge of editor, select Folding > Enable Folding to enable the function
or disable.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 42
6. If necessary, move cursor to a code field then right click, select Open Declaration to open a declaration file.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 43
After creating a project, CoIDE will automatically generate a builder.xml file for the project. It contains the
project configuration. By editing the file you could configure the project. There is an interface in CoIDE to help
us to edit builder.xml file.
There are several ways to open the project configuration interface: double-click build.xml in the project view
or click Project->Configuration in CoIDE menubar.
For CoIDE projects, you can define preprocessor symbols for the parser. This makes the parser understand the
contents of the C/C++ source code so that you can more effectively use the search and code completion
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 44
features.
Add symbols in "Defined symbols" section:
For CoIDE projects, you can add include paths for the parser. This makes the parser find the header included in
the C source code so that you can more effectively use the search and code completion features.
Add symbols in "Include paths" section:
When you create a new project, you can specify the output file type. This output file type will determine the
toolchain and data, and tabs that CoIDE uses. In CooCox CoIDE, you can choose from the following output file
types:
Executable -The target file is a binary file (*.bin) that can be downloaded into the chip and run, it is
selected by default.
Library - The target file is a library file (libxx.a). It is a collection of object files
which you can link into another application.
CoIDE combines object files (i.e. *.o) into an archive (*.a) that is directly linked into an executable.
Setting optimization options makes the compiler attempt to improve the performance and/or code size at the
expense of compilation time and possibly the ability to debug the program.
Optimization - Set optimization levels, about more optimization levels, please refer to gcc documentation .
Discard unused sections - Enable garbage collection of unused input sections. The section containing the
entry symbol and all sections containing symbols undefined on the command-line will be kept, as will
sections containing symbols referenced by dynamic objects. Check this option will reduce code size.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 45
Adding Library
Library is a set of routines, external functions and variables which are resolved in a caller at compile-time and
copied into a target application by a compiler, linker, or binder, producing an object file and a stand-alone
executable. CoIDE library is a gcc library.
Add libraries file in "Linked Libraries" section.
Customize the start address and size for IROM and IRAM in "Memory Areas" section.
Customize the linker script file for current project in "Locate Link File" section.
You can add, delete and modify the Compiler and Linker options.
1. Select Project > Build. If necessary, you can select Rebuild to recompile your project or select Clean to
clean-up the project have compiled.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 48
1. If necessary, you can select Project > Close Project to close the current project.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 52
CoIDE integrates a lot of infrastructure components, in order to allow users to use these components
more easily, each component can be corresponded to multiple sample code fragment, you can view
them and add them to your project, you also could upload your own examples to the internet.
1. Click the component which shows "with x example(s)" in the Component View of CoIDE.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 57
2. The example view will appear and display all the code snippets of the selected component.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 58
5. You can click "More Example for xxx" to view more example for the selected chip.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 61
6. Other example will show in more example view based on the component classification.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 62
7. Click the example name can open the example in the edit view.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 63
2. It will popup a dialog to tell you where the example will be located in, click "yes", please.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 65
2. If you have not login, you must login first.If you don not have an account, click the link named "Get new
CooCox account?" at the bottom of Login Dialog.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 68
1. You can click "Upload Component" under the "Project" menu or the button in the Repository view.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 82
2. Login with your account, it could be the account of yours in CooCox Forum.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 83
5. Click next to save the settings of "Files" and then enter the "Tags" page.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 86
6. Edit the information about the component; you need to select the manufacture, chip, category
for the component.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 87
5. Modify the help content and click "save" in the "Saving" page.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 96
2. Right Click the component you uploaded in the Repository View, and select "Delete".
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 99
4. In the lower right corner of the CoIDE interface, you will find deleting is executing.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 101
5. Delete successfully.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 102
3. Debug Guide
Before debugging your project, you could configurate it first. Like the steps below:
3.1.1 Debugger
1. Hardware Tab:
Adapter: CoIDE supports Colink, CoLinkEx, NuLink, Olimex Open-OCD and Stellaris-ICDI these
five adapters.
Port: CoIDE supports both SWD and JTAG debugging modes.
Max Clock(Hz): You could select 2M, 1M, 500K, 300K and 100K clock here.
2. Startup Tab: You could check Run to main or not according to your needs.
3. Advance Tab:
Reset Mode: There are there reset modes for you to choose: HW RESET, VECTRESET and
SYSRESETREQ.
CacheRomEnable: Checked indicates enable ROM cache.
TargetInfo: It will show your Host Name and Port Number.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 105
3.1.2 Download
Auto Download before Debugging: Download the program to the chip automatically before
start debug.
Verify After Download: Verify the program after download it to the chip.
Erase Full Chip: Erase the full chip before downloading your program.
Erase Effected: Erase the effected sectors before downloading your program.
Do not Erase: It will not erase the chip before downloading your program.
The debug execution controls are superceded by breakpoints. For example, if you attempt to step over a
function and the program hits a breakpoint, it pauses, regardless of whether the function is completed. You can
control your debug execution in various ways, but they all rely on a core set of debug controls.
Keyboard
Icons Action Description
shortcut
Adding Breakpoints
A breakpoint can be set on an executable line of the program. If the breakpoint is enabled when you debug, the
execution will suspend before the code of that line is executed.
To add a breakpoint point, you could double-click the marker bar located in the left margin of the C/C++
Editor beside the line of code where you want to add a breakpoint. A dot will display in the marker bar and
in the Breakpoints View, along with the name of the associated file.
Adding Watchpoints
A watchpoint is a special breakpoint that stops the execution of the program whenever the value of a given
expression changes, without specifying where it might occur. Unlike breakpoints (which are line-specific),
watchpoints are associated with files. They take effect whenever a specified condition is true, regardless of
when or where it occurred. You can set a watchpoint on a global variable by highlighting the variable in the
editor.
To remove breakpoints or watchpoints, you can do anyone of the following three methods:
1. In the edit view, right click the breakpoint symbol, select Toggle Breakpoint or just double click the
breakpoint symbol.
2. In the Breakpoints view, select the breakpoints you want to remove and click Remove the selected
breakpoints button or Remove all breakpoints button.
Then right-click the highlighted breakpoints and watchpoints and click Remove or Remove all.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 112
You can temporarily disable a breakpoint or watchpoint without losing the information it contains.
To enable or disable breakpoints or watchpoints, you can do anyone of the following three methods:
1. In the edit view, right click the breakpoint symbol, select Enable Breakpoint or Disable Breakpoint
2. In the Breakpoints view, check the breakpoints and watchpoints that you want to enable or disable.
1) Select the breakpoints and watchpoints that you want to enable or disable;
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 113
Then right-click the highlighted breakpoints and watchpoints and click Disable or Enable.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 114
The Disassembly View shows the loaded program as assembler instructions mixed with source code for
comparison. The currently executing line is indicated by an arrow marker and highlighted in the view. You can
do the following tasks in the Disassembly view.
Move to
Jump to the line selected in the Disassembly view. Context menu
Line
The Breakpoints View lists all the breakpoints you have set in your workspace. Only up to six breakpoints can
be toggled if you are debugging in flash with Cortex-M3 series' chips, for Cortex-M0, the number is four.
Otherwise, warnings will be presented at runtime.
You can double-click a breakpoint to find its location in the editor (if applicable). You can also enable or disable
breakpoints, delete them, add new ones.
Expand All Expands all of the items in the view. View action
Collapse All Collapses all of the items in the view. View action
Show full paths Show the full paths of the breakpoints. View action
Import
Opens the import breakpoints wizard. Context menu
Breakpoints...
Export
Opens the export breakpoints wizard. Context menu
Breakpoints...
Breakpoint
Opens the breakpoints properties dialog. Context menu
Properties...
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 117
The Registers view of the Debug perspective lists information about the registers in a selected stack frame.
You can view information about the registers in a selected stack frame. Values that have changed are
highlighted in the Registers view when your program stops.
The table below lists the icons displayed in the Registers view toolbar:
The Memory view of the Debug perspective lets you monitor and modify your process memory. Memory can be
displayed in different predefined data formats -- memory renderings. The CoIDE supports five rendering types
-- hexadecimal (default), ascii, signed integer and unsigned integer.
The Memory view can display and modify the value of selected memory address. The Rendering pane can be
configured to display more than two renderings simultaneously.
The table below lists the icons displayed in the Memory view toolbar.
Reset To Base Address Resets the Rendering pane to the original base address.
The Variables View displays information about the variables associated with the stack frame selected in the
Debug View. When debugging a C/C++ program, data that contains variables can be expanded to show the
variables and the fields the variables contain.
You can view information about the variables in a selected stack frame in the Variables view. When execution
stops, the changed values are by default highlighted . Like the other debug-related views, the Variables view
does not refresh as you run your executable. A refresh occurs when execution stops.
Show Type Name Configure columns to show type names. view action
Show logic structure Show logic structure of the Variables. view action
Select All Selects all of the variables in the view. Context menu
An expression is a snippet of code which can be evaluated to produce a result. The context for an expression
depends on the particular debug model. Some expressions may need to be evaluated at a specific location in the
program so that the variables can be referenced. You can view information about expressions in the
Expressions view.
You can inspect expressions from a scrapbook page, a stack frame of a suspended thread, and other places. The
Expressions View opens automatically when an item is added to the view. When debugging a C/C++ program,
data that contains variables can be expanded to show the variables and the fields of the variables.
Show Type Name Configure columns to dispaly type names. view action
Show logic structure Show logic structure of the Expressions. view action
Context menu
Add Watch Expression Allows you to add a watch expression.
and view action
Removes the currently selected expression(s) Context menu
Remove
from the view. and view action
Context menu
Remove All Removes all of the expressions from the view.
and view action
Select All Selects all of the variables in the view. Context menu
Edit Watch Expression Allows you to edit exsiting watch expression. Context menu
Reevaluate
Reevaluates the currently selected expression. Context menu
Expression
Select a format type. Choices include: Binary,
Format Context menu
Decimal, Natural, and Hexadecimal.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 124
1. The Debug view shows the target debugging information in a tree hierarchy.
2. The number beside the thread label is a reference counter, not a thread identification number.
3. The CDT displays stack frames as child elements. It displays the reason for the suspension
beside the thread, (such as end of stepping range, breakpoint hit, and signal received). When a
program exits, the exit code is displayed.
The Peripherals View can be used to view and Modify the vaule of Peripherals' registers.Values that have
changed are highlighted in the Peripherals view when your program stops.
To use CoAssitant in CoIDE, you only need to perform the following steps:
3. Click the name of Peripheral to view the base address and description for this peripheral.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 129
4. Click "+" to show the register list and view the value of these registers.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 130
5. The Register that have changed are highlighted in in the Peripherals view.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 131
7. In this view, you can get the description, RW access, address offset and the reset value of the register.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 133
8. You can modify the value of register when you debug a project.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 134
4. C/C++ Views
The Project Explorer view displays in a tree structure similar to the C/C++ Projects view, but it is not limited to
C and C++ projects. In this view you can do the following things:
Files that you selected in the Project Explorer view affect the information which display in other views.
Toolbar:
Icon Description
C or C++ file
Class
Macro Definition
Enum
Enumerator
Variable
Field private
Field protected
Field public
Include
Makefile
Method private
Method protected
Method public
Namespace
Struct
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 136
Type definition
Union
Function
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 137
The Outline view displays an outline of a structured C/C++ file that is currently open in the editor area, by listing
the structural elements.
The table below lists the icons displayed in the Outline view toolbar
Icon Description
Hide Fields
The table below lists the icons displayed in the Outline view.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 138
Icon Description
Class
Namespace
Macro Definition
Enum
Enumerator
Variable
Field private
Field protected
Field public
Include
Method private
Method protected
Method public
Struct
Type definition
Union
Function
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 139
This view shows the output of the execution of your program and enables you to enter input for the program.
The console shows three different kinds of text, each is in a different color, default as follows:
You can choose the different colors for these kinds of text in the preferences pages (Window > Preferences >
Debug > Console).
When you right-click in the Console view (or when you press Shift+F10 when the focus is on the Console view),
you could see the following options:
These options perform the standard edit operations. Which options are available depends on where the focus is
in the Console view. For example, you cannot paste text into the program output, but you can paste text to the
bottom of the file.
Find/Replace
Open a Find/Replace dialog, which operate only on the text in the Console view.
When you have completed a search and have results in the Search view, you can put the focus on that view and
get more options on the Search menu.
A C/C++ search can also be conducted via the context menu of selected resources and elements in the following
views:
Outline view
Search result view
The search context menu is also available in the C/C++ editor. The search is only performed if the currently
selected text can be resolved to a C/C++ element.
The type of the selected C/C++ element defines which search context menus are available. The C/C++ editor
does not constrain the list of available C/C++ searches based on the selection.
Run the Current Search Again Run the current search again.
The C/C++ editor provides specialized features for editing C/C++ related files.
Associated with the editor is a C/C++-specific Outline view, which shows the structure of the active C, C++ . It
will update when you edit these files.
1. Syntax highlighting
2. Content/code assist
3. Integrated debugging features
The most common way to invoke the C/C++ editor is to open a file from the Project Explorer by clicking the file
(single or double-click depending on the user preferences).
The C/C++ editor does not contain a toolbar itself, but relies on the use of the context menu (right click your
mouse in the editor view , the context menu will be presented) and key binding actions.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 144
You can get CoIDE's version information from the Help menu, also you can get its User guide from this menu.
1. You can open the help contents by clicking Help Contents under the Help menu.
CooCox CoIDE UserGuide Version: 1.2.2 2011-3-4 page 145
Toolbar Actions