AppCode Web Help

Customize Data Views

Debug tool window | Variables tab | context menu | Customize Data Views

Use this dialog to configure the debugger data view options. Note that the same settings can be alternatively configured on the Debugger page in the Preferences dialog.

Java tab

Item Description
Autoscroll to new local variables Automatically scroll to new variables that appear in the scope when stepping.
Auto tooltips for values Select or clear the check box to enable or disable showing tooltips for values.

A tooltip in this context means a pop-up that provides an alternative, sometimes more convenient presentation of values in the Variables pane.

To illustrate, let's assume that there is a statement like this in your code:

String s = "Hello, World! \n Hello, World!";

When this statement is executed in the debugger, you’ll see a line looking similar to this in the Variables pane:

s = {java.lang.String@62}"Hello, World! \n Hello, World!"

with the line break shown as \n.

If the Auto tooltips for values option is on and you click this line and then hold the mouse pointer on it, you’ll see a yellow area (the "tooltip") in which the value of s is shown as

Hello, World!
Hello, World!

with a real line break in place of \n.

If the option is off, to show or hide such a tooltip, you should press the Alt key.

Show In this section, select the check boxes to have the Debugger show the elements listed below:
  • Declared type
  • Synthetic fields
  • $val fields and local variables
  • Fully qualified names
  • Object id
  • Static fields
  • Static final fields
Array In this section, specify the options related to showing arrays in the Debugger.
Item Description
Array start/end index Define the range of array elements to be shown.
Show maximum <number> array elements Define the maximum number of array elements to be shown.

This and the previous setting depend on one another. For example, if the range is 0-100 and the maximum number of elements is 50, AppCode will show elements 0 to 25 and 75 to 99 omitting those in between.

Hide null array elements If selected, the null array elements are omitted.
Enable alternative view for Collection classes Present Collections and Maps in a more convenient form.
Enable toString() object view In this group you can select classes if you need them and their descendants to be presented as a result of the toString() method call while debugging:
Item Description
For all classes that override toString() method Show all classes as toString().
For classes from the list Define the list of classes to be shown as toString(), using the add_class, add_class_pattern and the delete buttons. Use the check boxes next to the class names to temporarily enable or disable particular filters.
add_class Click this button to add a class to the list using the Choose Class dialog.
add_class_pattern Click this button to add a custom class filter using the New Filter dialog. To define a filter, enter a string pattern e.g., *.Test, javax.swing.*, etc.
delete Click this button to remove a file or filter from the list.

Java Data Type Renderers tab

On this tab, you can create and customize rendering schemes for data presentation in the debugger Frame view.

If no rendering scheme is currently defined, start by clicking add.

Item Description
add Use this icon to add a new rendering scheme to the list.
delete Use this icon to remove the selected scheme from the list.
copy Use this icon to create a copy of the selected scheme.
arrowUparrowDown Use these icons to move the selected item one line up or down in the list.
Renderer name Edit or view name of the selected renderer.
Apply renderer to objects of type (fully-qualified name) Define the type of objects to be affected by the renderer. Type the fully qualified name of the object, or click the ellipsis button and choose the desired type from the list in the Renderer Reference Type dialog.
When rendering a node This option determines how an object is displayed in the debugger:
  • Use default renderer: Select this option to display the node in a default AppCode way.
  • Use following expression: Type in the java expression you want to use to identify an object. You can use object's properties, constants, and even string math as a part of your renderer.
When expanding a node Define how the children information is presented.

Normally, expanding a node in the debugger lists the object's member variables (using renderer appropriate for their object types). This option lets you override that behavior and select a single expression or a series of expressions to control the display. You may use this to limit the amount of information displayed or to be more precise in how the information is presented for example.

  • Use default renderer: information for the selected node children is presented in a default way.
  • Use expression: enter a Java expression to calculate information to be presented for a node.

    Test if a node can be expanded (optional): enter a Boolean expression. If it is true, the renderer displays expandable nodes for the defined objects. Otherwise, no nodes are displayed.

  • Use the list of expressions: create a list of separate expressions to be calculated and presented as node children. Use:

    add (⌘N) to create a new expression.

    delete (⌘⌦) to remove the selected expression from the list.

    arrowUp (⌃↑) to move the selected expression one line up in the list.

    arrowDown (⌃↓) to move the selected expression one line down in the list.

See Also

Last modified: 8 October 2014
comments powered by Disqus