View Code Explorer - Revision history

Admin at 19:32, 17 January 2017

2017-01-17T19:32:02Z

Admin at 19:31, 17 January 2017

2017-01-17T19:31:53Z

Admin at 18:01, 15 June 2015

2015-06-15T18:01:43Z

Admin at 10:40, 4 February 2014

2014-02-04T10:40:58Z

Admin at 09:44, 24 August 2013

2013-08-24T09:44:57Z

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

Created page with "= Action = Shows the Code Explorer Window Code explorer.png Action =

Shows the Code Explorer Window

 

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

 

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 !

- 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.

 

 {{Languages}}

[[Category:BASCOM IDE]]

← Older revision		Revision as of 19:32, 17 January 2017
Line 136:		Line 136:

	Now by clicking the item you will go to the point in your code where the item is referenced.		Now by clicking the item you will go to the point in your code where the item is referenced.
−
−	~~= <br/> =~~

	= <span class="f_Header">Show References</span> =		= <span class="f_Header">Show References</span> =

← Older revision		Revision as of 19:31, 17 January 2017
Line 137:		Line 137:
	Now by clicking the item you will go to the point in your code where the item is referenced.		Now by clicking the item you will go to the point in your code where the item is referenced.

		+	= <br/> =

		+	= <span class="f_Header">Show References</span> =
		+
		+	This options shows a panel on the bottom of the code explorer tree. When you activate the tooltip keeping SHIFT pressed and hovering an item in the editor, the references panel will be updated with all references of that item. A single click on an item in this list will set the cursor in the IDE to referred item.
		+
		+
		+
		+	Consider this simple piece of code :
		+
		+	Dim S As Single
		+
		+	Input "s " , S
		+
		+	Print S
		+
		+
		+
		+	When pressing SHIFT and hovering the mouse over the variable S , the tooltip will be shown : [[File:Tooltip-s.png\|tooltip-s]]
		+
		+	The references list will be updated as well. The item in bold points to the definition, in this case the DIM S.
		+
		+	The following two items in the list point to the INPUT "s ", S and the Print S.
		+
		+
		+
		+	The panel can be shown or hidden using the right click menu from the explorer.

← Older revision		Revision as of 18:01, 15 June 2015
Line 139:		Line 139:


−	When the Code Explorer is visible it will provide a number of other features : Indent lines can be drawn for structures. And when pressing SHIFT and moving the variable over a variable or constant, you can get information in a tooltip. Indents can be enabled in the options.	+

@@ Line 137: / Line 137: @@
 Now by clicking the item you will go to the point in your code where the item is referenced.
 &nbsp;
 &nbsp;

@@ Line 14: / Line 14: @@
 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:
@@ Line 37: / Line 39: @@
 - 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.
+- CallStack. This is optional. Since it takes time to trace the call stack it is turned off by default. Use right mouse click and 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.
 &nbsp;
@@ Line 47: / Line 53: @@
 &nbsp;
-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.
+The code explorer works in a separate thread. It will be updated a few seconds after you have quit typing.
 &nbsp;
-<br/><br/>{{Languages}}
+{{Languages}}
 [[Category:BASCOM IDE]]