Browsing English (United Kingdom) translation

123.

!Define node data for a wxTreeCtrl.
!Note that all lines that start with a "!" are comment lines and ignored.
!Also, all empty lines are ignored (a line of spaces is not an empty line).
!
!The node data is organized similar to a Tabbed Hierarchical Values (THV) file,
!such that each line of text represents one label for a single tree node.
!The number of leading TAB characters indicate the indentation level of the
!tree node.
!
!Space (or blank) characters are not used the same as TAB characters; if your
!editor substitutes spaces for TABs, use the "TAB Char" attribute to change
!the character used to indicate the tree node level.
!
!Following is a sample tree data definition:

First level, no tabs[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column
[tab]Second level, 1 tab[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column
[tab][tab]Third level, 2 tabs[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column
First level again, no tabs[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column
[tab]Second level again, 1 tab[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column
[tab]Another second level, 1 tab[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column
[tab][tab]Third level again, 2 tabs[tab]Second Column[tab]Third Column[tab]Fourth Column[tab]Fifth Column

135.

"One True Brace Style"uses linux braces and adds braces to unbraced one line conditional statements.
Opening braces are broken from namespaces, classes, and function definitions.The braces are attached to everything else,
including arrays, structs, enums, and statements within a function.
In the example, braces have been added to the "return 0;" statement.
The option --add-one-line-braces can also be used with this style.

881.

AVR64DA48

985.

Add different command line macros for different
extensions. This effectively adds support for non C/C++
files.
In the generated files box, add macros for any files that
will be generated when the command runs. These are
files that will further need to be compiled by the build
system.
Currently, only the $file* macros are allowed to appear
in the generated files box.

See docs for more info.

1336.

Auto increments the version and build number of your application every time
a change has been made and stores it in version.h with easy to use variable declarations.
Also have a feature for committing changes a la SVN style, a version scheme editor and a change log generator.

Example:

#include "version.h"
printf("v%d.%d.%d.%d",MAJOR,MINOR,BUILD,REVISION); //C example
string version = AutoVersion::FULLVERSION_STRING; //C++ example

Declarations available in the AutoVersion namespace on C++ and global on C:

1) Date Version Types
[tab] static const char DATE[]
[tab] static const char MONTH[]
[tab] static const char YEAR[]
[tab] static const double UBUNTU_VERSION_STYLE

2) Software Status
[tab] static const char STATUS[]
[tab] static const char STATUS_SHORT[]

3) Standard Version Type
[tab] static const long MAJOR
[tab] static const long MINOR
[tab] static const long BUILD
[tab] static const long REVISION

4) Miscellaneous Version Types
[tab] static const long BUILDS_COUNT
[tab] #define RC_FILEVERSION
[tab] #define RC_FILEVERSION_STRING
[tab] static const char FULLVERSION_STRING[]

5) SVN Version
[tab] static const char SVN_REVISION[]
[tab] static const char SVN_DATE[]

1350.

Auto-completes the word under the caret (nothing to do with code-completion plugins)

1368.

Automatic source paths...

1369.

Automatic versioning

1372.

Automatically adds missing includes and/or forward declarations to C++ source files within a single project or all projects within a workspace.

1376.

Automatically lay-out the window. If disabled, you must call Layout(), Fit() or SetSizeHints() in your own code as desired.