IntelliJ IDEA 14.1.0 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 Settings dialog.

Java tab

Item Description
Autoscroll to new local variables Select this option to automatically scroll to new variables that appear in the scope when stepping.
Auto tooltips for values Select this option to enable automatic display of tooltips for values.

A tooltip in this context is a pop-up that provides an alternative, sometimes a 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 this option is disabled, you must press the Alt key to display a value.

Show In this section, select which elements you want the Debugger to display:
  • Declared type
  • Synthetic fields
  • $val fields and local variables
  • Fully qualified names
  • Object id
  • Static fields
  • Static final fields
Show hex value for primitives Select this option if you want numeric variables to be displayed in the hexadecimal format.
Hide null array elements Select this option if you want null array elements to be omitted.
Enable alternative view for Collection classes Select this option to display collections and maps in a more convenient format.
Enable toString() object view In this section, you can select classes if you need them and their descendants to be presented as a result of the toString() method call while debugging. Use the following controls:
  • For all classes that override toString() method: select this option to show all classes as toString().
  • For classes from the list: populate the list of classes to be shown as toString(), using theadd_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 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.
arrowUp arrowDown Use these icons to move the selected item one line up or down in the list.

Note that the order of items in the list determines which renderer is used in the case of ambiguity born of class inheritance.

Renderer name In this field, specify the name of a new renderer, or edit an existing renderer name.
Apply renderer to objects of type (fully-qualified name) In this field, specify the type of objects that will be represented with this renderer. Type a fully qualified object name, or click the Browse button browseButton 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 when nodes are collapsed:
  • Use default renderer: select this option to display the node in the default way.
  • Use following expression: enter the java expression you want to use to identify an object. You can use object properties, constants, and even a string math as part of your renderer.

    Note that you can use code completion (Ctrl+Space) when defining expressions.

    All method calls and member variable access are relative to the object you're rendering. Use this to refer to an instance to which the renderer applies.

When expanding a node This option determines how an object is displayed in the debugger when nodes are expanded:

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

  • Use default renderer: select this option to display the node children in the default way.
  • Use following expression: enter the Java expression you want to use to identify an object.

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

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

    add (Alt+Insert) to create a new expression.

    delete (Alt+Delete) to remove the selected expression from the list.

    arrowUp (Alt+Up) to move the selected expression one line up in the list.

    arrowDown (Alt+Down) to move the selected expression one line down in the list.

Note that you can use code completion (Ctrl+Space) when defining expressions.

See Also

Last modified: 24 March 2015
comments powered by Disqus