Settings menu - Configuring Easy Code
must have its
corresponding ".cfg" file (Fasm.cfg, Fasm64.cfg,
GoAsm.cfg, GoAsm64.cfg, etc.) in
EasyCode\Config folder. but when you download Easy
Code 2 there is no ".cfg" file. Instead there is a file
with extension ".ori" (ori-ginal) for each assembler
configuration, as a reference for you to have an idea of what
to configure. Those files contain, among other values, the
paths and command line options for each assembler, linker,
resource and library compilers, and for each project type.
Once again, all paths are referred to the root of drive C:\
for simplicity, but as said before they should be in any other drive
or path. You just have to take into account the paths where
you have the corresponding tools and set the right path for each
tool in the Paths
command line options, as we will see later on in
section. Once again, using the system drive C: IS NOT
recommended, specially on Window 8.1 and Windows 10, because
of the permissions restriction.
When Easy Code starts, it checks whether each "ori" file has its "cfg" equivalent file. If the "cfg" file already exists nothing happens, if not, it makes a copy of the "ori" file but with the "cfg" extension. Doing so makes "ori" files always remain unchanged and avoids ".cfg" files to be created more than once (overwritten). If you already ran Easy Code, you can see the ".cfg" files in the "EasyCode\Config" folder.
The Settings section is available through the Tools-->Settings menu and it displays the following window:
Several options allow you to customize the editor.
Autocomplete Procs, Macros and Structures
Context help for variables and constants
Context help for functions and macros
Context help for structures (not yet implemented)
Highlight API constants and structures
Convert tabs to spaces
Hide selected text
Show collapse buttons
Show line numbers
Show selection bar
Draw line after EndP / EndM / EndS
Draw vertical lines in tab positions
Tabulation size (in spaces):
REMARKS: The editor may scrolls slowly in old computers. If so, try to uncheck the Highlight API constants and structures option.
Here you can
(and how) the syntax for different keywords will be
Checking the Default
conversion option (recommended) means that compiler keywords
will be converted to the same syntax as they have in their
corresponding configuration file.
constants and structures
Checking the Convert
to API case option (recommended) will convert all API names
to their right syntax.
macros, structs and variable names
this option (recommended) will convert all mentioned
names to their right syntax.
Specifies whether keywords
will be highlighted or not.
whether Easy Code adds or removes blanks to beautify the
is the most important part of the whole settings, as it is
where all assembler configurations are properly set in order
to work fine and without errors.
The Configuration combo box selects the configuration to be inspected or modified. Once a configuration is selected, you can choose the text encoding in the Text encoding combo box. ANSI text is the default value (recommended) and does not affect to the code editor, which always works in Unicode mode, but you can choose any other encoding method if you like, ONLY IF it is supported by the corresponding compiler. Otherwise, errors will be fired when compiling the source code and the project will not be built.
On the other hand, there are ten groups of different colours where you can add or remove keywords (keywords coming by default are the ones supported by the compiler being configured) taking into account that keywords will be highlighted with the colour of the group they are included in. Of course you can change the colour of each group at your own.
Now you have to specify the right paths for the assembler you are configuring. If there is any project loaded please close it, then click on the Paths and command line options button and the following window will be shown:
REMARKS: It is highly recommended not to have any project loaded while setting the paths and command line options shown in the window above.
can see in the window above, all wrong paths are printed in
red colour (in that case all paths are red-coloured because
I have all these tools in drive G:). Now please enter the
right paths for the required files and remember that all
non-existing (wrong) paths will be printed in red colour.
To set the right paths is an essential step in order to be
able to build projects easily and without errors.
The essential paths (not optional) you have to set in order to build all project types, are those labeled as:
All other paths are optional.
Once you have entered all the required paths, you can click on the Options tab and the following window will be shown:
You can have a look if
you like at the commmand line options for the compiler,
linker and resource and library compilers, both Debug and
Release modes, but it is highly recommended NOT TO MODIFY
any command line option at this time.
Please save this configuration by clicking on the OK button. Now you may want to repeat the same steps for all other configurations, but it would be better trying to build the examples for the assembler you just have configured (recommended).
Here you can specify the path for:
Help Tab - Configuring other help files
In the Help
tab you can
define up to five other help files (for opcodes, FPU,
MMX, etc.). By double-clicking on a label (Help
#1, Help #2, etc.) you will be able to
change its text according to the related file to be
launched. The text for each label will be shown in
the corresponding item of the Help menu.
REMARKS: Each entry can specify the path to a help file, or a web address (URL). Both, file or URL will be printed in red colour if they are wrong. To determine whether a path conforms to a valid URL format or not, the PathIsURL API function is called.