View Code Explorer/de - Revision history

Admin: 1 revision

2013-02-15T19:06:18Z

1 revision

Admin: Created page with "= Action = Shows the Code Explorer Window Code explorer.png
2013-02-12T21:06:05Z

Created page with "= <span style="font-size: 14pt; font-weight: bold;">Action</span> = Shows the Code Explorer Window Code explorer.png <span class="..."

New page
== (COPIED FROM ENGLISH PAGE) === <span style="font-size: 14pt; font-weight: bold;">Action</span> =

Shows the Code Explorer Window

 

[[File:Code explorer.png|center|Code explorer.png]]

<span class="f_ImageCaption"> </span>

The code explorer shows code elements in a tree. By double clicking an element the cursor will be set to the matching code in the editor.

You can also drag an element into the editor window.

By clicking the right mouse a pop up menu will allow you to filter out constants and variables (registers) from the definition file.

The following code elements will be shown in the explorer:

- Aliases. These are the user [[ALIAS]].

- Assembler. This is for single line asm using <span style="font-weight: bold;">!</span>

- Assembler Block. This is for assembler blocks using $asm .. $end asm. If you add comment after $asm, it will be shown in the tree as well. Example : $asm ; Test

- Constants. Both user defined constants ([[CONST]]) and constants from the definition file are shown.

- Declarations. Subs and Functions are both shown. Each with their own color.

- Functions. These are the user function implementations.

- Labels. When labels are used in subs and functions, the sub/functions name is listed first.

- Macros. These are the user macro's created with [[MACRO]].

- Subs. These are the user sub implementations.

- Variables. These are the variables from the user code and definition file. Each shown with their own color. Locals are shown under a branch of the sub/function.

- CallStack. This is optional. Since it takes time to trace the call stack it is turned off by default. Use the pop up menu to activate it.

The call stack shows a tree of the calls you make to user subs and functions. And each sub/function also shows the user functions it calls.

 

When the Code Explorer has the focus, pressing CTRL+F will search in the code explorer and not in the editor.

 

Using the code explorer can slow down editing. When the code explorer is visible, after modifications of the code, the project is parsed in the same thread. When you hide/close the window, you will not notice this. On a modern PC you will probably not notice it either way. In version 2.0.7.6 the code explorer is considered a beta functionality. If an error occurs, contact support. By making the Code Explorer window invisible, the explorer is deactivated.

 

<br/><br/>{{Languages}}

[[Category:BASCOM IDE/de]]