Code::Blocks - User contributions [en]

Code::Blocks SDK events

2010-08-22T16:05:25Z

Mariocup: /* Events that must be registered with RegisterEventSink */

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
During a Code::Blocks session, many things are happening: projects/files loading, closing, activating, saving, etc. These are interesting things that happen and various parts of Code::Blocks and its plugins are interested in them.
The Code::Blocks SDK provides functions that allow a part of the code to be "subscribed" to these events (i.e. be notified when they happen). This is what we 'll look at in this article.

''Note: since mid-November 2007, loggers registration is handled with events too.''

=== Available events ===
There are many event constants defined for the interesting events that happens inside Code::Blocks. These constants are defined in <tt>include/sdk_events.h</tt> and listed at the bottom of this page.

Also note that there 4 different event categories:
* Logging system related (CodeBlocksLogEvent)
* View layout related (CodeBlocksLayoutEvent)
* Docking system related (CodeBlocksDockEvent)
* and everything else (CodeBlocksEvent)

=== Subscribing to events ===
Up until July 6th (2007), Code::Blocks events were handled like other wxWidgets events: by declaring an event table in your class that should handle them and adding relevant event table entries.

But the event system changed radically on July 6th (2007), in order to battle some shortcomings of the wxWidgets event system (at least for our usage). While designing the new system, great attention has been paid so that plugin writers have to do minimum changes to convert their code.

The class that handles all event registrations is the central class in Code::Blocks which you use if you want to do anything with the Code::Blocks SDK: <tt>Manager</tt>. Let's see by example how would a class (e.g. <tt>SomePlugin</tt>) subscribe for the cbEVT_EDITOR_SAVE event (fired when an editor's contents are saved):

// assuming an existing member function:
// void SomePlugin::OnEditorSaved(CodeBlocksEvent& event);

Manager::Get()->RegisterEventSink(cbEVT_EDITOR_SAVE, new cbEventFunctor<SomePlugin, CodeBlocksEvent>(this, &SomePlugin::OnEditorSaved));

Seems difficult? It isn't, if you realize what the second argument to <tt>Manager::RegisterEventSink</tt> does.

<tt>cbEventFunctor</tt> is a class that encapsulates a this-pointer call. It is like a C function pointer except that it works with class instances (i.e. a member-function pointer).
For obvious reasons it is a template class, taking two template arguments: the first is the class' name and the second is the type of the event the member function handles.

The constructor of <tt>cbEventFunctor</tt> takes two arguments: first is the class instance (we use the <tt>this</tt> pointer) and the second is the address of the member function.

And that's it. After using the above code, the defined function will be called-back on each editor saving :).

'''Important note:''' For various reasons, cbEVT_PIPEDPROCESS* and cbEVT_THREADEDTASK* events should still be bound using the old way (i.e. by adding event table entries). If this is changed in the future, this article will be updated accordingly.

=== Unsubscribing from events ===
Usually there is no need to unsubscribe from event notifications. A plugin, for example, is automatically removed from all event notifications when it is detached (deactivated, unloaded, uninstalled).

But if you really think you need to unsubscribe from events, there is a function to do that: <tt>Manager::Get()->RemoveAllEventSinksFor(void* owner)</tt>. As the sole argument, pass the instance that you registered the events in the first place.

Notice that this function will remove ''all event notifications'' for the specified instance. There is no way to remove event notifications selectively. It's an all-or-nothing deal...

=== When to register/unregister for event notifications? ===
In plugins, event notifications should be registered in <tt>OnAttach()</tt>. As mentioned above, there is no need to unregister anything in <tt>OnDetach()</tt> because it is automatically done by Code::Blocks.

For code other than plugins, register whenever you think is better (depends on the actual code).

Also notice that Code::Blocks removes all registrations on shut down, so don't even think that we have memory leaks in that part ;).

=== Any examples? ===
If the example provided above is not enough, browse through the sources of the core/contrib Code::Blocks plugins. A few of them register for events: just search the code for <tt>RegisterEventSink</tt>.
But it really is nothing difficult: just remove the event handlers from the class's event table and register with this new way.

=== List of Available Code::Blocks Events ===

==== Events that must be registered with RegisterEventSink ====
''app events''
* cbEVT_APP_STARTUP_DONE
* cbEVT_APP_START_SHUTDOWN
* <strike>cbEVT_APP_UPDATE_TITLE</strike> (removed)

''plugin events'' (CodeBlocksEvent)
* cbEVT_PLUGIN_ATTACHED
* cbEVT_PLUGIN_RELEASED
* cbEVT_PLUGIN_INSTALLED
* cbEVT_PLUGIN_UNINSTALLED

''editor events'' (CodeBlocksEvent)
* cbEVT_EDITOR_CLOSE
* cbEVT_EDITOR_OPEN
* cbEVT_EDITOR_ACTIVATED
* cbEVT_EDITOR_DEACTIVATED
* cbEVT_EDITOR_SAVE
* cbEVT_EDITOR_MODIFIED
* cbEVT_EDITOR_TOOLTIP
* cbEVT_EDITOR_TOOLTIP_CANCEL
* cbEVT_EDITOR_BREAKPOINT_ADD
* cbEVT_EDITOR_BREAKPOINT_EDIT
* cbEVT_EDITOR_BREAKPOINT_DELETE
* cbEVT_EDITOR_UPDATE_UI
* cbEVT_EDITOR_SWITCHED

''project events'' (CodeBlocksEvent)
* cbEVT_PROJECT_CLOSE
* cbEVT_PROJECT_OPEN
* cbEVT_PROJECT_SAVE
* cbEVT_PROJECT_ACTIVATE
* cbEVT_PROJECT_BEGIN_ADD_FILES
* cbEVT_PROJECT_END_ADD_FILES
* cbEVT_PROJECT_BEGIN_REMOVE_FILES
* cbEVT_PROJECT_END_REMOVE_FILES
* cbEVT_PROJECT_FILE_ADDED
* cbEVT_PROJECT_FILE_REMOVED
* cbEVT_PROJECT_POPUP_MENU
* cbEVT_PROJECT_TARGETS_MODIFIED
* cbEVT_PROJECT_RENAMED
* cbEVT_PROJECT_FILE_CHANGED
* cbEVT_CLEAN_PROJECT_STARTED
* cbEVT_WORKSPACE_CHANGED
* cbEVT_CLEAN_WORKSPACE_STARTED

''main menubar creation'' (CodeBlocksEvent)
* cbEVT_MENUBAR_CREATE_BEGIN: app notifies that the menubar is started being (re)created
* cbEVT_MENUBAR_CREATE_END: app notifies that the menubar (re)creation ended

''compiler-related events'' (CodeBlocksEvent)
* cbEVT_COMPILER_STARTED
* cbEVT_COMPILER_FINISHED

''debugger-related events'' (CodeBlocksEvent)
* cbEVT_DEBUGGER_STARTED
* cbEVT_DEBUGGER_PAUSED
* cbEVT_DEBUGGER_FINISHED

''logging-system related events'' (CodeBlocksLogEvent)
* cbEVT_ADD_LOG_WINDOW: add a log window
* cbEVT_REMOVE_LOG_WINDOW: remove a log window
* cbEVT_SWITCH_TO_LOG_WINDOW: switch to a log window (make it visible)
* cbEVT_SHOW_LOG_MANAGER: show log manager
* cbEVT_HIDE_LOG_MANAGER: hide log manager
* cbEVT_LOCK_LOG_MANAGER: "lock" it (used with auto-hiding functionality)
* cbEVT_UNLOCK_LOG_MANAGER: "unlock" it (used with auto-hiding functionality)

''dockable windows'' (CodeBlocksDockEvent)
* cbEVT_ADD_DOCK_WINDOW: request app to add and manage a docked window
* cbEVT_REMOVE_DOCK_WINDOW: request app to stop managing a docked window
* cbEVT_SHOW_DOCK_WINDOW: request app to show a docked window
* cbEVT_HIDE_DOCK_WINDOW: request app to hide a docked window
* cbEVT_DOCK_WINDOW_VISIBILITY: app notifies that a docked window has been hidden/shown to actually find out its state use IsWindowReallyShown(event.pWindow);

''layout related events'' (CodeBlocksLayoutEvent)
* cbEVT_SWITCH_VIEW_LAYOUT: request app to switch view layout
* cbEVT_SWITCHED_VIEW_LAYOUT: app notifies that a new layout has been applied

==== Events processed on wxWidgets event tables and '''not''' registered using RegisterEventSink ====
''pipedprocess events'' (CodeBlocksEvent)
* cbEVT_PIPEDPROCESS_STDOUT
* cbEVT_PIPEDPROCESS_STDERR
* cbEVT_PIPEDPROCESS_TERMINATED

''thread-pool events'' (CodeBlocksEvent)
* cbEVT_THREADTASK_STARTED
* cbEVT_THREADTASK_ENDED
* cbEVT_THREADTASK_ALLDONE

[[User:Mandrav|Mandrav]] 10:31, 23 November 2007 (UTC)

Code::Blocks SDK events

2010-08-22T16:04:34Z

Mariocup: /* Events that must be registered with RegisterEventSink */

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
During a Code::Blocks session, many things are happening: projects/files loading, closing, activating, saving, etc. These are interesting things that happen and various parts of Code::Blocks and its plugins are interested in them.
The Code::Blocks SDK provides functions that allow a part of the code to be "subscribed" to these events (i.e. be notified when they happen). This is what we 'll look at in this article.

''Note: since mid-November 2007, loggers registration is handled with events too.''

=== Available events ===
There are many event constants defined for the interesting events that happens inside Code::Blocks. These constants are defined in <tt>include/sdk_events.h</tt> and listed at the bottom of this page.

Also note that there 4 different event categories:
* Logging system related (CodeBlocksLogEvent)
* View layout related (CodeBlocksLayoutEvent)
* Docking system related (CodeBlocksDockEvent)
* and everything else (CodeBlocksEvent)

=== Subscribing to events ===
Up until July 6th (2007), Code::Blocks events were handled like other wxWidgets events: by declaring an event table in your class that should handle them and adding relevant event table entries.

But the event system changed radically on July 6th (2007), in order to battle some shortcomings of the wxWidgets event system (at least for our usage). While designing the new system, great attention has been paid so that plugin writers have to do minimum changes to convert their code.

The class that handles all event registrations is the central class in Code::Blocks which you use if you want to do anything with the Code::Blocks SDK: <tt>Manager</tt>. Let's see by example how would a class (e.g. <tt>SomePlugin</tt>) subscribe for the cbEVT_EDITOR_SAVE event (fired when an editor's contents are saved):

// assuming an existing member function:
// void SomePlugin::OnEditorSaved(CodeBlocksEvent& event);

Manager::Get()->RegisterEventSink(cbEVT_EDITOR_SAVE, new cbEventFunctor<SomePlugin, CodeBlocksEvent>(this, &SomePlugin::OnEditorSaved));

Seems difficult? It isn't, if you realize what the second argument to <tt>Manager::RegisterEventSink</tt> does.

<tt>cbEventFunctor</tt> is a class that encapsulates a this-pointer call. It is like a C function pointer except that it works with class instances (i.e. a member-function pointer).
For obvious reasons it is a template class, taking two template arguments: the first is the class' name and the second is the type of the event the member function handles.

The constructor of <tt>cbEventFunctor</tt> takes two arguments: first is the class instance (we use the <tt>this</tt> pointer) and the second is the address of the member function.

And that's it. After using the above code, the defined function will be called-back on each editor saving :).

'''Important note:''' For various reasons, cbEVT_PIPEDPROCESS* and cbEVT_THREADEDTASK* events should still be bound using the old way (i.e. by adding event table entries). If this is changed in the future, this article will be updated accordingly.

=== Unsubscribing from events ===
Usually there is no need to unsubscribe from event notifications. A plugin, for example, is automatically removed from all event notifications when it is detached (deactivated, unloaded, uninstalled).

But if you really think you need to unsubscribe from events, there is a function to do that: <tt>Manager::Get()->RemoveAllEventSinksFor(void* owner)</tt>. As the sole argument, pass the instance that you registered the events in the first place.

Notice that this function will remove ''all event notifications'' for the specified instance. There is no way to remove event notifications selectively. It's an all-or-nothing deal...

=== When to register/unregister for event notifications? ===
In plugins, event notifications should be registered in <tt>OnAttach()</tt>. As mentioned above, there is no need to unregister anything in <tt>OnDetach()</tt> because it is automatically done by Code::Blocks.

For code other than plugins, register whenever you think is better (depends on the actual code).

Also notice that Code::Blocks removes all registrations on shut down, so don't even think that we have memory leaks in that part ;).

=== Any examples? ===
If the example provided above is not enough, browse through the sources of the core/contrib Code::Blocks plugins. A few of them register for events: just search the code for <tt>RegisterEventSink</tt>.
But it really is nothing difficult: just remove the event handlers from the class's event table and register with this new way.

=== List of Available Code::Blocks Events ===

==== Events that must be registered with RegisterEventSink ====
''app events''
* cbEVT_APP_STARTUP_DONE
* cbEVT_APP_START_SHUTDOWN
* <strike>cbEVT_APP_UPDATE_TITLE</strike> (removed)

''plugin events'' (CodeBlocksEvent)
* cbEVT_PLUGIN_ATTACHED
* cbEVT_PLUGIN_RELEASED
* cbEVT_PLUGIN_INSTALLED
* cbEVT_PLUGIN_UNINSTALLED

''editor events'' (CodeBlocksEvent)
* cbEVT_EDITOR_CLOSE
* cbEVT_EDITOR_OPEN
* cbEVT_EDITOR_ACTIVATED
* cbEVT_EDITOR_DEACTIVATED
* cbEVT_EDITOR_SAVE
* cbEVT_EDITOR_MODIFIED
* cbEVT_EDITOR_TOOLTIP
* cbEVT_EDITOR_TOOLTIP_CANCEL
* cbEVT_EDITOR_BREAKPOINT_ADD
* cbEVT_EDITOR_BREAKPOINT_EDIT
* cbEVT_EDITOR_BREAKPOINT_DELETE
* cbEVT_EDITOR_UPDATE_UI
* cbEVT_EDITOR_SWITCHED

''project events'' (CodeBlocksEvent)
* cbEVT_PROJECT_CLOSE
* cbEVT_PROJECT_OPEN
* cbEVT_PROJECT_SAVE
* cbEVT_PROJECT_ACTIVATE
* cbEVT_PROJECT_BEGIN_ADD_FILES
* cbEVT_PROJECT_END_ADD_FILES
* cbEVT_PROJECT_BEGIN_REMOVE_FILES
* cbEVT_PROJECT_END_REMOVE_FILES
* cbEVT_PROJECT_FILE_ADDED
* cbEVT_PROJECT_FILE_REMOVED
* cbEVT_PROJECT_POPUP_MENU
* cbEVT_PROJECT_TARGETS_MODIFIED
* cbEVT_PROJECT_RENAMED
* cbEVT_WORKSPACE_CHANGED
* cbEVT_PROJECT_FILE_CHANGED
* cbEVT_CLEAN_PROJECT_STARTED
* cbEVT_CLEAN_WORKSPACE_STARTED

''main menubar creation'' (CodeBlocksEvent)
* cbEVT_MENUBAR_CREATE_BEGIN: app notifies that the menubar is started being (re)created
* cbEVT_MENUBAR_CREATE_END: app notifies that the menubar (re)creation ended

''compiler-related events'' (CodeBlocksEvent)
* cbEVT_COMPILER_STARTED
* cbEVT_COMPILER_FINISHED

''debugger-related events'' (CodeBlocksEvent)
* cbEVT_DEBUGGER_STARTED
* cbEVT_DEBUGGER_PAUSED
* cbEVT_DEBUGGER_FINISHED

''logging-system related events'' (CodeBlocksLogEvent)
* cbEVT_ADD_LOG_WINDOW: add a log window
* cbEVT_REMOVE_LOG_WINDOW: remove a log window
* cbEVT_SWITCH_TO_LOG_WINDOW: switch to a log window (make it visible)
* cbEVT_SHOW_LOG_MANAGER: show log manager
* cbEVT_HIDE_LOG_MANAGER: hide log manager
* cbEVT_LOCK_LOG_MANAGER: "lock" it (used with auto-hiding functionality)
* cbEVT_UNLOCK_LOG_MANAGER: "unlock" it (used with auto-hiding functionality)

''dockable windows'' (CodeBlocksDockEvent)
* cbEVT_ADD_DOCK_WINDOW: request app to add and manage a docked window
* cbEVT_REMOVE_DOCK_WINDOW: request app to stop managing a docked window
* cbEVT_SHOW_DOCK_WINDOW: request app to show a docked window
* cbEVT_HIDE_DOCK_WINDOW: request app to hide a docked window
* cbEVT_DOCK_WINDOW_VISIBILITY: app notifies that a docked window has been hidden/shown to actually find out its state use IsWindowReallyShown(event.pWindow);

''layout related events'' (CodeBlocksLayoutEvent)
* cbEVT_SWITCH_VIEW_LAYOUT: request app to switch view layout
* cbEVT_SWITCHED_VIEW_LAYOUT: app notifies that a new layout has been applied

==== Events processed on wxWidgets event tables and '''not''' registered using RegisterEventSink ====
''pipedprocess events'' (CodeBlocksEvent)
* cbEVT_PIPEDPROCESS_STDOUT
* cbEVT_PIPEDPROCESS_STDERR
* cbEVT_PIPEDPROCESS_TERMINATED

''thread-pool events'' (CodeBlocksEvent)
* cbEVT_THREADTASK_STARTED
* cbEVT_THREADTASK_ENDED
* cbEVT_THREADTASK_ALLDONE

[[User:Mandrav|Mandrav]] 10:31, 23 November 2007 (UTC)

Variable expansion

2010-02-15T21:39:36Z

Mariocup: /* Files and directories */

[[Category:User Documentation]]

== Syntax ==
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:

* <code>$VARIABLE</code>
* <code>$(VARIABLE)</code>
* <code>${VARIABLE}</code>
* <code>%VARIABLE%</code>

Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global user variables]].
The names listed below are interpreted as builtin types.

Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.

'''Per-target definitions have precedence over per-project definitions.'''

== List of available builtins ==

=== Code::Blocks workspace ===

<code>$(WORKSPACE_FILENAME)</code>, <code>$(WORKSPACE_FILE_NAME)</code>, <code>$(WORKSPACEFILE)</code>, <code>$(WORKSPACEFILENAME)</code>
:The filename of the current workspace project (.workspace).

<code>$(WORKSPACENAME)</code>, <code>$(WORKSPACE_NAME)</code>
:The name of the workspace that is displayed in the tab Projects of the Management panel.

<code>$(WORKSPACE_DIR)</code>, <code>$(WORKSPACE_DIRECTORY)</code>, <code>$(WORKSPACEDIR)</code>, <code>$(WORKSPACEDIRECTORY)</code>
:The location of the workspace directory.

=== Files and directories ===

<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>
:The filename of the currently compiling project.

<code>$(PROJECT_NAME)</code>
:The name of the currently compiling project.

<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>
:The common top-level directory of the currently compiling project.

<code>$(ACTIVE_EDITOR_FILENAME)</code>
:The filename of the file opened in the currently active editor.

<code>$(ACTIVE_EDITOR_LINE)</code>
:Return the current line in the active editor.

<code>$(ACTIVE_EDITOR_COLUMN)</code>
:Return the column of the current line in the active editor.

<code>$(ACTIVE_EDITOR_DIRNAME)</code>
:Currently active file's containing directory (relative to the common top level path)

<code>$(ACTIVE_EDITOR_STEM)</code>
:Currently active file's base name (without extension).

<code>$(ACTIVE_EDITOR_EXT)</code>
:Currently active file's extension.

<code>$(ALL_PROJECT_FILES)</code>
:A string containing the names of all files in the current project.

<code>$(MAKEFILE)</code>
:The filename of the makefile.

<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code>
:The path to the currently running instance of Code::Blocks

<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code>
:The 'shared' directory of the currently running instance of Code::Blocks

<code>$(PLUGINS)</code>
:The 'plugins' directory of the currently running instance of Code::Blocks

<code>$(TARGET_COMPILER_DIR)</code>
:The compiler installation directory so-called master path.

=== Build targets ===

<code>$(FOOBAR_OUTPUT_FILE)</code>
:A ''specific'' target's output file.

<code>$(FOOBAR_OUTPUT_DIR)</code>
:A ''specific'' target's output directory.

<code>$(FOOBAR_OUTPUT_BASENAME)</code>
:A ''specific'' target's output file's base name (no path, no extension).

<code>$(TARGET_OUTPUT_DIR)</code>
:The ''current'' target's output directory.

<code>$(TARGET_OBJECT_DIR)</code>
:The ''current'' target's object directory.

<code>$(TARGET_NAME)</code>
:The ''current'' target's name.

<code>$(TARGET_OUTPUT_FILE)</code>
:The ''current'' target's output file.

<code>$(TARGET_OUTPUT_BASENAME)</code>
:The ''current'' target's output file's base name (no path, no extension).

<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code>
:The ''current'' target's build tool executable (compiler, linker, etc).

=== Language and encoding ===

<code>$(LANGUAGE)</code>
:The system language in human readable form.

<code>$(ENCODING)</code>
:The character encoding in human readable form.

=== Time and date ===

<code>$(TDAY)</code>
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)

<code>$(TODAY)</code>
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)

<code>$(NOW)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)

<code>$(NOW_L)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)

<code>$(WEEKDAY)</code>
:Human-readable day of the week (for example "Wednesday")

<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code>
:These are identical to the preceding types, but are expressed relative to UTC.

<code>$(DAYCOUNT)</code>
:The number of the days passed since an arbitrarily chosen day zero (January 1, 2009). Useful as last component of a version/build number.

=== Random values ===

<code>$(COIN)</code>
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.

<code>$(RANDOM)</code>
:A 16bit positive random number (0-65535)

=== Conditional Evaluation ===

<code>$if(condition){true clause}{false clause}</code>
:Conditional evaluation will resolve to its <tt>true clause</tt> if
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)
:Conditional evaluation will resolve to its <tt>false clause</tt> if
::<tt>condition</tt> is empty
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt>

Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.

=== Script expansion ===

:For maximum flexibility, you can embed scripts using the <tt>[[</tt> <tt>]]</tt> operator as a special case of variable expansion. Embedded scripts have access to all standard functionality available to scrips and work pretty much like <tt>bash</tt> backticks (except for having access to Code::Blocks' namespace). As such, scripts are not limited to producing text output, but can also manipulate Code::Blocks state (projects, targets, etc.). Although this is technically possible, it is generally bad design and a very stupid idea to do so. Manipulating Code::Blocks state from a pre-build script is a much better solution. 

:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.

:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.

:Example: 
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt> 
:inserts the active project's title into the command line.

Variable expansion

2010-01-01T11:05:04Z

Mariocup: /* Files and directories */

[[Category:User Documentation]]

== Syntax ==
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:

* <code>$VARIABLE</code>
* <code>$(VARIABLE)</code>
* <code>${VARIABLE}</code>
* <code>%VARIABLE%</code>

Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global user variables]].
The names listed below are interpreted as builtin types.

Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.

'''Per-target definitions have precedence over per-project definitions.'''

== List of available builtins ==

=== Code::Blocks workspace ===

<code>$(WORKSPACE_FILENAME)</code>, <code>$(WORKSPACE_FILE_NAME)</code>, <code>$(WORKSPACEFILE)</code>, <code>$(WORKSPACEFILENAME)</code>
:The filename of the current workspace project (.workspace).

<code>$(WORKSPACENAME)</code>, <code>$(WORKSPACE_NAME)</code>
:The name of the workspace that is displayed in the tab Projects of the Management panel.

<code>$(WORKSPACE_DIR)</code>, <code>$(WORKSPACE_DIRECTORY)</code>, <code>$(WORKSPACEDIR)</code>, <code>$(WORKSPACEDIRECTORY)</code>
:The location of the workspace directory.

=== Files and directories ===

<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>
:The filename of the currently compiling project.

<code>$(PROJECT_NAME)</code>
:The name of the currently compiling project.

<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>
:The common top-level directory of the currently compiling project.

<code>$(ACTIVE_EDITOR_FILENAME)</code>
:The filename of the file opened in the currently active editor.

<code>$(ACTIVE_EDITOR_DIRNAME)</code>
:Currently active file's containing directory (relative to the common top level path)

<code>$(ACTIVE_EDITOR_STEM)</code>
:Currently active file's base name (without extension).

<code>$(ACTIVE_EDITOR_EXT)</code>
:Currently active file's extension.

<code>$(ALL_PROJECT_FILES)</code>
:A string containing the names of all files in the current project.

<code>$(MAKEFILE)</code>
:The filename of the makefile.

<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code>
:The path to the currently running instance of Code::Blocks

<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code>
:The 'shared' directory of the currently running instance of Code::Blocks

<code>$(PLUGINS)</code>
:The 'plugins' directory of the currently running instance of Code::Blocks

<code>$(TARGET_COMPILER_DIR)</code>
:The compiler installation directory so-called master path.

=== Build targets ===

<code>$(FOOBAR_OUTPUT_FILE)</code>
:A ''specific'' target's output file.

<code>$(FOOBAR_OUTPUT_DIR)</code>
:A ''specific'' target's output directory.

<code>$(FOOBAR_OUTPUT_BASENAME)</code>
:A ''specific'' target's output file's base name (no path, no extension).

<code>$(TARGET_OUTPUT_DIR)</code>
:The ''current'' target's output directory.

<code>$(TARGET_OBJECT_DIR)</code>
:The ''current'' target's object directory.

<code>$(TARGET_NAME)</code>
:The ''current'' target's name.

<code>$(TARGET_OUTPUT_FILE)</code>
:The ''current'' target's output file.

<code>$(TARGET_OUTPUT_BASENAME)</code>
:The ''current'' target's output file's base name (no path, no extension).

<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code>
:The ''current'' target's build tool executable (compiler, linker, etc).

=== Language and encoding ===

<code>$(LANGUAGE)</code>
:The system language in human readable form.

<code>$(ENCODING)</code>
:The character encoding in human readable form.

=== Time and date ===

<code>$(TDAY)</code>
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)

<code>$(TODAY)</code>
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)

<code>$(NOW)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)

<code>$(NOW_L)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)

<code>$(WEEKDAY)</code>
:Human-readable day of the week (for example "Wednesday")

<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code>
:These are identical to the preceding types, but are expressed relative to UTC.

<code>$(DAYCOUNT)</code>
:The number of the days passed since an arbitrarily chosen day zero (January 1, 2009). Useful as last component of a version/build number.

=== Random values ===

<code>$(COIN)</code>
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.

<code>$(RANDOM)</code>
:A 16bit positive random number (0-65535)

=== Conditional Evaluation ===

<code>$if(condition){true clause}{false clause}</code>
:Conditional evaluation will resolve to its <tt>true clause</tt> if
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)
:Conditional evaluation will resolve to its <tt>false clause</tt> if
::<tt>condition</tt> is empty
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt>

Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.

=== Script expansion ===

:For maximum flexibility, you can embed scripts using the <tt>[[</tt> <tt>]]</tt> operator as a special case of variable expansion. Embedded scripts have access to all standard functionality available to scrips and work pretty much like <tt>bash</tt> backticks (except for having access to Code::Blocks' namespace). As such, scripts are not limited to producing text output, but can also manipulate Code::Blocks state (projects, targets, etc.). Although this is technically possible, it is generally bad design and a very stupid idea to do so. Manipulating Code::Blocks state from a pre-build script is a much better solution. 

:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.

:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.

:Example: 
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt> 
:inserts the active project's title into the command line.

Variable expansion

2009-01-16T11:16:57Z

Mariocup: /* Code::Blocks workspace */

[[Category:User Documentation]]

== Syntax ==
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:

* <code>$VARIABLE</code>
* <code>$(VARIABLE)</code>
* <code>${VARIABLE}</code>
* <code>%VARIABLE%</code>

Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global user variables]].
The names listed below are interpreted as builtin types.

Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.

'''Per-target definitions have precedence over per-project definitions.'''

== List of available builtins ==

=== Code::Blocks workspace ===

<code>$(WORKSPACE_FILENAME)</code>, <code>$(WORKSPACE_FILE_NAME)</code>, <code>$(WORKSPACEFILE)</code>, <code>$(WORKSPACEFILENAME)</code>
:The filename of the current workspace project (.workspace).

<code>$(WORKSPACENAME)</code>, <code>$(WORKSPACE_NAME)</code>
:The name of the workspace that is displayed in the tab Projects of the Management panel.

<code>$(WORKSPACE_DIR)</code>, <code>$(WORKSPACE_DIRECTORY)</code>, <code>$(WORKSPACEDIR)</code>, <code>$(WORKSPACEDIRECTORY)</code>
:The location of the workspace directory.

=== Files and directories ===

<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>
:The filename of the currently compiling project.

<code>$(PROJECT_NAME)</code>
:The name of the currently compiling project.

<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>
:The common top-level directory of the currently compiling project.

<code>$(ACTIVE_EDITOR_FILENAME)</code>
:The filename of the file opened in the currently active editor.

<code>$(ACTIVE_EDITOR_DIRNAME)</code>
:Currently active file's containing directory (relative to the common top level path)

<code>$(ACTIVE_EDITOR_STEM)</code>
:Currently active file's base name (without extension).

<code>$(ACTIVE_EDITOR_EXT)</code>
:Currently active file's extension.

<code>$(ALL_PROJECT_FILES)</code>
:A string containing the names of all files in the current project.

<code>$(MAKEFILE)</code>
:The filename of the makefile.

<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code>
:The path to the currently running instance of Code::Blocks

<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code>
:The 'shared' directory of the currently running instance of Code::Blocks

<code>$(PLUGINS)</code>
:The 'plugins' directory of the currently running instance of Code::Blocks

=== Build targets ===

<code>$(FOOBAR_OUTPUT_FILE)</code>
:A ''specific'' target's output file.

<code>$(FOOBAR_OUTPUT_DIR)</code>
:A ''specific'' target's output directory.

<code>$(FOOBAR_OUTPUT_BASENAME)</code>
:A ''specific'' target's output file's base name (no path, no extension).

<code>$(TARGET_OUTPUT_DIR)</code>
:The ''current'' target's output directory.

<code>$(TARGET_OBJECT_DIR)</code>
:The ''current'' target's object directory.

<code>$(TARGET_NAME)</code>
:The ''current'' target's name.

<code>$(TARGET_OUTPUT_FILE)</code>
:The ''current'' target's output file.

<code>$(TARGET_OUTPUT_BASENAME)</code>
:The ''current'' target's output file's base name (no path, no extension).

<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code>
:The ''current'' target's build tool executable (compiler, linker, etc).

=== Language and encoding ===

<code>$(LANGUAGE)</code>
:The system language in human readable form.

<code>$(ENCODING)</code>
:The character encoding in human readable form.

=== Time and date ===

<code>$(TDAY)</code>
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)

<code>$(TODAY)</code>
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)

<code>$(NOW)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)

<code>$(NOW_L)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)

<code>$(WEEKDAY)</code>
:Human-readable day of the week (for example "Wednesday")

<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code>
:These are identical to the preceding types, but are expressed relative to UTC.

=== Random values ===

<code>$(COIN)</code>
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.

<code>$(RANDOM)</code>
:A 16bit positive random number (0-65535)

=== Conditional Evaluation ===

<code>$if(condition){true clause}{false clause}</code>
:Conditional evaluation will resolve to its <tt>true clause</tt> if
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)
:Conditional evaluation will resolve to its <tt>false clause</tt> if
::<tt>condition</tt> is empty
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt>

Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.

=== Script expansion ===

:For maximum flexibility, you can embed scripts using the <tt>[[</tt> <tt>]]</tt> operator as a special case of variable expansion. Embedded scripts have access to all standard functionality available to scrips and work pretty much like <tt>bash</tt> backticks (except for having access to Code::Blocks' namespace). As such, scripts are not limited to producing text output, but can also manipulate Code::Blocks state (projects, targets, etc.). Although this is technically possible, it is generally bad design and a very stupid idea to do so. Manipulating Code::Blocks state from a pre-build script is a much better solution. 

:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.

:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.

:Example: 
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt> 
:inserts the active project's title into the command line.

Variable expansion

2009-01-16T11:09:17Z

Mariocup: /* List of available builtins */

[[Category:User Documentation]]

== Syntax ==
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:

* <code>$VARIABLE</code>
* <code>$(VARIABLE)</code>
* <code>${VARIABLE}</code>
* <code>%VARIABLE%</code>

Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global user variables]].
The names listed below are interpreted as builtin types.

Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.

'''Per-target definitions have precedence over per-project definitions.'''

== List of available builtins ==

=== Code::Blocks workspace ===

<code>$(WORKSPACE_FILENAME)</code>, <code>$(WORKSPACE_FILE_NAME)</code>, <code>$(WORKSPACEFILE)</code>, <code>$(WORKSPACEFILENAME)</code>
:The filename of the current workspace project (.workspace).

<code>$(WORKSPACENAME)</code>, <code>$(WORKSPACE_NAME)</code>
:The name of the workspace that is displayed in the Management panel.

<code>$(WORKSPACE_DIR)</code>, <code>$(WORKSPACE_DIRECTORY)</code>, <code>$(WORKSPACEDIR)</code>, <code>$(WORKSPACEDIRECTORY)</code>
:The location of the workspace directory.

=== Files and directories ===

<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>
:The filename of the currently compiling project.

<code>$(PROJECT_NAME)</code>
:The name of the currently compiling project.

<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>
:The common top-level directory of the currently compiling project.

<code>$(ACTIVE_EDITOR_FILENAME)</code>
:The filename of the file opened in the currently active editor.

<code>$(ACTIVE_EDITOR_DIRNAME)</code>
:Currently active file's containing directory (relative to the common top level path)

<code>$(ACTIVE_EDITOR_STEM)</code>
:Currently active file's base name (without extension).

<code>$(ACTIVE_EDITOR_EXT)</code>
:Currently active file's extension.

<code>$(ALL_PROJECT_FILES)</code>
:A string containing the names of all files in the current project.

<code>$(MAKEFILE)</code>
:The filename of the makefile.

<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code>
:The path to the currently running instance of Code::Blocks

<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code>
:The 'shared' directory of the currently running instance of Code::Blocks

<code>$(PLUGINS)</code>
:The 'plugins' directory of the currently running instance of Code::Blocks

=== Build targets ===

<code>$(FOOBAR_OUTPUT_FILE)</code>
:A ''specific'' target's output file.

<code>$(FOOBAR_OUTPUT_DIR)</code>
:A ''specific'' target's output directory.

<code>$(FOOBAR_OUTPUT_BASENAME)</code>
:A ''specific'' target's output file's base name (no path, no extension).

<code>$(TARGET_OUTPUT_DIR)</code>
:The ''current'' target's output directory.

<code>$(TARGET_OBJECT_DIR)</code>
:The ''current'' target's object directory.

<code>$(TARGET_NAME)</code>
:The ''current'' target's name.

<code>$(TARGET_OUTPUT_FILE)</code>
:The ''current'' target's output file.

<code>$(TARGET_OUTPUT_BASENAME)</code>
:The ''current'' target's output file's base name (no path, no extension).

<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code>
:The ''current'' target's build tool executable (compiler, linker, etc).

=== Language and encoding ===

<code>$(LANGUAGE)</code>
:The system language in human readable form.

<code>$(ENCODING)</code>
:The character encoding in human readable form.

=== Time and date ===

<code>$(TDAY)</code>
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)

<code>$(TODAY)</code>
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)

<code>$(NOW)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)

<code>$(NOW_L)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)

<code>$(WEEKDAY)</code>
:Human-readable day of the week (for example "Wednesday")

<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code>
:These are identical to the preceding types, but are expressed relative to UTC.

=== Random values ===

<code>$(COIN)</code>
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.

<code>$(RANDOM)</code>
:A 16bit positive random number (0-65535)

=== Conditional Evaluation ===

<code>$if(condition){true clause}{false clause}</code>
:Conditional evaluation will resolve to its <tt>true clause</tt> if
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)
:Conditional evaluation will resolve to its <tt>false clause</tt> if
::<tt>condition</tt> is empty
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt>

Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.

=== Script expansion ===

:For maximum flexibility, you can embed scripts using the <tt>[[</tt> <tt>]]</tt> operator as a special case of variable expansion. Embedded scripts have access to all standard functionality available to scrips and work pretty much like <tt>bash</tt> backticks (except for having access to Code::Blocks' namespace). As such, scripts are not limited to producing text output, but can also manipulate Code::Blocks state (projects, targets, etc.). Although this is technically possible, it is generally bad design and a very stupid idea to do so. Manipulating Code::Blocks state from a pre-build script is a much better solution. 

:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.

:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.

:Example: 
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt> 
:inserts the active project's title into the command line.

Variable expansion

2009-01-16T11:08:29Z

Mariocup: /* Files and directories */

[[Category:User Documentation]]

== Syntax ==
Code::Blocks treats the following functionally identical character sequences inside pre-build, post-build, or build steps as variables:

* <code>$VARIABLE</code>
* <code>$(VARIABLE)</code>
* <code>${VARIABLE}</code>
* <code>%VARIABLE%</code>

Variable names must consist of alphanumeric characters and are not case-sensitive. Variables starting with a single hash sign (<code>#</code>) are interpreted as [[global user variables]].
The names listed below are interpreted as builtin types.

Variables which are neither global user variables nor builtin types are replaced with a value provided in the project file, or with an environment variable if the latter should fail.

'''Per-target definitions have precedence over per-project definitions.'''

== List of available builtins ==

=== Code::Blocks workspace ===

<code>$(WORKSPACE_FILENAME)</code>, <code>$(WORKSPACE_FILE_NAME)</code>, <code>$(WORKSPACEFILE)</code>, <code>$(WORKSPACEFILENAME)</code>: The filename of the current workspace project (.workspace).

<code>$(WORKSPACENAME)</code>, <code>$(WORKSPACE_NAME)</code>: The name of the workspace that is displayed in the Management panel.

<code>$(WORKSPACE_DIR)</code>, <code>$(WORKSPACE_DIRECTORY)</code>, <code>$(WORKSPACEDIR)</code>, <code>$(WORKSPACEDIRECTORY)</code>: The location of the workspace directory.

=== Files and directories ===

<code>$(PROJECT_FILENAME)</code>, <code>$(PROJECT_FILE)</code>, <code>$(PROJECTFILE)</code>
:The filename of the currently compiling project.

<code>$(PROJECT_NAME)</code>
:The name of the currently compiling project.

<code>$(PROJECT_DIR)</code>, <code>$(PROJECTDIR)</code>, <code>$(PROJECT_DIRECTORY)</code>
:The common top-level directory of the currently compiling project.

<code>$(ACTIVE_EDITOR_FILENAME)</code>
:The filename of the file opened in the currently active editor.

<code>$(ACTIVE_EDITOR_DIRNAME)</code>
:Currently active file's containing directory (relative to the common top level path)

<code>$(ACTIVE_EDITOR_STEM)</code>
:Currently active file's base name (without extension).

<code>$(ACTIVE_EDITOR_EXT)</code>
:Currently active file's extension.

<code>$(ALL_PROJECT_FILES)</code>
:A string containing the names of all files in the current project.

<code>$(MAKEFILE)</code>
:The filename of the makefile.

<code>$(CODEBLOCKS)</code>, <code>$(APP_PATH)</code>, <code>$(APPPATH)</code>, <code>$(APP-PATH)</code>
:The path to the currently running instance of Code::Blocks

<code>$(DATAPATH)</code>, <code>$(DATA_PATH)</code>, <code>$(DATA-PATH)</code>
:The 'shared' directory of the currently running instance of Code::Blocks

<code>$(PLUGINS)</code>
:The 'plugins' directory of the currently running instance of Code::Blocks

=== Build targets ===

<code>$(FOOBAR_OUTPUT_FILE)</code>
:A ''specific'' target's output file.

<code>$(FOOBAR_OUTPUT_DIR)</code>
:A ''specific'' target's output directory.

<code>$(FOOBAR_OUTPUT_BASENAME)</code>
:A ''specific'' target's output file's base name (no path, no extension).

<code>$(TARGET_OUTPUT_DIR)</code>
:The ''current'' target's output directory.

<code>$(TARGET_OBJECT_DIR)</code>
:The ''current'' target's object directory.

<code>$(TARGET_NAME)</code>
:The ''current'' target's name.

<code>$(TARGET_OUTPUT_FILE)</code>
:The ''current'' target's output file.

<code>$(TARGET_OUTPUT_BASENAME)</code>
:The ''current'' target's output file's base name (no path, no extension).

<code>$(TARGET_CC), $(TARGET_CPP), $(TARGET_LD), $(TARGET_LIB)</code>
:The ''current'' target's build tool executable (compiler, linker, etc).

=== Language and encoding ===

<code>$(LANGUAGE)</code>
:The system language in human readable form.

<code>$(ENCODING)</code>
:The character encoding in human readable form.

=== Time and date ===

<code>$(TDAY)</code>
:Current date in the form <code>YYYYMMDD</code> (for example 20051228)

<code>$(TODAY)</code>
:Current date in the form <code>YYYY-MM-DD</code> (for example 2005-12-28)

<code>$(NOW)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm</code> (for example 2005-12-28-07.15)

<code>$(NOW_L)</code>
:Timestamp in the form <code>YYYY-MM-DD-hh.mm.ss</code> (for example 2005-12-28-07.15.45)

<code>$(WEEKDAY)</code>
:Human-readable day of the week (for example "Wednesday")

<code>$(TDAY_UTC)</code>, <code>$(TODAY_UTC)</code>, <code>$(NOW_UTC)</code>, <code>$(NOW_L_UTC)</code>, <code>$(WEEKDAY_UTC)</code>
:These are identical to the preceding types, but are expressed relative to UTC.

=== Random values ===

<code>$(COIN)</code>
:This variable tosses a virtual coin (once per invokation) and returns 0 or 1.

<code>$(RANDOM)</code>
:A 16bit positive random number (0-65535)

=== Conditional Evaluation ===

<code>$if(condition){true clause}{false clause}</code>
:Conditional evaluation will resolve to its <tt>true clause</tt> if
::<tt>condition</tt> is a non-empty character sequence other than <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a non-empty variable that does not resolve to <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that evaluates to <tt>true</tt> (implicit by previous condition)
:Conditional evaluation will resolve to its <tt>false clause</tt> if
::<tt>condition</tt> is empty
::<tt>condition</tt> is <tt>0</tt> or <tt>false</tt>
::<tt>condition</tt> is a variable that is empty or evaluates to <tt>0</tt> or <tt>false</tt>

Please do note that neither the variable syntax variants <tt>%if(...)</tt> nor <tt>$(if)(...)</tt> are supported for this construct.

=== Script expansion ===

:For maximum flexibility, you can embed scripts using the <tt>[[</tt> <tt>]]</tt> operator as a special case of variable expansion. Embedded scripts have access to all standard functionality available to scrips and work pretty much like <tt>bash</tt> backticks (except for having access to Code::Blocks' namespace). As such, scripts are not limited to producing text output, but can also manipulate Code::Blocks state (projects, targets, etc.). Although this is technically possible, it is generally bad design and a very stupid idea to do so. Manipulating Code::Blocks state from a pre-build script is a much better solution. 

:The script text is replaced with any output generated by your script, or discarded in case of a syntax error.

:As conditional evaluation runs prior to expanding scripts, conditional evaluation can be used for preprocessor functionality. Builtin variables (and user variables) are expanded after scripts, so it is possible to reference variables in a script's output.

:Example: 
:<tt><nowiki>[[ print(GetProjectManager().GetActiveProject().GetTitle()); ]]</nowiki></tt> 
:inserts the active project's title into the command line.

Keyboard Shortcuts

2009-01-03T01:03:32Z

Mariocup: /* Search */

[[Category:User Documentation]]

::''Note: You can define your own keyboard shortcuts with the [[Keyboard Shortcuts plugin]]''

== Editor ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Undo last action || Ctrl + Z
|-

|-
| Redo last action || Ctrl + Shift + Z
|-

|-
| Cut selected text || Ctrl + X
|-

|-
| Copy selected text || Ctrl + C
|-

|-
| Paste text from clipboard || Ctrl + V
|-

|-
| Select all text || Ctrl + A
|-

|-
| Swap header / source || F11
|-

|-
| Comment highlighted code || Ctrl + Shift + C
|-

|-
| Uncomment highlighted code || Ctrl + Shift + X
|-

|-
| Duplicate line caret is on || Ctrl + D
|-

|-
| Auto-complete / Abbreviations || Ctrl + Space / Ctrl + J
|-

|-
| Show call tip || Ctrl + Shift + Space
|-

|-
| Swap line caret is on with line above it || Ctrl + T
|-

|-
| Toggle bookmark || Ctrl + B
|-

|-
| Goto previous bookmark || Alt + PgUp
|-

|-
| Goto next bookmark || Alt + PgDown
|-

|-
| Toggle current block folding || F12
|-

|-
| Toggle all folds || Shift + F12
|-

|}

This is a list of shortcuts provided by the Code::Blocks' editor component. These shortcuts cannot be rebound.

{| border="1" cellpadding="3" cellspacing="0" style="1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Magnify text size. || Ctrl + Keypad "+"
|-

|-
| Reduce text size. || Ctrl + Keypad "-"
|-

|-
| Restore text size to normal. || Ctrl + Keypad "/"
|-

|-
| Cycle through recent files. || Ctrl + Tab
|-

|-
| Indent block. || Tab
|-

|-
| Dedent block. || Shift + Tab
|-

|-
| Delete to start of word. || Ctrl + BackSpace
|-

|-
| Delete to end of word. || Ctrl + Delete
|-

|-
| Delete to start of line. || Ctrl + Shift + BackSpace
|-

|-
| Delete to end of line. || Ctrl + Shift + Delete
|-

|-
| Go to start of document. || Ctrl + Home
|-

|-
| Extend selection to start of document. || Ctrl + Shift + Home
|-

|-
| Go to start of display line. || Alt + Home
|-

|-
| Extend selection to start of display line. || Alt + Shift + Home
|-

|-
| Go to end of document. || Ctrl + End
|-

|-
| Extend selection to end of document. || Ctrl + Shift + End
|-

|-
| Go to end of display line. || Alt + End
|-

|-
| Extend selection to end of display line. || Alt + Shift + End
|-

|-
| Expand or contract a fold point. || Ctrl + Keypad "*"
|-

|-
| Create or delete a bookmark. || Ctrl + F2
|-

|-
| Go to next bookmark. || F2
|-

|-
| Select to next bookmark. || Alt + F2
|-

|-
| Find selection. || Ctrl + F3
|-

|-
| Find selection backwards. || Ctrl + Shift + F3
|-

|-
| Scroll up. || Ctrl + Up
|-

|-
| Scroll down. || Ctrl + Down
|-

|-
| Line cut. || Ctrl + L
|-

|-
| Line copy. || Ctrl + Shift + T
|-

|-
| Line delete. || Ctrl + Shift + L
|-

|-
| Line transpose with previous. || Ctrl + T
|-

|-
| Line duplicate. || Ctrl + D
|-

|-
| Find matching preprocessor conditional, skipping nested ones. || Ctrl + K
|-

|-
| Select to matching preprocessor conditional. || Ctrl + Shift + K
|-

|-
| Find matching preprocessor conditional backwards, skipping nested ones. || Ctrl + J
|-

|-
| Select to matching preprocessor conditional backwards. || Ctrl + Shift + J
|-

|-
| Previous paragraph. Shift extends selection. || Ctrl + [
|-

|-
| Next paragraph. Shift extends selection. || Ctrl + ]
|-

|-
| Previous word. Shift extends selection. || Ctrl + Left
|-

|-
| Next word. Shift extends selection. || Ctrl + Right
|-

|-
| Previous word part. Shift extends selection. || Ctrl + /
|-

|-
| Next word part. Shift extends selection. || Ctrl + \
|-

|}

== Files ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| New file or project || Ctrl + N
|-

|-
| Open existing file or project || Ctrl + O
|-

|-
| Save current file || Ctrl + S
|-

|-
| Save all files || Ctrl + Shift + S
|-

|-
| Close current file || Ctrl + F4 / Ctrl + W
|-

|-
| Close all files || Ctrl + Shift + F4 / Ctrl + Shift + W
|-

|}

This is a list of shortcuts provided by the Code::Blocks' tab component. These shortcuts cannot be rebound.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Activate next open file || Ctrl + Tab
|-

|-
| Activate previous open file || Ctrl + Shift + Tab
|-

|}

== View ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Show / hide Messages pane || F2
|-

|-
| Show / hide Management pane || Shift + F2
|-

|-
| Move project up (in Project tree) || Ctrl + Shift + Up
|-

|-
| Move project down (in Project tree) || Ctrl + Shift + Down
|-

|-
| Activate prior (in Project tree) || Alt + F5
|-

|-
| Activate next (in Project tree) || Alt + F6
|-

|-
| Zoom in / out || Ctrl + Roll Mouse Wheel
|-

|-
| Focus editor || CTRL + Alt + E
|-

|}

== Search ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Find || Ctrl + F
|-

|-
| Find next || F3
|-

|-
| Find previous || Shift + F3
|-

|-
| Find in files || Crtl + Shift + F
|-

|-
| Replace || Ctrl + R
|-

|-
| Replace in files || Ctrl + Shift + R
|-

|-
| Goto line || Ctrl + G
|-

|-
| Goto next changed line || Ctrl + F3
|-

|-
| Goto previous changed line || Ctrl + Shift + F3
|-

|-
| Goto file || Alt + G
|-

|-
| Goto function || Ctrl + Alt + G
|-

|-
| Goto previous function || Ctrl + PgUp
|-

|-
| Goto next function || Ctrl + PgDn
|-

|-
| Goto declaration || Ctrl + Shift + .
|-

|-
| Goto implementation || Ctrl + .
|-

|-
| Open include file || Ctrl + Alt + .
|-

|}

== Build ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Build || Ctrl + F9
|-

|-
| Compile current file || Ctrl + Shift + F9
|-

|-
| Run || Ctrl + F10
|-

|-
| Build and Run || F9
|-

|-
| Rebuild || Ctrl + F11
|-

|}

== Debug ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
!Function
!Shortcut Key
|-

|-
| Debug || F8
|-

|-
| Continue debugging || Ctrl + F7
|-

|-
| Step over a code block || F7
|-

|-
| Step into a code block || Shift + F7
|-

|-
| Step out of a code block || Ctrl + Shift + F7
|-

|-
| Toggle breakpoint || F5
|-

|-
| Run to cursor || F4
|-

|-
| Previous error || Alt + F1
|-

|-
| Next error || Alt + F2
|-

|}

User talk:Mariocup

2008-11-23T11:44:33Z

Mariocup: /* Setting Defines */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and assigning a shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:44:22Z

Mariocup: /* Assembler Options */

User talk:Mariocup

2008-11-23T11:43:51Z

Mariocup: /* Resize editor window */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and assigning a shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:42:47Z

Mariocup: /* Extension Points for options */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:42:34Z

Mariocup: /* Occlusion highlight */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:41:56Z

Mariocup: /* File Explorer in CB */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:41:39Z

Mariocup: /* Block Select Mode */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:41:23Z

Mariocup: /* Insert Class method Declaration/Implementation */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:41:12Z

Mariocup: /* Clipboard History */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
If users are writing source code a quite common problem is that your are using copy and paste functionality. Sometimes it could happen that you want to replace two different words with a new string. For example you have a header file and renamed two defines

#define NAME1 1
#define NAME2 2

and renamed

#define NAME_1 1
#define NAME_2 2

These defines are a bit mask in status variable and this is used in your source code.

var = NAME1 | NAME2;

It would be easier in such a case to put NAME_1 and NAME_2 in a clipboard history, that could be displayed e.g. in the log & others window. Now if you reached the line with var you could select NAME1 and make e.g. a double click on the NAME_1 entry in the clipboard history to paste the string and if you select NAME2 the same again for the other entry. Since you could have several entries in the clipboard history it would make sense to sort them alphebatically (e.g. sort button or column) on demand.

For example I am using (http://ditto-cp.sourceforge.net/) ditto clipboard history manager under windows. With this clipboard manager you can type a text in a search field and then you get a filtered clipboard history. This would be a more advanced feature but desirable.

Since a clipboard entry could be very long I think it should be trunkated to a fix number of characters. I do not know what would be a reasonable length.

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:39:59Z

Mariocup: /* Resize editor window */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) - Saving different layouts and putting shortcuts is a workaround.

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:39:26Z

Mariocup: /* Wrap Mode */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-23T11:39:03Z

Mariocup: /* Aspell */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Hunspell ==
Integrate Hunspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:38:47Z

Mariocup: /* Insert Class method Declaration/Implementation */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:38:32Z

Mariocup: /* Show value of defines */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:38:10Z

Mariocup: /* Insert Class method Declaration/Implementation */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:37:55Z

Mariocup: /* Incremental Search */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:37:33Z

Mariocup: /* Insert Class method Declaration/Implementation */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:37:13Z

Mariocup: /* Clipboard History */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:36:54Z

Mariocup: /* Window docking */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-11-11T22:35:59Z

Mariocup: /* Search Dialog */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

Code::Blocks Plugins

2008-10-07T18:36:18Z

Mariocup: /* Contrib Plugins */

[[Category: User Documentation]]
Code::Blocks' features can be extend by using '''plugins'''. Plugins listed here are divided into two categories: ''core'' and ''contrib''.

=== Core Plugins ===

The core plugins are installed by default and offer the basic functions of Code::Blocks. The core plugins are maintained / developed by the official development team.

'''[[Autosave plugin|Autosave]]'''

:Saves project files between intervals.

'''[[Class Wizard plugin|Class Wizard]]'''

:Provides wizard for creating new classes.

'''[[Code Completion plugin|Code Completion]]'''

:Provides code completion functionality and class browser.

'''[[Compiler plugin|Compiler]]'''

:Provides support for various compilers in one interface.

'''[[Debugger plugin|Debugger]]'''

:Provides support for various debuggers in one interface.

'''[[File Extension Handler plugin|File Extensions Handler]]'''

:Adds extra file extension handlers.

'''[[Open Files List plugin|Open Files List]]'''

:Manages a list of all opened files (editors).

'''[[Projects Importer plugin|Projects Importer]]'''

:Imports projects from other IDE's, e.g. MS Visual Studio and DevC++.

'''[[Scripted Wizard plugin|Scripted Wizard]]'''

:Provides scripted wizard functionality.

'''[[Source Code Formatter plugin|Source Code Formatter]]'''

:Formats source code files with specific style.

'''[[To-Do List plugin|To-Do List]]'''

:Adds to-do items to source code.

'''[[WinXP Look'n'Feel plugin|WinXP Look'n'Feel]]'''

:Creates manifest file which enables the version 6.0 of the Common Controls on Windows XP.

=== Contrib Plugins ===

The user-''contrib''uted plugins are not installed by default and offer extended functionality for Code::Blocks. The contrib plugins are maintained / developed by third-party developers.

'''[[AutoVersioning|Auto Versioning]]'''

:Helps you keep track of your project version and status.

'''[[Browse Tracker plugins|Browse Tracker]]'''

:Browse to previous source positions.

'''[[C::B Games plugin|C::B Games]]'''

:Games in a integrated development environment? You bet.

'''[[Code Profiler plugin|Code Profiler]]'''

:Provides graphical interface to GNU GProf profiler.

'''[[Code Snippets plugin|Code Snippets]]'''

:Manages small pieces of code (i.e. snippets).

'''[[Code Statistics plugin|Code Statistics]]'''

:Shows various statistics from source code files.

'''[[Copy Strings to Clipboard plugin|Copy Strings to Clipboard]]'''

:Copies literal strings from the current editor to clipboard.

'''[[DevPak Installer plugin|DevPak Installer]]'''

:Installs and updates DevC++ DevPaks.

'''[[DragScroll plugin|DragScroll]]'''

:Enables dragging and scrolling with mouse.

'''[[Environment Variables plugin|Environment Variables]]'''

:Sets environment variables within the focus of Code::Blocks.

'''[[Help plugin]]'''

:Integrates third-party help files to the interface.

'''[[HexEditor plugin]]'''

:Opens files in a Code::Blocks integrated HexEditor.

'''[[Keyboard Shortcuts plugin|Keyboard Shortcuts]]'''

:Manages menu shortcuts.

'''[[Koders plugin|Koders]]'''

:Queries the Koders webpage for keywords.

'''[[RegEx Testbed plugin|RegEx Testbed]]'''

:Regular expressions testbed.

'''[[Source Exporter plugin|Source Exporter]]'''

:Exports source code files to other formats such as HTML and PDF.

'''[[Symbol Table plugin|Symbol Table]]'''

:A simple graphical interface to the GNU symbol table displayer (nm).

'''[[ThreadSearch]]'''

:Multi-threaded 'Search in files' with preview window.

'''[[Valgrind plugin|Valgrind]]'''

:Valgrind analysis tools integration.

'''[[wxSmith plugin|wxSmith]]'''

:RAD tool for creating wxWidgets dialogs.

Code::Blocks command line arguments

2008-10-01T11:39:18Z

Mariocup: /* Command line arguments */

[[Category: User Documentation]]
== Using command line arguments ==

=== Windows ===

# Find the Code::Blocks shortcut in the Desktop or Start menu.
# Right click on the icon and select Properties.
# Select the Shortcut tab.
# Append the command line arguments you want to use to the end of the Target text (behind the quote mark).
# Run Code::Blocks by using the shortcut you edited.

'''Example'''

"C:\Program Files\CodeBlocks\codeblocks.exe" /na /nd

=== *nix ===

# Launch a terminal client, such as XTerm, Gnome Terminal or Konsole.
# Type "codeblocks" and then append the command line arguments you want to use.

'''Example'''

codeblocks --no-splash-screen --debug-log

== Command line arguments ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
! Argument
! Function
|-

|-
| ''<filename>''
| Specifies the project *.cbp filename or workspace *.workspace filename. For instance ''<filename>'' may be ''c:\some\where\a\project.cbp''. Place this argument at end of command line, just before output redirection if any.
|-

|-
| '''--file='''''<filename>[:line]''
| Open file in Code::Blocks and optionally jump to a specific line.
|-

|-
| '''/h''', '''--help''', '''/?''', '''--?'''
| Shows a help message about the command line arguments.
|-

|-
| '''/na''', '''--no-check-associations'''
| Don't perform any file association checks (Windows only).
|-

|-
| '''/nd''', '''--no-dde'''
| Don't start a [http://en.wikipedia.org/wiki/Dynamic_Data_Exchange DDE] server (Windows only).
|-

|-
| '''/ns''', '''--no-splash-screen'''
| Hides the splash screen when the application is loading.
|-

|-
| '''/d''', '''--debug-log'''
| Display application's debug log.
|-

|-
| '''--prefix='''''<str>''
| Sets the shared data directory prefix.
|-

|-
| '''/p''', '''--personality='''''<str>'', '''--profile='''''<str>''
| Sets the [[Personalities|personality]] to use. You can use ''ask'' as the parameter to list available personalities.
|-

|-
| '''--rebuild'''
| Clean and build the project / workspace.
|-

|-
| '''--build'''
| Build the project / workspace.
|-

|-
| '''--target='''''<str>''
| Sets target for batch build. For example --target="Release".
|-

|-
| '''--no-batch-window-close'''
| Keeps the batch log window visible after the batch build has completed.
|-

|-
| '''--batch-build-notify'''
| Shows a message after the batch build has completed.
|-

|-
| '''>''' ''<build log file>''
| Placed in the very last position of command line, this may be used to redirect standard output to log file, this is not a codeblock option as such, but just a DOS/*nix shell usual standard output redirection
|-

|}

Code::Blocks command line arguments

2008-10-01T11:39:08Z

Mariocup: /* Command line arguments */

[[Category: User Documentation]]
== Using command line arguments ==

=== Windows ===

# Find the Code::Blocks shortcut in the Desktop or Start menu.
# Right click on the icon and select Properties.
# Select the Shortcut tab.
# Append the command line arguments you want to use to the end of the Target text (behind the quote mark).
# Run Code::Blocks by using the shortcut you edited.

'''Example'''

"C:\Program Files\CodeBlocks\codeblocks.exe" /na /nd

=== *nix ===

# Launch a terminal client, such as XTerm, Gnome Terminal or Konsole.
# Type "codeblocks" and then append the command line arguments you want to use.

'''Example'''

codeblocks --no-splash-screen --debug-log

== Command line arguments ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
! Argument
! Function
|-

|-
| ''<filename>''
| Specifies the project *.cbp filename or workspace *.workspace filename. For instance ''<filename>'' may be ''c:\some\where\a\project.cbp''. Place this argument at end of command line, just before output redirection if any.
|-

|-
| '''--file='''''<filename>[:line]''
| Open file in Code::Blocks and optionally jump to a specific line.
|-

|-
| '''/h''', '''--help''','''/?''', '''--?'''
| Shows a help message about the command line arguments.
|-

|-
| '''/na''', '''--no-check-associations'''
| Don't perform any file association checks (Windows only).
|-

|-
| '''/nd''', '''--no-dde'''
| Don't start a [http://en.wikipedia.org/wiki/Dynamic_Data_Exchange DDE] server (Windows only).
|-

|-
| '''/ns''', '''--no-splash-screen'''
| Hides the splash screen when the application is loading.
|-

|-
| '''/d''', '''--debug-log'''
| Display application's debug log.
|-

|-
| '''--prefix='''''<str>''
| Sets the shared data directory prefix.
|-

|-
| '''/p''', '''--personality='''''<str>'', '''--profile='''''<str>''
| Sets the [[Personalities|personality]] to use. You can use ''ask'' as the parameter to list available personalities.
|-

|-
| '''--rebuild'''
| Clean and build the project / workspace.
|-

|-
| '''--build'''
| Build the project / workspace.
|-

|-
| '''--target='''''<str>''
| Sets target for batch build. For example --target="Release".
|-

|-
| '''--no-batch-window-close'''
| Keeps the batch log window visible after the batch build has completed.
|-

|-
| '''--batch-build-notify'''
| Shows a message after the batch build has completed.
|-

|-
| '''>''' ''<build log file>''
| Placed in the very last position of command line, this may be used to redirect standard output to log file, this is not a codeblock option as such, but just a DOS/*nix shell usual standard output redirection
|-

|}

User talk:Mariocup

2008-09-30T14:08:17Z

Mariocup: /* Incremental Search */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-09-30T14:05:52Z

Mariocup: /* Show value of defines */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET) Already implemented.

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-09-30T14:05:21Z

Mariocup: /* Block Select Mode */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. --[[User:Mariocup|Mariocup]] This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-09-30T14:04:23Z

Mariocup: /* Block Select Mode */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array. This features is already implemented.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

- Isn't that already supported? (the "Stop" button first interrupts the process and on second-click stops it) - [[User:Mandrav|Mandrav]] 10:06, 13 April 2008 (CEST)

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

Code::Blocks command line arguments

2008-09-30T10:40:45Z

Mariocup: /* Command line arguments */

[[Category: User Documentation]]
== Using command line arguments ==

=== Windows ===

# Find the Code::Blocks shortcut in the Desktop or Start menu.
# Right click on the icon and select Properties.
# Select the Shortcut tab.
# Append the command line arguments you want to use to the end of the Target text (behind the quote mark).
# Run Code::Blocks by using the shortcut you edited.

'''Example'''

"C:\Program Files\CodeBlocks\codeblocks.exe" /na /nd

=== *nix ===

# Launch a terminal client, such as XTerm, Gnome Terminal or Konsole.
# Type "codeblocks" and then append the command line arguments you want to use.

'''Example'''

codeblocks --no-splash-screen --debug-log

== Command line arguments ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 1px solid gray"
! Argument
! Function
|-

|-
| ''<filename>''
| Specifies the project *.cbp filename or workspace *.workspace filename. For instance ''<filename>'' may be ''c:\some\where\a\project.cbp''. Place this argument at end of command line, just before output redirection if any.
|-

|-
| '''--file='''''<filename>[:line]''
| Open file in Code::Blocks and optionally jump to a specific line.
|-

|-
| '''/h''', '''--help'''
| Shows a help message about the command line arguments.
|-

|-
| '''/na''', '''--no-check-associations'''
| Don't perform any file association checks (Windows only).
|-

|-
| '''/nd''', '''--no-dde'''
| Don't start a [http://en.wikipedia.org/wiki/Dynamic_Data_Exchange DDE] server (Windows only).
|-

|-
| '''/ns''', '''--no-splash-screen'''
| Hides the splash screen when the application is loading.
|-

|-
| '''/d''', '''--debug-log'''
| Display application's debug log.
|-

|-
| '''--prefix='''''<str>''
| Sets the shared data directory prefix.
|-

|-
| '''/p''', '''--personality='''''<str>'', '''--profile='''''<str>''
| Sets the [[Personalities|personality]] to use. You can use ''ask'' as the parameter to list available personalities.
|-

|-
| '''--rebuild'''
| Clean and build the project / workspace.
|-

|-
| '''--build'''
| Build the project / workspace.
|-

|-
| '''--target='''''<str>''
| Sets target for batch build. For example --target="Release".
|-

|-
| '''--no-batch-window-close'''
| Keeps the batch log window visible after the batch build has completed.
|-

|-
| '''--batch-build-notify'''
| Shows a message after the batch build has completed.
|-

|-
| '''>''' ''<build log file>''
| Placed in the very last position of command line, this may be used to redirect standard output to log file, this is not a codeblock option as such, but just a DOS/*nix shell usual standard output redirection
|-

|}

Scripting commands

2008-06-11T06:09:03Z

Mariocup: /* CompileOptionsBase */

[[Category:Scripting Code::Blocks]]
Scripting is no good if all you can do is use the scripting language's built-in commands only. The host application (Code::Blocks) needs to expose parts of its internals to scripts, so scripts can use and control the host.

Code::Blocks has exposed a very large chunk of its SDK to scripts. This makes scripting in Code::Blocks nearly as powerful as native code (C++).

In this page all the exported constants, functions and classes are documented as a quick reference. For detailed documentation on each function/class, refer to the Code::Blocks SDK documentation.

''NOTE: Please remember that [http://www.squirrel-lang.org Squirrel] is typeless. Data types mentioned below are only used for documentation purposes.''

''NOTE: Please keep in mind that if a function has default parameters in C++ (which can be ommitted), you still have to type them for scripts (for e.g. exposed wxWidgets functionality). This means you *have* to use e.g. wxFileName.GetFullPath(wxPATH_NATIVE) instead of e.g only wxFileName.GetFullPath().

== Application object ==
The application object is accessed through the variable named '''<tt>App</tt>'''. Currently it has no bound functions...

== Global functions ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || Log || wxString || logs to the application log
|-

|-
| void || LogDebug || wxString || logs to the debug log
|-

|-
| void || LogWarning || wxString || logs a warning
|-

|-
| void || LogError || wxString || logs an error
|-

|-
| int || Message || wxString,wxString,int || arg1=msg, arg2=caption, arg3=buttons; see API docs for cbMessageBox()
|-

|-
| void || ShowMessage || wxString ||
|-

|-
| void || ShowWarning || wxString ||
|-

|-
| void || ShowError || wxString ||
|-

|-
| void || ShowInfo || wxString ||
|-

|-
| wxString || ReplaceMacros || wxString,bool ||
|-

|-
| ScriptingManager* || GetScriptingManager || ||
|-

|-
| ProjectManager* || GetProjectManager || ||
|-

|-
| EditorManager* || GetEditorManager || ||
|-

|-
| ConfigManager* || GetConfigManager || ||
|-

|-
| UserVariableManager* || GetUserVariableManager || ||
|-

|-
| CompilerFactory* || GetCompilerFactory || ||
|-

|-
| wxArrayString || GetArrayFromString || wxString,wxString,bool ||
|-

|-
| wxString || GetStringFromArray || wxArrayString,wxString,bool ||
|-

|-
| wxString || EscapeSpaces || wxString ||
|-

|-
| wxString || UnixFilename || wxString ||
|-

|-
| FileType || FileTypeOf || wxString ||
|-

|-
| wxString || URLEncode || wxString ||
|-

|-
| void || NotifyMissingFile || wxString ||
|-

|-
| int || GetPlatformsFromString || wxString ||
|-

|-
| wxString || GetStringFromPlatforms || int,bool||
|-

|-
| void|| Display || wxString,wxString,int,int ||
|-

|-
| wxString || GetFolder || int || see API docs for ConfigManager::GetFolder()
|-

|-
| wxString || LocateDataFile|| wxString, int || see API docs for ConfigManager::LocateDataFile()
|-

|-
| bool || InstallPlugin || wxString,bool, bool || Install a binary plugin
|-

|-
| void || Include || wxString || similar to C/C++ ''<tt>#include "name"</tt>''
|-

|-
| bool || IsNull || void* ||
|-

|-
| wxString || _T || const char* || basically this is the wxString constructor
|-

|-
| bool || wxLaunchDefaultBrowser || wxString ||
|-

|-
| wxColour || wxGetColourFromUser || [wxColour] ||
|-

|-
| long || wxGetNumberFromUser || wxString,wxString,wxString ||
|-

|-
| wxString || wxGetPasswordFromUser || wxString,wxString,wxString ||
|-

|-
| wxString || wxGetTextFromUser || wxString,wxString,wxString ||
|-

|}

== ScriptingManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || RegisterScriptMenu || wxString, wxString || registers the script file (arg1) under a menu item (arg2).
e.g. <tt>GetScriptingManager().RegisterScriptMenu(_T("sample.script"), _T("Scripts/Sample script"))</tt>;
|-

|}

Notes about the <tt>RegisterScriptMenu</tt> function: 
* The second argument (menu item) is a string containing the full menu path to create the menu item. The path separator is a slash (/). For example, the string "Settings/Sample menu/Sample item" would create the menu path "Settings->Sample menu->Sample item".
* When each part of the path is evaluated, it is checked whether it starts with a number followed by a colon (:). If so then this is considered to be a menu index in the parent menu and the menu is inserted at that index instead of being appended to the menu. The number and colon are removed from the string.
* If the menu item starts with a dash (-), then a separator line is prepended in the menu before the menu item (e.g. "Scripts/'''-'''Sample script").
* For your convenience, all menu items created using this function have one extra functionality: if you keep the SHIFT key pressed while clicking on any of these "script menu items", instead of running the attached script, Code::Blocks will open it in the editor for you to view/edit :).
* Have a look at the [[Startup script#Example|startup script example]].

== ConfigManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| int || Read || int,int ||
|-

|-
| bool || Read || bool,bool ||
|-

|-
| float || Read || float,float ||
|-

|-
| wxString || Read || wxString,wxString ||
|-

|-
| void || Write || int,int ||
|-

|-
| void || Write || bool,bool ||
|-

|-
| void || Write || float,float ||
|-

|-
| void || Write || wxString,wxString[,bool] ||
|-

|}

== ProjectManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| wxString || GetDefaultPath || ( ) ||
|-

|-
| void || SetDefaultPath || (const wxString& path) ||
|-

|-
| cbProject* || GetActiveProject || ( ) ||
|-

|-
| void || SetProject || (cbProject* project, bool refresh = true) ||
|-

|-
| bool || LoadWorkspace || (const wxString& filename = DEFAULT_WORKSPACE)||
|-

|-
| bool || SaveWorkspace || ( ) ||
|-

|-
| bool || SaveWorkspaceAs || (const wxString& filename) ||
|-

|-
| bool || CloseWorkspace || ( ) ||
|-

|-
| cbProject* || IsOpen || (const wxString& filename) ||
|-

|-
| cbProject* || LoadProject || (const wxString& filename, bool activateIt = true) ||
|-

|-
| bool || SaveProject || (cbProject* project) ||
|-

|-
| bool || SaveProjectAs || (cbProject* project) ||
|-

|-
| bool || SaveActiveProject || ( ) ||
|-

|-
| bool || SaveActiveProjectAs || ( ) ||
|-

|-
| bool || SaveAllProjects || ( ) ||
|-

|-
| bool || CloseProject || (cbProject* project, bool dontsave = false, bool refresh = true) ||
|-

|-
| bool || CloseActiveProject || (bool dontsave = false) ||
|-

|-
| bool || CloseAllProjects || (bool dontsave = false) ||
|-

|-
| cbProject* || NewProject || (const wxString& filename = wxEmptyString) ||
|-

|-
| int || AddFileToProject || (const wxString& filename, cbProject* project = 0L, int target = -1) ||
|-

|-
| int || AskForBuildTargetIndex || (cbProject* project = 0L) ||

|-
| void || RebuildTree || ( ) ||
|-

|-
| bool || AddProjectDependency || (cbProject* base, cbProject* dependsOn) ||
|-

|-
| void || RemoveProjectDependency || (cbProject* base, cbProject* doesNotDependOn) ||
|-

|-
| void || ClearProjectDependencies || (cbProject* base) ||
|-

|-
| void || RemoveProjectFromAllDependencies || (cbProject* base) ||
|-

|-
| ProjectsArray* || GetDependenciesForProject || (cbProject* base) ||
|-

|-
| void || ConfigureProjectDependencies || (cbProject* base = 0) ||
|-
|}

== EditorManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || Configure || ( ) ||
|-

|-
| cbEditor* || New || (const wxString& newFileName = wxEmptyString) ||
|-

|-
| cbEditor* || Open || (const wxString& filename) ||
|-

|-
| cbEditor* || IsBuiltinOpen || (const wxString& filename) ||
|-

|-
| cbEditor* || GetBuiltinEditor || (const wxString& filename)|(int index) ||
|-

|-
| cbEditor* || GetBuiltinActiveEditor || ( ) ||
|-

|-
| EditorBase* || GetActiveEditor || ( ) ||
|-

|-
| void || ActivateNext || ( ) ||
|-

|-
| void || ActivatePrevious || ( ) ||
|-

|-
| bool || SwapActiveHeaderSource || ( ) ||
|-

|-
| bool || CloseActive || (bool dontsave = false) ||
|-

|-
| bool || Close || (const wxString& filename,bool dontsave = false)|(int index,bool dontsave = false),(EditorBase* editor,bool dontsave = false) ||
|-

|-
| bool || CloseAll || (bool dontsave=false) ||
|-

|-
| bool || Save || (const wxString& filename)|(int index)||
|-

|-
| bool || SaveActive || ( ) ||
|-

|-
| bool || SaveAs || (int index) ||
|-

|-
| bool || SaveActiveAs || ( ) ||
|-

|-
| bool || SaveAll || ( ) ||
|-

|-
| int || ShowFindDialog || (bool replace, bool explicitly_find_in_files = false),bool ||
|-

|}

== UserVariableManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || Exists || (const wxString& variable) ||
|-

|}

== IO namespace ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || DirectoryExists || (const wxString& dir) ||
|-

|-
| wxString || SelectDirectory || (const wxString& message, const wxString& initialPath, bool showCreateDirButton) ||
|-

|-
| bool || '''CreateDirectory''' || (const wxString& full_path, int perms) || arg1=dir, arg2=permissions
|-

|-
| bool || '''RemoveDirectory''' || (const wxString& src) ||
|-

|-
| bool || '''CopyFile''' ||(const wxString& src, const wxString& dst, bool overwrite) || src,dest,overwrite
|-

|-
| bool || '''RenameFile''' || (const wxString& src, const wxString& dst) || old,new
|-

|-
| bool || '''RemoveFile''' || (const wxString& src) ||
|-

|-
| bool || FileExists || (const wxString& file) ||
|-

|-
| wxString || SelectFile || (const wxString& title, const wxString& defaultFile, const wxString& filter) ||
|-

|-
| bool || ReadFileContents || (const wxString& filename) ||
|-

|-
| bool || '''WriteFileContents''' || (const wxString& filename, const wxString& contents) || filename,contents
|-

|-
| int || '''Execute''' || (const wxString& command) ||
|-

|-
| wxString || '''ExecuteAndGetOutput''' || (const wxString& command) ||
|-

|-
| wxString || GetCwd || ( ) ||
|-

|-
| void || SetCwd || (const wxString& dir) || directory (currently working directory)
|-

|}

'''Notes:'''
The namespaces are accesses by prepending it's name (e.g. "IO.") to the scripting function, e.g. "IO.DirectoryExists(...)". "::" is only used when declaring the members of the namespace.
The functions in bold are going through the scripts security layer so there is no guarantee calling them will succeed. You should always examine the return value...
There exists one constant too, named ''allowInsecureScripts'', which allow you to test whether Code::Blocks was compiled with the functions going through the security layer.

== CompilerFactory ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || IsValidCompilerID || (const wxString& id) ||
|-

|-
| int || GetCompilerIndex || (const wxString& id) ||
|-

|-
| wxString || GetDefaultCompilerID || ( ) ||
|-

|-
| wxString || GetCompilerVersionString || (const wxString& Id) ||
|-

|-
| bool || CompilerInheritsFrom || ( ) ||
|-

|}

== wxString ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || operator+ || ||
|-

|-
| bool || operator< || ||
|-

|-
| bool || operator<= || ||
|-

|-
| bool || operator>= || ||
|-

|-
| bool || operator> || ||
|-

|-
| int || Find || wxString ||
|-

|-
| bool || Matches || wxString ||
|-

|-
| void || AddChar || char ||
|-

|-
| char || GetChar || int ||
|-

|-
| bool || IsEmpty || ||
|-

|-
| int || Length || ||
|-

|-
| int || length || || same as Length()
|-

|-
| int || len || || same as Length()
|-

|-
| int || size || || same as Length()
|-

|-
| wxString || Lower || ||
|-

|-
| wxString || LowerCase || || same as Lower()
|-

|-
| void || MakeLower || ||
|-

|-
| wxString || Upper || ||
|-

|-
| wxString || UpperCase || || same as Upper()
|-

|-
| void || MakeUpper || ||
|-

|-
| wxString || Mid || int,int ||
|-

|-
| void || Remove || int,int ||
|-

|-
| void || RemoveLast || ||
|-

|-
| int || Replace || wxString,wxString[,bool] ||
|-

|-
| wxString || Right || int ||
|-

|-
| wxString || AfterFirst || char ||
|-

|-
| wxString || AfterLast || char ||
|-

|-
| wxString || BeforeFirst || char ||
|-

|-
| wxString || BeforeLast || char ||
|-
|}
''NOTE: Is instantiated in a script using: local my_wxstring = ::wxString();

== wxArrayString ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || Add || wxString, size_t || arg1=string, arg2=number of copies to add
|-

|-
| void || Clear || ||
|-

|-
| int || GetCount || ||
|-

|-
| wxString || Item || int ||
|-

|}
''NOTE: Is instantiated in a script using: local my_wxarraystring = ::wxArrayString();

== wxColour ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| byte || Red || ||
|-

|-
| byte || Green || ||
|-

|-
| byte || Blue || ||
|-

|-
| void || Set || byte,byte,byte ||
|-

|}
''NOTE: Is instantiated in a script using: local my_wxcolour = ::wxColour();

== ProjectFile ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || AddBuildTarget || (const wxString& targetName)||
|-

|-
| void || RenameBuildTarget || (const wxString& oldTargetName, const wxString& newTargetName) ||
|-

|-
| void || RemoveBuildTarget || (const wxString& targetName)||
|-

|-
| wxString || GetBaseName || ( ) ||
|-

|-
| wxString || GetObjName || ( ) ||
|-

|-
| void || SetObjName || (const wxString& targetName) ||
|-

|-
| cbProject* || GetParentProject || ( ) ||
|-

|-
| wxString|| GetCustomBuildCommand|| (const wxString& compilerId) ||
|-

|-
| void || SetCustomBuildCommand || (const wxString& compilerId, const wxString& newBuildCommand) ||
|-

|-
| bool || GetUseCustomBuildCommand|| (const wxString& compilerId) ||
|-

|-
| void || SetUseCustomBuildCommand || (const wxString& compilerId, bool useCustomBuildCommand) ||
|-

|-
| wxFileName || file || || (variable)
|-

|-
| wxString || relativeFilename || || (variable)
|-

|-
| wxString || relativeToCommonTopLevelPath || || (variable)
|-

|-
| bool || compile || || (variable)
|-

|-
| bool || link || || (variable)
|-

|-
| int || weight || || (variable)
|-

|-
| wxString || compilerVar || || (variable)
|-

|}

== CompileOptionsBase ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || AddPlatform || (int platform) || windows,unix,mac
|-

|-
| void || RemovePlatform || (int platform) ||
|-

|-
| void || SetPlatforms || (int platform) ||
|-

|-
| void || GetPlatforms || ||
|-

|-
| void || SupportsCurrentPlatform || (int platform) ||
|-

|-
| void || SetLinkerOptions || (const wxArrayString& linkerOpts) ||
|-

|-
| void || SetLinkLibs || (const wxArrayString& linkLibs) ||
|-

|-
| void || SetCompilerOptions || (const wxArrayString& compilerOpts) ||
|-

|-
| void || SetIncludeDirs || (const wxArrayString& includeDirs) ||
|-

|-
| void || SetResourceIncludeDirs || (const wxString& option) ||
|-

|-
| void || SetLibDirs || (const wxArrayString& libDirs) ||
|-

|-
| void || SetCommandsBeforeBuild || (const wxArrayString& commands) ||
|-

|-
| void || SetCommandsAfterBuild || (const wxArrayString& commands) ||
|-

|-
| wxArrayString || GetLinkerOptions || ||
|-

|-
| wxArrayString || GetLinkLibs || ||
|-

|-
| wxArrayString || GetCompilerOptions || ||
|-

|-
| wxArrayString || GetIncludeDirs || ||
|-

|-
| wxArrayString || GetResourceIncludeDirs || ||
|-

|-
| wxArrayString || GetLibDirs || ||
|-

|-
| wxArrayString || GetCommandsBeforeBuild || ||
|-

|-
| wxArrayString || GetCommandsAfterBuild || ||
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || (bool modified) ||
|-

|-
| void || AddLinkerOption || (const wxString& option) ||
|-

|-
| void || AddLinkLib || (const wxString& lib) ||
|-

|-
| void || AddCompilerOption || (const wxString& option)||
|-

|-
| void || AddIncludeDir || (const wxString& option) ||
|-

|-
| void || AddResourceIncludeDir || (const wxString& option) ||
|-

|-
| void || AddLibDir || (const wxString& option) ||
|-

|-
| void || AddCommandsBeforeBuild || (const wxString& command) ||
|-

|-
| void || AddCommandsAfterBuild || (const wxString& command) ||
|-

|-
| void || RemoveLinkerOption || (const wxString& option) ||
|-

|-
| void || RemoveLinkLib || (const wxString& lib) ||
|-

|-
| void || RemoveCompilerOption || (const wxString& option) ||
|-

|-
| void || RemoveIncludeDir || (const wxString& option) ||
|-

|-
| void || RemoveResourceIncludeDir || (const wxString& option) ||
|-

|-
| void || RemoveLibDir || (const wxString& option) ||
|-

|-
| void || RemoveCommandsBeforeBuild || (const wxString& command) ||
|-

|-
| void || RemoveCommandsAfterBuild || (const wxString& command) ||
|-

|-
| bool || GetAlwaysRunPostBuildSteps || ||
|-

|-
| void || SetAlwaysRunPostBuildSteps || (bool always) ||
|-

|-
| void || SetBuildScripts || (const wxArrayString& scripts) ||
|-

|-
| wxArrayString || GetBuildScripts || ||
|-

|-
| void || AddBuildScript || (const wxString& script) ||
|-

|-
| void || RemoveBuildScript || (const wxString& script) ||
|-

|-
| bool || SetVar || (const wxString& key, const wxString& value, bool onlyIfExists = false) ||
|-

|-
| wxString || GetVar || (const wxString& key) ||
|-

|-
| bool || UnsetVar || (const wxString& key) ||
|-

|-
| void || UnsetAllVars || ( ) ||
|-

|}

== CompileTargetBase ==
Extends CompileOptionsBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || SetTargetFilenameGenerationPolicy || enum, enum ||
|-

|-
| wxString || GetFilename || ||
|-

|-
| wxString || GetTitle || ||
|-

|-
| void || SetTitle || wxString ||
|-

|-
| void || SetOutputFilename || wxString ||
|-

|-
| void || SetWorkingDir || wxString ||
|-

|-
| void || SetObjectOutput || wxString ||
|-

|-
| void || SetDepsOutput || wxString ||
|-

|-
| OptionsRelation || GetOptionRelation || OptionsRelationType ||
|-

|-
| void || SetOptionRelation || OptionsRelationType,OptionsRelation ||
|-

|-
| wxString || GetWorkingDir || ||
|-

|-
| wxString || GetObjectOutput || ||
|-

|-
| wxString || GetDepsOutput || ||
|-

|-
| wxString || GetOutputFilename || ||
|-

|-
| wxString || SuggestOutputFilename || ||
|-

|-
| wxString || GetExecutableFilename || ||
|-

|-
| wxString || GetDynamicLibFilename || ||
|-

|-
| wxString || GetDynamicLibDefFilename || ||
|-

|-
| wxString || GetStaticLibFilename || ||
|-

|-
| wxString || GetBasePath || ||
|-

|-
| void || SetTargetType || TargetType ||
|-

|-
| TargetType || GetTargetType || ||
|-

|-
| wxString || GetExecutionParameters || ||
|-

|-
| void || SetExecutionParameters || wxString ||
|-

|-
| wxString || GetHostApplication || ||
|-

|-
| void || SetHostApplication || wxString ||
|-

|-
| void || SetCompilerID || wxString ||
|-

|-
| wxString || GetCompilerID || ||
|-

|-
| wxString || GetMakeCommandFor || enum ||
|-

|-
| void || SetMakeCommandFor || enum,wxString ||
|-

|-
| bool || MakeCommandsModified || ||
|-

|}

== ProjectBuildTarget ==
Extends CompileTargetBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| cbProject* || GetParentProject || ||
|-

|-
| wxString || GetFullTitle || ||
|-

|-
| wxString || GetExternalDeps || ||
|-

|-
| void || SetExternalDeps || wxString ||
|-

|-
| void || SetAdditionalOutputFiles || wxString ||
|-

|-
| wxString || GetAdditionalOutputFiles || ||
|-

|-
| bool || GetIncludeInTargetAll || ||
|-

|-
| void || SetIncludeInTargetAll || bool ||
|-

|-
| bool || GetCreateDefFile || ||
|-

|-
| void || SetCreateDefFile || bool ||
|-

|-
| bool || GetCreateStaticLib || ||
|-

|-
| void || SetCreateStaticLib || bool ||
|-

|-
| bool || GetUseConsoleRunner || ||
|-

|-
| void || SetUseConsoleRunner || bool ||
|-

|}

== cbProject ==
Extends CompileTargetBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || bool ||
|-

|-
| wxString || GetMakefile || ||
|-

|-
| void || SetMakefile || wxString ||
|-

|-
| bool || IsMakefileCustom || ||
|-

|-
| void || SetMakefileCustom || bool ||
|-

|-
| bool || CloseAllFiles || bool ||
|-

|-
| bool || SaveAllFiles || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || SaveLayout || ||
|-

|-
| bool || LoadLayout || ||
|-

|-
| bool || ShowOptions || || Display the project options dialog
|-

|-
| wxString || GetCommonTopLevelPath || ||
|-

|-
| int || GetFilesCount || || Returns number of files in the project
|-

|-
| ProjectFile* || GetFile || int ||
|-

|-
| ProjectFile* || GetFileByFilename || wxString,bool,bool || See API docs for cbProject::GetFileByName
|-

|-
| bool || RemoveFile || int ||
|-

|-
| ProjectFile* || AddFile || wxString|int,wxString,bool,bool,int || See API docs for cbProject::AddFile
|-

|-
| int || GetBuildTargetsCount || ||
|-

|-
| ProjectBuildTarget* || GetBuildTarget || wxString|int ||
|-

|-
| ProjectBuildTarget* || AddBuildTarget || wxString ||
|-

|-
| bool || RenameBuildTarget || wxString|int,wxString ||
|-

|-
| ProjectBuildTarget* || DuplicateBuildTarget || wxString|int,wxString ||
|-

|-
| bool || RemoveBuildTarget || wxString|int ||
|-

|-
| bool || ExportTargetAsProject || wxString|int ||
|-

|-
| bool || BuildTargetValid || wxString|bool ||
|-

|-
| wxString || GetFirstValidBuildTargetName || bool ||
|-

|-
| void || SetDefaultExecuteTarget || wxString ||
|-

|-
| wxString || GetDefaultExecuteTarget || wxString ||
|-

|-
| bool || SetActiveBuildTarget || wxString ||
|-

|-
| wxString || GetActiveBuildTarget || ||
|-

|-
| int || SelectTarget || int,bool ||
|-

|-
| ProjectBuildTarget* || GetCurrentlyCompilingTarget || ||
|-

|-
| void || SetCurrentlyCompilingTarget || ProjectBuildTarget* ||
|-

|-
| PCHMode || GetModeForPCH || ||
|-

|-
| void || SetModeForPCH || PCHMode ||
|-

|-
| void || SetExtendedObjectNamesGeneration || bool ||
|-

|-
| bool || GetExtendedObjectNamesGeneration || ||
|-

|-
| void || SetNotes || wxString ||
|-

|-
| wxString || GetNotes || ||
|-

|-
| void || SetShowNotesOnLoad || bool ||
|-

|-
| bool || GetShowNotesOnLoad || ||
|-

|-
| void || ShowNotes || bool,bool ||
|-

|-
| void || AddToExtensions || wxString ||
|-

|-
| bool || DefineVirtualBuildTarget || wxString,wxArrayString ||
|-

|-
| bool || HasVirtualBuildTarget|| wxSring ||
|-

|-
| bool || RemoveVirtualBuildTarget|| wxString ||
|-

|-
| wxArrayString || GetVirtualBuildTargets|| ||
|-

|-
| wxArrayString || GetVirtualBuildTargetGroup || wxString ||
|-

|-
| wxArrayString || GetExpandedVirtualBuildTargetGroup|| wxString ||
|-

|-
| bool || CanAddToVirtualBuildTarget || wxSring,wxString ||
|-

|-
| void || SetTitle || wxSring ||
|-
|}

== EditorBase ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| wxString || GetFilename || ||
|-

|-
| void || SetFilename || wxString ||
|-

|-
| wxString || GetShortName || ||
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || bool ||
|-

|-
| wxString || GetTitle || ||
|-

|-
| void || SetTitle || wxString ||
|-

|-
| void || Activate || ||
|-

|-
| bool || Close || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || IsBuiltinEditor || ||
|-

|-
| bool || ThereAreOthers || ||
|-

|-
| void || GotoLine || int,bool ||
|-

|-
| void || ToggleBreakpoint || int,bool ||
|-

|-
| bool || HasBreakpoint || int ||
|-

|-
| void || GotoNextBreakpoint || ||
|-

|-
| void || GotoPreviousBreakpoint || ||
|-

|-
| void || ToggleBookmark || int,bool ||
|-

|-
| bool || HasBookmark || int ||
|-

|-
| void || GotoNextBookmark || ||
|-

|-
| void || GotoPreviousBookmark || ||
|-

|-
| void || Undo || ||
|-

|-
| void || Redo || ||
|-

|-
| void || Cut || ||
|-

|-
| void || Copy || ||
|-

|-
| void || Paste || ||
|-

|-
| bool || CanUndo || ||
|-

|-
| bool || CanRedo || ||
|-

|-
| bool || CanPaste || ||
|-

|-
| bool || HasSelection || ||
|-

|}

== cbEditor ==
Extends EditorBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || SetEditorTitle || wxString ||
|-

|-
| ProjectFile* || GetProjectFile || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || SaveAs || ||
|-

|-
| void || FoldAll || ||
|-

|-
| void || UnfoldAll || ||
|-

|-
| void || ToggleAllFolds || ||
|-

|-
| void || FoldBlockFromLine || int ||
|-

|-
| void || UnfoldBlockFromLine || int ||
|-

|-
| void || ToggleFoldBlockFromLine || int ||
|-

|-
| int || GetLineIndentInSpaces || int ||
|-

|-
| wxString || GetLineIndentString || int ||
|-

|-
| void || Touch || ||
|-

|-
| bool || Reload || bool ||
|-

|-
| void || Print || bool,PrintColourMode,bool ||
|-

|-
| void || AutoComplete || ||
|-

|-
| bool || AddBreakpoint || int,bool ||
|-

|-
| bool || RemoveBreakpoint || int,bool ||
|-

|-
| void || SetText || wxString || this is not present in cbEditor; included to help scripts edit text
|-

|-
| wxString || GetText || || this is not present in cbEditor; included to help scripts edit text
|-

|}

== Constants ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 0px solid gray"
!Constant
!Type
!Remarks
|-

|-
| PLATFORM || int || this defines the platform Code::Blocks is currently running on. It is equal to only one of the following PLATFORM_* constants
|-

|-
| PLATFORM_MSW || int || All Windows platforms
|-

|-
| PLATFORM_GTK || int || All GTK platforms (Linux, BSD, Solaris, Darwin, etc.)
|-

|-
| PLATFORM_MAC || int || All Mac platforms
|-

|-
| PLATFORM_OS2 || int || OS/2 platform
|-

|-
| PLATFORM_X11 || int || All X11 platforms
|-

|-
| PLATFORM_UNKNOWN || int || Unknown platform. Please inform us if PLATFORM == PLATFORM_UNKNOWN so we can make this platform known too ;)
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Message dialog flags'''
|-

|-
| wxOK || int || Flag for Message() 's third argument (flags).
|-

|-
| wxYES_NO || int || -"-
|-

|-
| wxCANCEL || int || -"-
|-

|-
| wxICON_QUESTION || int || -"-
|-

|-
| wxICON_INFORMATION || int || -"-
|-

|-
| wxICON_WARNING || int || -"-
|-

|-
| wxICON_ERROR || int || -"-
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Message dialog return values'''
|-

|-
| wxID_OK || int ||
|-

|-
| wxID_YES || int ||
|-

|-
| wxID_NO || int ||
|-

|-
| wxID_CANCEL || int ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum OptionsRelationType'''
|-

|-
| ortCompilerOptions || enum ||
|-

|-
| ortLinkerOptions || enum ||
|-

|-
| ortIncludeDirs || enum ||
|-

|-
| ortLibDirs || enum ||
|-

|-
| ortResDirs || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum OptionsRelation'''
|-

|-
| orUseParentOptionsOnly || enum ||
|-

|-
| orUseTargetOptionsOnly || enum ||
|-

|-
| orPrependToParentOptions || enum ||
|-

|-
| orAppendToParentOptions || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum TargetType'''
|-

|-
| ttExecutable || enum ||
|-

|-
| ttConsoleOnly || enum ||
|-

|-
| ttStaticLib || enum ||
|-

|-
| ttDynamicLib || enum ||
|-

|-
| ttCommandsOnly || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum MakeCommand'''
|-

|-
| mcClean || enum ||
|-

|-
| mcDistClean || enum ||
|-

|-
| mcBuild || enum ||
|-

|-
| mcCompileFile || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PCHMode'''
|-

|-
| pchSourceDir || enum ||
|-

|-
| pchObjectDir || enum ||
|-

|-
| pchSourceFile || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PrintScope'''
|-

|-
| psSelection || enum ||
|-

|-
| psActiveEditor || enum ||
|-

|-
| psAllOpenEditors || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PrintColourMode'''
|-

|-
| pcmBlackAndWhite || enum ||
|-

|-
| pcmColourOnWhite || enum ||
|-

|-
| pcmInvertColours || enum ||
|-

|-
| pcmAsIs || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum TemplateOutputType'''
|-

|-
| wizProject || enum || TemplateOutputType::totProject
|-

|-
| wizTarget || enum || TemplateOutputType::totTarget
|-

|-
| wizFiles || enum || TemplateOutputType::totFiles
|-

|-
| wizCustom || enum || TemplateOutputType::totCustom
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Other constants'''
|-

|-
| wxFILE_SEP_PATH || wxString || Path separator. "\" for windows, "/" for all other platforms
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''File extensions (e.g. "cbp")'''
|-

|-
| EXT_WORKSPACE || wxString ||
|-

|-
| EXT_CODEBLOCKS || wxString ||
|-

|-
| EXT_DEVCPP || wxString ||
|-

|-
| EXT_MSVC6 || wxString ||
|-

|-
| EXT_MSVC6_WORKSPACE || wxString ||
|-

|-
| EXT_MSVC7 || wxString ||
|-

|-
| EXT_MSVC7_WORKSPACE || wxString ||
|-

|-
| EXT_D || wxString ||
|-

|-
| EXT_F || wxString ||
|-

|-
| EXT_F77 || wxString ||
|-

|-
| EXT_F95 || wxString ||
|-

|-
| EXT_CPP || wxString ||
|-

|-
| EXT_C || wxString ||
|-

|-
| EXT_CC || wxString ||
|-

|-
| EXT_CXX || wxString ||
|-

|-
| EXT_HPP || wxString ||
|-

|-
| EXT_H || wxString ||
|-

|-
| EXT_HH || wxString ||
|-

|-
| EXT_HXX || wxString ||
|-

|-
| EXT_OBJECT || wxString ||
|-

|-
| EXT_XRCRESOURCE || wxString ||
|-

|-
| EXT_STATICLIB || wxString ||
|-

|-
| EXT_DYNAMICLIB || wxString ||
|-

|-
| EXT_EXECUTABLE || wxString ||
|-

|-
| EXT_RESOURCE || wxString ||
|-

|-
| EXT_RESOURCEBIN || wxString ||
|-

|-
| EXT_XML || wxString ||
|-

|-
| EXT_SCRIPT || wxString ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''File extensions with leading dot (e.g. ".cbp")'''
|-

|-
| DOT_EXT_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_CODEBLOCKS || wxString ||
|-

|-
| DOT_EXT_DEVCPP || wxString ||
|-

|-
| DOT_EXT_MSVC6 || wxString ||
|-

|-
| DOT_EXT_MSVC6_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_MSVC7 || wxString ||
|-

|-
| DOT_EXT_MSVC7_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_D || wxString ||
|-

|-
| DOT_EXT_F || wxString ||
|-

|-
| DOT_EXT_F77 || wxString ||
|-

|-
| DOT_EXT_F95 || wxString ||
|-

|-
| DOT_EXT_CPP || wxString ||
|-

|-
| DOT_EXT_C || wxString ||
|-

|-
| DOT_EXT_CC || wxString ||
|-

|-
| DOT_EXT_CXX || wxString ||
|-

|-
| DOT_EXT_HPP || wxString ||
|-

|-
| DOT_EXT_H || wxString ||
|-

|-
| DOT_EXT_HH || wxString ||
|-

|-
| DOT_EXT_HXX || wxString ||
|-

|-
| DOT_EXT_OBJECT || wxString ||
|-

|-
| DOT_EXT_XRCRESOURCE || wxString ||
|-

|-
| DOT_EXT_STATICLIB || wxString ||
|-

|-
| DOT_EXT_DYNAMICLIB || wxString ||
|-

|-
| DOT_EXT_EXECUTABLE || wxString ||
|-

|-
| DOT_EXT_RESOURCE || wxString ||
|-

|-
| DOT_EXT_RESOURCEBIN || wxString ||
|-

|-
| DOT_EXT_XML || wxString ||
|-

|-
| DOT_EXT_SCRIPT || wxString ||
|-

|}

== See also ==

* [[Scripting Code::Blocks|Scripting index]]

Scripting commands

2008-04-27T21:20:38Z

Mariocup: /* cbProject */

[[Category:Scripting Code::Blocks]]
Scripting is no good if all you can do is use the scripting language's built-in commands only. The host application (Code::Blocks) needs to expose parts of its internals to scripts, so scripts can use and control the host.

Code::Blocks has exposed a very large chunk of its SDK to scripts. This makes scripting in Code::Blocks nearly as powerful as native code (C++).

In this page all the exported constants, functions and classes are documented as a quick reference. For detailed documentation on each function/class, refer to the Code::Blocks SDK documentation.

''NOTE: Please remember that [http://www.squirrel-lang.org Squirrel] is typeless. Data types mentioned below are only used for documentation purposes.''

''NOTE: Please keep in mind that if a function has default parameters in C++ (which can be ommitted), you still have to type them for scripts (for e.g. exposed wxWidgets functionality). This means you *have* to use e.g. wxFileName.GetFullPath(wxPATH_NATIVE) instead of e.g only wxFileName.GetFullPath().

== Application object ==
The application object is accessed through the variable named '''<tt>App</tt>'''. Currently it has no bound functions...

== Global functions ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || Log || wxString || logs to the application log
|-

|-
| void || LogDebug || wxString || logs to the debug log
|-

|-
| void || LogWarning || wxString || logs a warning
|-

|-
| void || LogError || wxString || logs an error
|-

|-
| int || Message || wxString,wxString,int || arg1=msg, arg2=caption, arg3=buttons; see API docs for cbMessageBox()
|-

|-
| void || ShowMessage || wxString ||
|-

|-
| void || ShowWarning || wxString ||
|-

|-
| void || ShowError || wxString ||
|-

|-
| void || ShowInfo || wxString ||
|-

|-
| wxString || ReplaceMacros || wxString,bool ||
|-

|-
| ScriptingManager* || GetScriptingManager || ||
|-

|-
| ProjectManager* || GetProjectManager || ||
|-

|-
| EditorManager* || GetEditorManager || ||
|-

|-
| ConfigManager* || GetConfigManager || ||
|-

|-
| UserVariableManager* || GetUserVariableManager || ||
|-

|-
| CompilerFactory* || GetCompilerFactory || ||
|-

|-
| wxArrayString || GetArrayFromString || wxString,wxString,bool ||
|-

|-
| wxString || GetStringFromArray || wxArrayString,wxString,bool ||
|-

|-
| wxString || EscapeSpaces || wxString ||
|-

|-
| wxString || UnixFilename || wxString ||
|-

|-
| FileType || FileTypeOf || wxString ||
|-

|-
| wxString || URLEncode || wxString ||
|-

|-
| void || NotifyMissingFile || wxString ||
|-

|-
| int || GetPlatformsFromString || wxString ||
|-

|-
| wxString || GetStringFromPlatforms || int,bool||
|-

|-
| void|| Display || wxString,wxString,int,int ||
|-

|-
| wxString || GetFolder || int || see API docs for ConfigManager::GetFolder()
|-

|-
| wxString || LocateDataFile|| wxString, int || see API docs for ConfigManager::LocateDataFile()
|-

|-
| bool || InstallPlugin || wxString,bool, bool || Install a binary plugin
|-

|-
| void || Include || wxString || similar to C/C++ ''<tt>#include "name"</tt>''
|-

|-
| bool || IsNull || void* ||
|-

|-
| wxString || _T || const char* || basically this is the wxString constructor
|-

|-
| bool || wxLaunchDefaultBrowser || wxString ||
|-

|-
| wxColour || wxGetColourFromUser || [wxColour] ||
|-

|-
| long || wxGetNumberFromUser || wxString,wxString,wxString ||
|-

|-
| wxString || wxGetPasswordFromUser || wxString,wxString,wxString ||
|-

|-
| wxString || wxGetTextFromUser || wxString,wxString,wxString ||
|-

|}

== ScriptingManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || RegisterScriptMenu || wxString, wxString || registers the script file (arg1) under a menu item (arg2).
e.g. <tt>GetScriptingManager().RegisterScriptMenu(_T("sample.script"), _T("Scripts/Sample script"))</tt>;
|-

|}

Notes about the <tt>RegisterScriptMenu</tt> function: 
* The second argument (menu item) is a string containing the full menu path to create the menu item. The path separator is a slash (/). For example, the string "Settings/Sample menu/Sample item" would create the menu path "Settings->Sample menu->Sample item".
* When each part of the path is evaluated, it is checked whether it starts with a number followed by a colon (:). If so then this is considered to be a menu index in the parent menu and the menu is inserted at that index instead of being appended to the menu. The number and colon are removed from the string.
* If the menu item starts with a dash (-), then a separator line is prepended in the menu before the menu item (e.g. "Scripts/'''-'''Sample script").
* For your convenience, all menu items created using this function have one extra functionality: if you keep the SHIFT key pressed while clicking on any of these "script menu items", instead of running the attached script, Code::Blocks will open it in the editor for you to view/edit :).
* Have a look at the [[Startup script#Example|startup script example]].

== ConfigManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| int || Read || int,int ||
|-

|-
| bool || Read || bool,bool ||
|-

|-
| float || Read || float,float ||
|-

|-
| wxString || Read || wxString,wxString ||
|-

|-
| void || Write || int,int ||
|-

|-
| void || Write || bool,bool ||
|-

|-
| void || Write || float,float ||
|-

|-
| void || Write || wxString,wxString[,bool] ||
|-

|}

== ProjectManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| wxString || GetDefaultPath || ( ) ||
|-

|-
| void || SetDefaultPath || (const wxString& path) ||
|-

|-
| cbProject* || GetActiveProject || ( ) ||
|-

|-
| void || SetProject || (cbProject* project, bool refresh = true) ||
|-

|-
| bool || LoadWorkspace || (const wxString& filename = DEFAULT_WORKSPACE)||
|-

|-
| bool || SaveWorkspace || ( ) ||
|-

|-
| bool || SaveWorkspaceAs || (const wxString& filename) ||
|-

|-
| bool || CloseWorkspace || ( ) ||
|-

|-
| cbProject* || IsOpen || (const wxString& filename) ||
|-

|-
| cbProject* || LoadProject || (const wxString& filename, bool activateIt = true) ||
|-

|-
| bool || SaveProject || (cbProject* project) ||
|-

|-
| bool || SaveProjectAs || (cbProject* project) ||
|-

|-
| bool || SaveActiveProject || ( ) ||
|-

|-
| bool || SaveActiveProjectAs || ( ) ||
|-

|-
| bool || SaveAllProjects || ( ) ||
|-

|-
| bool || CloseProject || (cbProject* project, bool dontsave = false, bool refresh = true) ||
|-

|-
| bool || CloseActiveProject || (bool dontsave = false) ||
|-

|-
| bool || CloseAllProjects || (bool dontsave = false) ||
|-

|-
| cbProject* || NewProject || (const wxString& filename = wxEmptyString) ||
|-

|-
| int || AddFileToProject || (const wxString& filename, cbProject* project = 0L, int target = -1) ||
|-

|-
| int || AskForBuildTargetIndex || (cbProject* project = 0L) ||

|-
| void || RebuildTree || ( ) ||
|-

|-
| bool || AddProjectDependency || (cbProject* base, cbProject* dependsOn) ||
|-

|-
| void || RemoveProjectDependency || (cbProject* base, cbProject* doesNotDependOn) ||
|-

|-
| void || ClearProjectDependencies || (cbProject* base) ||
|-

|-
| void || RemoveProjectFromAllDependencies || (cbProject* base) ||
|-

|-
| ProjectsArray* || GetDependenciesForProject || (cbProject* base) ||
|-

|-
| void || ConfigureProjectDependencies || (cbProject* base = 0) ||
|-
|}

== EditorManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || Configure || ( ) ||
|-

|-
| cbEditor* || New || (const wxString& newFileName = wxEmptyString) ||
|-

|-
| cbEditor* || Open || (const wxString& filename) ||
|-

|-
| cbEditor* || IsBuiltinOpen || (const wxString& filename) ||
|-

|-
| cbEditor* || GetBuiltinEditor || (const wxString& filename)|(int index) ||
|-

|-
| cbEditor* || GetBuiltinActiveEditor || ( ) ||
|-

|-
| EditorBase* || GetActiveEditor || ( ) ||
|-

|-
| void || ActivateNext || ( ) ||
|-

|-
| void || ActivatePrevious || ( ) ||
|-

|-
| bool || SwapActiveHeaderSource || ( ) ||
|-

|-
| bool || CloseActive || (bool dontsave = false) ||
|-

|-
| bool || Close || (const wxString& filename,bool dontsave = false)|(int index,bool dontsave = false),(EditorBase* editor,bool dontsave = false) ||
|-

|-
| bool || CloseAll || (bool dontsave=false) ||
|-

|-
| bool || Save || (const wxString& filename)|(int index)||
|-

|-
| bool || SaveActive || ( ) ||
|-

|-
| bool || SaveAs || (int index) ||
|-

|-
| bool || SaveActiveAs || ( ) ||
|-

|-
| bool || SaveAll || ( ) ||
|-

|-
| int || ShowFindDialog || (bool replace, bool explicitly_find_in_files = false),bool ||
|-

|}

== UserVariableManager ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || Exists || (const wxString& variable) ||
|-

|}

== IO namespace ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || DirectoryExists || (const wxString& dir) ||
|-

|-
| wxString || SelectDirectory || (const wxString& message, const wxString& initialPath, bool showCreateDirButton) ||
|-

|-
| bool || '''CreateDirectory''' || (const wxString& full_path, int perms) || arg1=dir, arg2=permissions
|-

|-
| bool || '''RemoveDirectory''' || (const wxString& src) ||
|-

|-
| bool || '''CopyFile''' ||(const wxString& src, const wxString& dst, bool overwrite) || src,dest,overwrite
|-

|-
| bool || '''RenameFile''' || (const wxString& src, const wxString& dst) || old,new
|-

|-
| bool || '''RemoveFile''' || (const wxString& src) ||
|-

|-
| bool || FileExists || (const wxString& file) ||
|-

|-
| wxString || SelectFile || (const wxString& title, const wxString& defaultFile, const wxString& filter) ||
|-

|-
| bool || ReadFileContents || (const wxString& filename) ||
|-

|-
| bool || '''WriteFileContents''' || (const wxString& filename, const wxString& contents) || filename,contents
|-

|-
| int || '''Execute''' || (const wxString& command) ||
|-

|-
| wxString || '''ExecuteAndGetOutput''' || (const wxString& command) ||
|-

|-
| wxString || GetCwd || ( ) ||
|-

|-
| void || SetCwd || (const wxString& dir) || directory (currently working directory)
|-

|}

'''Notes:'''
The namespaces are accesses by prepending it's name (e.g. "IO.") to the scripting function, e.g. "IO.DirectoryExists(...)". "::" is only used when declaring the members of the namespace.
The functions in bold are going through the scripts security layer so there is no guarantee calling them will succeed. You should always examine the return value...
There exists one constant too, named ''allowInsecureScripts'', which allow you to test whether Code::Blocks was compiled with the functions going through the security layer.

== CompilerFactory ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| bool || IsValidCompilerID || (const wxString& id) ||
|-

|-
| int || GetCompilerIndex || (const wxString& id) ||
|-

|-
| wxString || GetDefaultCompilerID || ( ) ||
|-

|-
| wxString || GetCompilerVersionString || (const wxString& Id) ||
|-

|-
| bool || CompilerInheritsFrom || ( ) ||
|-

|}

== wxString ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || operator+ || ||
|-

|-
| bool || operator< || ||
|-

|-
| bool || operator<= || ||
|-

|-
| bool || operator>= || ||
|-

|-
| bool || operator> || ||
|-

|-
| int || Find || wxString ||
|-

|-
| bool || Matches || wxString ||
|-

|-
| void || AddChar || char ||
|-

|-
| char || GetChar || int ||
|-

|-
| bool || IsEmpty || ||
|-

|-
| int || Length || ||
|-

|-
| int || length || || same as Length()
|-

|-
| int || len || || same as Length()
|-

|-
| int || size || || same as Length()
|-

|-
| wxString || Lower || ||
|-

|-
| wxString || LowerCase || || same as Lower()
|-

|-
| void || MakeLower || ||
|-

|-
| wxString || Upper || ||
|-

|-
| wxString || UpperCase || || same as Upper()
|-

|-
| void || MakeUpper || ||
|-

|-
| wxString || Mid || int,int ||
|-

|-
| void || Remove || int,int ||
|-

|-
| void || RemoveLast || ||
|-

|-
| int || Replace || wxString,wxString[,bool] ||
|-

|-
| wxString || Right || int ||
|-

|-
| wxString || AfterFirst || char ||
|-

|-
| wxString || AfterLast || char ||
|-

|-
| wxString || BeforeFirst || char ||
|-

|-
| wxString || BeforeLast || char ||
|-
|}
''NOTE: Is instantiated in a script using: local my_wxstring = ::wxString();

== wxArrayString ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || Add || wxString, size_t || arg1=string, arg2=number of copies to add
|-

|-
| void || Clear || ||
|-

|-
| int || GetCount || ||
|-

|-
| wxString || Item || int ||
|-

|}
''NOTE: Is instantiated in a script using: local my_wxarraystring = ::wxArrayString();

== wxColour ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| byte || Red || ||
|-

|-
| byte || Green || ||
|-

|-
| byte || Blue || ||
|-

|-
| void || Set || byte,byte,byte ||
|-

|}
''NOTE: Is instantiated in a script using: local my_wxcolour = ::wxColour();

== ProjectFile ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || AddBuildTarget || (const wxString& targetName)||
|-

|-
| void || RenameBuildTarget || (const wxString& oldTargetName, const wxString& newTargetName) ||
|-

|-
| void || RemoveBuildTarget || (const wxString& targetName)||
|-

|-
| wxString || GetBaseName || ( ) ||
|-

|-
| wxString || GetObjName || ( ) ||
|-

|-
| void || SetObjName || (const wxString& targetName) ||
|-

|-
| cbProject* || GetParentProject || ( ) ||
|-

|-
| wxString|| GetCustomBuildCommand|| (const wxString& compilerId) ||
|-

|-
| void || SetCustomBuildCommand || (const wxString& compilerId, const wxString& newBuildCommand) ||
|-

|-
| bool || GetUseCustomBuildCommand|| (const wxString& compilerId) ||
|-

|-
| void || SetUseCustomBuildCommand || (const wxString& compilerId, bool useCustomBuildCommand) ||
|-

|-
| wxFileName || file || || (variable)
|-

|-
| wxString || relativeFilename || || (variable)
|-

|-
| wxString || relativeToCommonTopLevelPath || || (variable)
|-

|-
| bool || compile || || (variable)
|-

|-
| bool || link || || (variable)
|-

|-
| int || weight || || (variable)
|-

|-
| wxString || compilerVar || || (variable)
|-

|}

== CompileOptionsBase ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments in Prototype
!Remarks
|-

|-
| void || AddPlatform || (int platform) || windows,unix,mac
|-

|-
| void || RemovePlatform || (int platform) ||
|-

|-
| void || SetPlatforms || (int platform) ||
|-

|-
| void || GetPlatforms || ||
|-

|-
| void || SupportsCurrentPlatform || (int platform) ||
|-

|-
| void || SetLinkerOptions || (const wxArrayString& linkerOpts) ||
|-

|-
| void || SetLinkLibs || (const wxArrayString& linkLibs) ||
|-

|-
| void || SetCompilerOptions || (const wxArrayString& compilerOpts) ||
|-

|-
| void || SetIncludeDirs || (const wxArrayString& includeDirs) ||
|-

|-
| void || SetResourceIncludeDirs || (const wxString& option) ||
|-

|-
| void || SetLibDirs || (const wxArrayString& libDirs) ||
|-

|-
| void || SetCommandsBeforeBuild || (const wxArrayString& commands) ||
|-

|-
| void || SetCommandsAfterBuild || (const wxArrayString& commands) ||
|-

|-
| wxArrayString || GetLinkerOptions || ||
|-

|-
| wxArrayString || GetLinkLibs || ||
|-

|-
| wxArrayString || GetCompilerOptions || ||
|-

|-
| wxArrayString || GetIncludeDirs || ||
|-

|-
| wxArrayString || GetResourceIncludeDirs || ||
|-

|-
| wxArrayString || GetLibDirs || ||
|-

|-
| wxArrayString || GetCommandsBeforeBuild || ||
|-

|-
| wxArrayString || GetCommandsAfterBuild || ||
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || (bool modified) ||
|-

|-
| void || AddLinkerOption || (const wxString& option) ||
|-

|-
| void || AddLinkLib || (const wxString& lib) ||
|-

|-
| void || AddCompilerOption || (const wxString& option)||
|-

|-
| void || AddIncludeDir || (const wxString& option) ||
|-

|-
| void || AddResourceIncludeDir || (const wxString& option) ||
|-

|-
| void || AddLibDir || (const wxString& option) ||
|-

|-
| void || AddCommandsBeforeBuild || (const wxString& command) ||
|-

|-
| void || AddCommandsAfterBuild || (const wxString& command) ||
|-

|-
| void || RemoveLinkerOption || (const wxString& option) ||
|-

|-
| void || RemoveLinkLib || (const wxString& lib) ||
|-

|-
| void || RemoveCompilerOption || (const wxString& option) ||
|-

|-
| void || RemoveIncludeDir || (const wxString& option) ||
|-

|-
| void || RemoveResourceIncludeDir || (const wxString& option) ||
|-

|-
| void || RemoveLibDir || (const wxString& option) ||
|-

|-
| void || RemoveCommandsBeforeBuild || (const wxString& command) ||
|-

|-
| void || RemoveCommandsAfterBuild || (const wxString& command) ||
|-

|-
| bool || GetAlwaysRunPostBuildSteps || ||
|-

|-
| void || SetAlwaysRunPostBuildSteps || (bool always) ||
|-

|-
| void || SetBuildScripts || (const wxArrayString& scripts) ||
|-

|-
| wxArrayString || GetBuildScripts || ||
|-

|-
| void || AddBuildScript || (const wxString& script) ||
|-

|-
| void || RemoveBuildScript || (const wxString& script) ||
|-

|-
| bool || SetVar || 8const wxString& key, const wxString& value, bool onlyIfExists = false) ||
|-

|-
| wxString || GetVar || (const wxString& key) ||
|-

|-
| bool || UnsetVar || (const wxString& key) ||
|-

|-
| void || UnsetAllVars || ( ) ||
|-

|}

== CompileTargetBase ==
Extends CompileOptionsBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || SetTargetFilenameGenerationPolicy || enum, enum ||
|-

|-
| wxString || GetFilename || ||
|-

|-
| wxString || GetTitle || ||
|-

|-
| void || SetTitle || wxString ||
|-

|-
| void || SetOutputFilename || wxString ||
|-

|-
| void || SetWorkingDir || wxString ||
|-

|-
| void || SetObjectOutput || wxString ||
|-

|-
| void || SetDepsOutput || wxString ||
|-

|-
| OptionsRelation || GetOptionRelation || OptionsRelationType ||
|-

|-
| void || SetOptionRelation || OptionsRelationType,OptionsRelation ||
|-

|-
| wxString || GetWorkingDir || ||
|-

|-
| wxString || GetObjectOutput || ||
|-

|-
| wxString || GetDepsOutput || ||
|-

|-
| wxString || GetOutputFilename || ||
|-

|-
| wxString || SuggestOutputFilename || ||
|-

|-
| wxString || GetExecutableFilename || ||
|-

|-
| wxString || GetDynamicLibFilename || ||
|-

|-
| wxString || GetDynamicLibDefFilename || ||
|-

|-
| wxString || GetStaticLibFilename || ||
|-

|-
| wxString || GetBasePath || ||
|-

|-
| void || SetTargetType || TargetType ||
|-

|-
| TargetType || GetTargetType || ||
|-

|-
| wxString || GetExecutionParameters || ||
|-

|-
| void || SetExecutionParameters || wxString ||
|-

|-
| wxString || GetHostApplication || ||
|-

|-
| void || SetHostApplication || wxString ||
|-

|-
| void || SetCompilerID || wxString ||
|-

|-
| wxString || GetCompilerID || ||
|-

|-
| wxString || GetMakeCommandFor || enum ||
|-

|-
| void || SetMakeCommandFor || enum,wxString ||
|-

|-
| bool || MakeCommandsModified || ||
|-

|}

== ProjectBuildTarget ==
Extends CompileTargetBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| cbProject* || GetParentProject || ||
|-

|-
| wxString || GetFullTitle || ||
|-

|-
| wxString || GetExternalDeps || ||
|-

|-
| void || SetExternalDeps || wxString ||
|-

|-
| void || SetAdditionalOutputFiles || wxString ||
|-

|-
| wxString || GetAdditionalOutputFiles || ||
|-

|-
| bool || GetIncludeInTargetAll || ||
|-

|-
| void || SetIncludeInTargetAll || bool ||
|-

|-
| bool || GetCreateDefFile || ||
|-

|-
| void || SetCreateDefFile || bool ||
|-

|-
| bool || GetCreateStaticLib || ||
|-

|-
| void || SetCreateStaticLib || bool ||
|-

|-
| bool || GetUseConsoleRunner || ||
|-

|-
| void || SetUseConsoleRunner || bool ||
|-

|}

== cbProject ==
Extends CompileTargetBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || bool ||
|-

|-
| wxString || GetMakefile || ||
|-

|-
| void || SetMakefile || wxString ||
|-

|-
| bool || IsMakefileCustom || ||
|-

|-
| void || SetMakefileCustom || bool ||
|-

|-
| bool || CloseAllFiles || bool ||
|-

|-
| bool || SaveAllFiles || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || SaveLayout || ||
|-

|-
| bool || LoadLayout || ||
|-

|-
| bool || ShowOptions || || Display the project options dialog
|-

|-
| wxString || GetCommonTopLevelPath || ||
|-

|-
| int || GetFilesCount || || Returns number of files in the project
|-

|-
| ProjectFile* || GetFile || int ||
|-

|-
| ProjectFile* || GetFileByFilename || wxString,bool,bool || See API docs for cbProject::GetFileByName
|-

|-
| bool || RemoveFile || int ||
|-

|-
| ProjectFile* || AddFile || wxString|int,wxString,bool,bool,int || See API docs for cbProject::AddFile
|-

|-
| int || GetBuildTargetsCount || ||
|-

|-
| ProjectBuildTarget* || GetBuildTarget || wxString|int ||
|-

|-
| ProjectBuildTarget* || AddBuildTarget || wxString ||
|-

|-
| bool || RenameBuildTarget || wxString|int,wxString ||
|-

|-
| ProjectBuildTarget* || DuplicateBuildTarget || wxString|int,wxString ||
|-

|-
| bool || RemoveBuildTarget || wxString|int ||
|-

|-
| bool || ExportTargetAsProject || wxString|int ||
|-

|-
| bool || BuildTargetValid || wxString|bool ||
|-

|-
| wxString || GetFirstValidBuildTargetName || bool ||
|-

|-
| void || SetDefaultExecuteTarget || wxString ||
|-

|-
| wxString || GetDefaultExecuteTarget || wxString ||
|-

|-
| bool || SetActiveBuildTarget || wxString ||
|-

|-
| wxString || GetActiveBuildTarget || ||
|-

|-
| int || SelectTarget || int,bool ||
|-

|-
| ProjectBuildTarget* || GetCurrentlyCompilingTarget || ||
|-

|-
| void || SetCurrentlyCompilingTarget || ProjectBuildTarget* ||
|-

|-
| PCHMode || GetModeForPCH || ||
|-

|-
| void || SetModeForPCH || PCHMode ||
|-

|-
| void || SetExtendedObjectNamesGeneration || bool ||
|-

|-
| bool || GetExtendedObjectNamesGeneration || ||
|-

|-
| void || SetNotes || wxString ||
|-

|-
| wxString || GetNotes || ||
|-

|-
| void || SetShowNotesOnLoad || bool ||
|-

|-
| bool || GetShowNotesOnLoad || ||
|-

|-
| void || ShowNotes || bool,bool ||
|-

|-
| void || AddToExtensions || wxString ||
|-

|-
| bool || DefineVirtualBuildTarget || wxString,wxArrayString ||
|-

|-
| bool || HasVirtualBuildTarget|| wxSring ||
|-

|-
| bool || RemoveVirtualBuildTarget|| wxString ||
|-

|-
| wxArrayString || GetVirtualBuildTargets|| ||
|-

|-
| wxArrayString || GetVirtualBuildTargetGroup || wxString ||
|-

|-
| wxArrayString || GetExpandedVirtualBuildTargetGroup|| wxString ||
|-

|-
| bool || CanAddToVirtualBuildTarget || wxSring,wxString ||
|-

|-
| void || SetTitle || wxSring ||
|-
|}

== EditorBase ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| wxString || GetFilename || ||
|-

|-
| void || SetFilename || wxString ||
|-

|-
| wxString || GetShortName || ||
|-

|-
| bool || GetModified || ||
|-

|-
| void || SetModified || bool ||
|-

|-
| wxString || GetTitle || ||
|-

|-
| void || SetTitle || wxString ||
|-

|-
| void || Activate || ||
|-

|-
| bool || Close || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || IsBuiltinEditor || ||
|-

|-
| bool || ThereAreOthers || ||
|-

|-
| void || GotoLine || int,bool ||
|-

|-
| void || ToggleBreakpoint || int,bool ||
|-

|-
| bool || HasBreakpoint || int ||
|-

|-
| void || GotoNextBreakpoint || ||
|-

|-
| void || GotoPreviousBreakpoint || ||
|-

|-
| void || ToggleBookmark || int,bool ||
|-

|-
| bool || HasBookmark || int ||
|-

|-
| void || GotoNextBookmark || ||
|-

|-
| void || GotoPreviousBookmark || ||
|-

|-
| void || Undo || ||
|-

|-
| void || Redo || ||
|-

|-
| void || Cut || ||
|-

|-
| void || Copy || ||
|-

|-
| void || Paste || ||
|-

|-
| bool || CanUndo || ||
|-

|-
| bool || CanRedo || ||
|-

|-
| bool || CanPaste || ||
|-

|-
| bool || HasSelection || ||
|-

|}

== cbEditor ==
Extends EditorBase.

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"
|- style="background: #ececec; border: 0px solid gray"
!Return value
!Name
!Arguments
!Remarks
|-

|-
| void || SetEditorTitle || wxString ||
|-

|-
| ProjectFile* || GetProjectFile || ||
|-

|-
| bool || Save || ||
|-

|-
| bool || SaveAs || ||
|-

|-
| void || FoldAll || ||
|-

|-
| void || UnfoldAll || ||
|-

|-
| void || ToggleAllFolds || ||
|-

|-
| void || FoldBlockFromLine || int ||
|-

|-
| void || UnfoldBlockFromLine || int ||
|-

|-
| void || ToggleFoldBlockFromLine || int ||
|-

|-
| int || GetLineIndentInSpaces || int ||
|-

|-
| wxString || GetLineIndentString || int ||
|-

|-
| void || Touch || ||
|-

|-
| bool || Reload || bool ||
|-

|-
| void || Print || bool,PrintColourMode,bool ||
|-

|-
| void || AutoComplete || ||
|-

|-
| bool || AddBreakpoint || int,bool ||
|-

|-
| bool || RemoveBreakpoint || int,bool ||
|-

|-
| void || SetText || wxString || this is not present in cbEditor; included to help scripts edit text
|-

|-
| wxString || GetText || || this is not present in cbEditor; included to help scripts edit text
|-

|}

== Constants ==

{| border="1" cellpadding="3" cellspacing="0" style="border: 1px solid gray; border-collapse: collapse;"

|- style="background: #ececec; border: 0px solid gray"
!Constant
!Type
!Remarks
|-

|-
| PLATFORM || int || this defines the platform Code::Blocks is currently running on. It is equal to only one of the following PLATFORM_* constants
|-

|-
| PLATFORM_MSW || int || All Windows platforms
|-

|-
| PLATFORM_GTK || int || All GTK platforms (Linux, BSD, Solaris, Darwin, etc.)
|-

|-
| PLATFORM_MAC || int || All Mac platforms
|-

|-
| PLATFORM_OS2 || int || OS/2 platform
|-

|-
| PLATFORM_X11 || int || All X11 platforms
|-

|-
| PLATFORM_UNKNOWN || int || Unknown platform. Please inform us if PLATFORM == PLATFORM_UNKNOWN so we can make this platform known too ;)
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Message dialog flags'''
|-

|-
| wxOK || int || Flag for Message() 's third argument (flags).
|-

|-
| wxYES_NO || int || -"-
|-

|-
| wxCANCEL || int || -"-
|-

|-
| wxICON_QUESTION || int || -"-
|-

|-
| wxICON_INFORMATION || int || -"-
|-

|-
| wxICON_WARNING || int || -"-
|-

|-
| wxICON_ERROR || int || -"-
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Message dialog return values'''
|-

|-
| wxID_OK || int ||
|-

|-
| wxID_YES || int ||
|-

|-
| wxID_NO || int ||
|-

|-
| wxID_CANCEL || int ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum OptionsRelationType'''
|-

|-
| ortCompilerOptions || enum ||
|-

|-
| ortLinkerOptions || enum ||
|-

|-
| ortIncludeDirs || enum ||
|-

|-
| ortLibDirs || enum ||
|-

|-
| ortResDirs || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum OptionsRelation'''
|-

|-
| orUseParentOptionsOnly || enum ||
|-

|-
| orUseTargetOptionsOnly || enum ||
|-

|-
| orPrependToParentOptions || enum ||
|-

|-
| orAppendToParentOptions || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum TargetType'''
|-

|-
| ttExecutable || enum ||
|-

|-
| ttConsoleOnly || enum ||
|-

|-
| ttStaticLib || enum ||
|-

|-
| ttDynamicLib || enum ||
|-

|-
| ttCommandsOnly || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum MakeCommand'''
|-

|-
| mcClean || enum ||
|-

|-
| mcDistClean || enum ||
|-

|-
| mcBuild || enum ||
|-

|-
| mcCompileFile || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PCHMode'''
|-

|-
| pchSourceDir || enum ||
|-

|-
| pchObjectDir || enum ||
|-

|-
| pchSourceFile || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PrintScope'''
|-

|-
| psSelection || enum ||
|-

|-
| psActiveEditor || enum ||
|-

|-
| psAllOpenEditors || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum PrintColourMode'''
|-

|-
| pcmBlackAndWhite || enum ||
|-

|-
| pcmColourOnWhite || enum ||
|-

|-
| pcmInvertColours || enum ||
|-

|-
| pcmAsIs || enum ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''enum TemplateOutputType'''
|-

|-
| wizProject || enum || TemplateOutputType::totProject
|-

|-
| wizTarget || enum || TemplateOutputType::totTarget
|-

|-
| wizFiles || enum || TemplateOutputType::totFiles
|-

|-
| wizCustom || enum || TemplateOutputType::totCustom
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''Other constants'''
|-

|-
| wxFILE_SEP_PATH || wxString || Path separator. "\" for windows, "/" for all other platforms
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''File extensions (e.g. "cbp")'''
|-

|-
| EXT_WORKSPACE || wxString ||
|-

|-
| EXT_CODEBLOCKS || wxString ||
|-

|-
| EXT_DEVCPP || wxString ||
|-

|-
| EXT_MSVC6 || wxString ||
|-

|-
| EXT_MSVC6_WORKSPACE || wxString ||
|-

|-
| EXT_MSVC7 || wxString ||
|-

|-
| EXT_MSVC7_WORKSPACE || wxString ||
|-

|-
| EXT_D || wxString ||
|-

|-
| EXT_F || wxString ||
|-

|-
| EXT_F77 || wxString ||
|-

|-
| EXT_F95 || wxString ||
|-

|-
| EXT_CPP || wxString ||
|-

|-
| EXT_C || wxString ||
|-

|-
| EXT_CC || wxString ||
|-

|-
| EXT_CXX || wxString ||
|-

|-
| EXT_HPP || wxString ||
|-

|-
| EXT_H || wxString ||
|-

|-
| EXT_HH || wxString ||
|-

|-
| EXT_HXX || wxString ||
|-

|-
| EXT_OBJECT || wxString ||
|-

|-
| EXT_XRCRESOURCE || wxString ||
|-

|-
| EXT_STATICLIB || wxString ||
|-

|-
| EXT_DYNAMICLIB || wxString ||
|-

|-
| EXT_EXECUTABLE || wxString ||
|-

|-
| EXT_RESOURCE || wxString ||
|-

|-
| EXT_RESOURCEBIN || wxString ||
|-

|-
| EXT_XML || wxString ||
|-

|-
| EXT_SCRIPT || wxString ||
|-

|-
| colspan="3" align="center" style="background: #f8f8f8;" | '''File extensions with leading dot (e.g. ".cbp")'''
|-

|-
| DOT_EXT_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_CODEBLOCKS || wxString ||
|-

|-
| DOT_EXT_DEVCPP || wxString ||
|-

|-
| DOT_EXT_MSVC6 || wxString ||
|-

|-
| DOT_EXT_MSVC6_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_MSVC7 || wxString ||
|-

|-
| DOT_EXT_MSVC7_WORKSPACE || wxString ||
|-

|-
| DOT_EXT_D || wxString ||
|-

|-
| DOT_EXT_F || wxString ||
|-

|-
| DOT_EXT_F77 || wxString ||
|-

|-
| DOT_EXT_F95 || wxString ||
|-

|-
| DOT_EXT_CPP || wxString ||
|-

|-
| DOT_EXT_C || wxString ||
|-

|-
| DOT_EXT_CC || wxString ||
|-

|-
| DOT_EXT_CXX || wxString ||
|-

|-
| DOT_EXT_HPP || wxString ||
|-

|-
| DOT_EXT_H || wxString ||
|-

|-
| DOT_EXT_HH || wxString ||
|-

|-
| DOT_EXT_HXX || wxString ||
|-

|-
| DOT_EXT_OBJECT || wxString ||
|-

|-
| DOT_EXT_XRCRESOURCE || wxString ||
|-

|-
| DOT_EXT_STATICLIB || wxString ||
|-

|-
| DOT_EXT_DYNAMICLIB || wxString ||
|-

|-
| DOT_EXT_EXECUTABLE || wxString ||
|-

|-
| DOT_EXT_RESOURCE || wxString ||
|-

|-
| DOT_EXT_RESOURCEBIN || wxString ||
|-

|-
| DOT_EXT_XML || wxString ||
|-

|-
| DOT_EXT_SCRIPT || wxString ||
|-

|}

== See also ==

* [[Scripting Code::Blocks|Scripting index]]

User talk:Mariocup

2008-04-09T20:09:36Z

Mariocup:

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Insert Class method Declaration/Implementation==
The context menu in the editor Insert/Class method declaration/implementation shows the list of classes etc. but lacks of the ability of filter mechanism while typing text text like it is available for Goto File or Goto Function.--[[User:Mariocup|Mariocup]]

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-03-15T13:46:30Z

Mariocup: /* Multiple Watch Windows */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories". The name of the watch windows should be editable.

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-03-14T21:55:57Z

Mariocup:

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments --[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories".

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-03-14T21:54:43Z

Mariocup: /* Section Browser */

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
The search dialog should provide a filter for the search scope: Function, Class etc.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Search Dialogue ==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different sections.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories".

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-03-14T12:36:33Z

Mariocup:

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
The search dialog should provide a filter for the search scope: Function, Class etc.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
== Setting Defines ==
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Search Dialogue ==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different settings.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories".

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-03-14T12:35:58Z

Mariocup:

= Editor Improvements =

==Resize editor window==
A double click on a tab of an opened file should enlarge the editor window, and put the Log & Others and the management panel (F2 and Alt+F2) in the background. If you double click again on the tab, the window will be resized to the original size and the panels are visible again.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Icons in the Management window==
If you want to switch the different views in the management window you have to scroll, the tabs (projects, symbols, Files etc.). It would be easier for the user to have different icons like (http://kile.sourceforge.net/showscreenshot.php?id=2) in the margin to switch between the views. If you select e.g. the project icon then the project view will appear. Clicking again on the same icon will collapse the project view.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Save copy as==
Sometimes user want to make a backup of files or want to save a copy at a different location. Therefore a menu save copy as could be useful.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Clipboard History==
Editors like vi or Jedit offer clipboards for copy and paste. The user can select in which register is put the content of the clipboard and can paste the content of one of the buffer/register.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Search Dialog==
The Thread Search dialogue should be added also to the normal search dialogue.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Scope for Search==
The search dialog should provide a filter for the search scope: Function, Class etc.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Window docking==
Docking/Undocking of windows in CB with split view (See patch of dmoore for detaching CB windows).--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Incremental Search==
The search for a word will be highlighted within the text. All occurences should be highlighted.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Show value of defines==
For embedded developing often defines are used for bit masks. So it would be helpful if the user puts the cursor over a define and CB will hover the value of the define.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Wrap Mode==
If a text is wrapped in several lines (wrap mode) and the cursor is between these lines, then the Home-key will put the cursor in beginning of the first line instead of the start of the current line. This behaviour should be changed.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

==Convert Tab to spaces and vice versa==
If you mark a text in the editor and select the context menu, then tabs will converted to spaces within the selection.--[[User:Mariocup|Mariocup]] 11:38, 13 March 2008 (CET)

= Project Management =
Setting Defines
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

== Assembler Options ==
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

== Checkbox for Prebuilt and Postbuilt Steps ==
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

== Environment per build target ==
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

== File Explorer in CB ==
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

== Block Select Mode ==
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

== Aspell ==
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

== Linker Settings ==
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

= Embedded =
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

== Extension Points for options ==
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

== Occlusion highlight ==
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

== Symbol-Browser ==
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

== Search Dialogue ==
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments

== Show Call Hierarchy ==
Show tree view of the called function and functions that were called before and after it.

== Debugger Console ==
Integrate a gdb Debugger Console in CodeBlocks.

== Hardware Breakpoint ==
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

== Interrupt and Resume Debugger ==
Add button for interrupting and resume in the Debugger.

== Section Browser ==
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different settings.

== Symbol View in Debugger ==
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

== Mixed Mode ==
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

== Tabbed View ==
The windows of breakpoint, variables etc. should dockable in a tabbed view.

== Multiple Watch Windows ==
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories".

== Write Access to Register, Memory ==
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

== Special Function Register ==
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

== Multiple Debugger Instances ==
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

== Memory Consumption ==
A bar/gauge view of the allocated memory in different output sections.

== Squirell Debug ==
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User:Mariocup

2008-03-13T22:53:19Z

Mariocup: Removing all content from page

User:Mariocup

2008-03-13T22:52:47Z

Mariocup: New page: Project Management: Setting Defines For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be do...

Project Management:
Setting Defines
For example if a source file contains different #ifdef constructs, sometimes the user wants to toggle setting or unsetting of a define. This could be done either with introducing a comment character in the compiler define dialogue or using a split view window, where one column could be for setting a define and a second column for unsetting a define. The status of a define could be move between the columns by an arrow.

Assembler Options:
If you select the properties->Advanced option of an assembler file and click "Use custom build command" then per default "$compiler $options $includes - c $file -o $object" should appear.

Checkbox for Prebuilt and Postbuilt Steps
If you are using different postbuilt steps e.g. conversion of executable to a hex-file and followed by a build steps for flash programming it would be desirable either to have a a comment character for disabling postbuilt steps or introducing checkbox for selecting different post built steps.

Environment per build target
E.g. you want to use different compiler version for two build targets. The compiler is parametrise in the toolchain executable as an environment variable GNUGCC that points to different MinGW compiler versions. This could be realised when configurations of environment variables could be assigned for each build target.

File Explorer in CB
The file explorer (dmoore) and its shell extension can be used for flexible tasks like integrating Subversion support with gsvn or TortoiseSVN, diffing files etc. It should be integrated in Codeblocks.

Block Select Mode
Currently CodeBlocks supports only the selection and copy in block mode (ALT) but cannot paste the content in this mode. This features is useful for changing the content of columns in an array.

Aspell
Integrate Aspell as spell checker as CodeBlocks may be used as text editor too.

Linker Settings:
If you link different libraries that contain cylic references, then the linker will issue an error. To solve the problem you can surround the library list by

--start-group <liste libs> --end-group

Could be nice to have a checkbox in the Linker settings that will provide this command.

Embedded:
Add new tabs in the project settings for setting a predefined list of assembler and linker options (like in the compiler tab).

Extension Points for options:
Add mechanism to lock inconsistent selection of compiler, assembler or linker options. E.g. if one march= is selected other march= should be disabled and issue a warning.

Occlusion highlight:
/index.php?topic=7768.msg58463;topicseen#new (Ceniza)

Symbol-Browser:
The scope of the search in the symbol browse should depend on the user selection Global Functions, Global Variables, Defines etc.

Search Dialogue:
Add filter for searching with: Class/Struct, Union, Enumeration, Typedef, Function, Method, Variable, Namespace, Comments

Show Call Hierarchy:
Show tree view of the called function and functions that were called before and after it.

Debugger Console:
Integrate a gdb Debugger Console in CodeBlocks.

Hardware Breakpoint:
For embedded programming it is required to add so called hardware breakpoints. To do that gdb settings set only-use-hw-breakpoints 1 are required. These breakpoint should have a different color. Additional it could be a nice feature to be able to disable and enable existing breakpoints.

Interrupt and Resume Debugger:
Add button for interrupting and resume in the Debugger.

Section Browser:
In the gdb console the command "i file" will display the names of the output sections with start and end address. This information could be displayed in a tree view and by selecting the name of the output section you can navigate between sections. This could be useful to set breakpoint in different settings.

Symbol View in Debugger:
In some debuggers the symbols of an object (e.g. including startup code) are extracted and displayed in the symbol view. To get a clear view this view should provide a search dialogue and a filter mechanism for display the symbols.

Mixed Mode:
Provide a context menu to get a mixed mode (source code and assembler output) in debug mode. This should be possible for alle files within a project. In this view the user can set breakpoints in the assembler lines.

The display in mixed mode can be achived with the use of the GDB/MI interface (see gdb Manual gdb/mi Command Syntax):
Since gdb 6.1 the debugger can perform mi command with the use of interperter-exec command.

interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"

The passing of --0 or --1 will provide information for mixed mode if it is parsed.

Tabbed View:
The windows of breakpoint, variables etc. should dockable in a tabbed view.

Multiple Watch Windows:
In complex application with many watches the windows becomes unclear, since that a search function in the watch window would be cool. In addition it is diserable to have multiple watch windows to group some variables in "categories".

Write Access to Register, Memory:
Sometimes it is necessary to modify controller registers of values in the memory, therefore the memory and register view should provide a feature modify he content.

Special Function Register:
Architectures like PowerPC or TriCore have tousands of Special Functions Registers, which are not convenient to display them in the debugger. A browse dialogue for special funcions registers would simplify life.

Multiple Debugger Instances:
In embedded applications it is necessary to debug different projects (AVR, PowerPC etc.) simultaneously. For this reason the debugger mustn't be stopped when switching between projects.

Memory Consumption:
A bar/gauge view of the allocated memory in different output sections.

Squirell Debug:
Squirell scripts provide a simple mechanism to add functionality to CodeBlocks. The possibility to debug these scripts in CodeBlocks would be nice.

User talk:Mariocup

2008-03-13T21:40:57Z

Mariocup: /* Scope for Search */

User talk:Mariocup

2008-03-13T21:40:41Z

Mariocup: /* Search Dialog */

User talk:Mariocup

2008-03-13T21:39:36Z

Mariocup:

User talk:Mariocup

2008-03-13T10:38:11Z

Mariocup: