The variable value (Ctrl+shift+i is not valid) in the Quick View breakpoint at the Android Studio debugging process?

When you're doing keymap to eclipse, in the debug process, we like to use Ctrl+shift+i to see the results of an operation or invocation in Eclipse, which is handy. But after keymap to eclipse, you will find that the shortcut key cannot be made. What is the reason why we exclude each:

1, whether the accelerator mapping failed,

2, the mapping is successful, you see the shortcut keys also found to be normal, then check whether the shortcut key conflicts.

3, how is the shortcut key conflict, that solves the shortcut key conflict, normally solves the conflict, the shortcut key is can use normally, but you will find that even if you solve the conflict, Ctrl+shift+i still can not use. What's the reason?

First, we take one step at a-

The first step: Find ctrl+shift+i corresponding function point name, why to find this, because Android Studio does not support shortcut key direct Search, in the previous article has also been analyzed, how to find it, please poke this:how Android studio modified shortcut keys . The name found here is inspect.

The second step: OK, find the corresponding shortcut key name, to see if the map is successful, the mapping is successful, you can see the inspect corresponding shortcut key name is Ctrl+shift+i.

The third step: since the mapping is not wrong, then see if there is a conflict, how to see if there is a conflict between shortcut keys, please poke this:Android stuido How to view shortcut key conflicts? you will find that the shortcut is in conflict with the quick definition, conflict, resolve the conflict, modify the current shortcut, or modify or remove the quick definition (you can choose to remove things if you feel that the conflicting function points are not commonly used).

Then you resolve the conflict, but this time you will find that it is still not available. Why, the reason is explained in detail in this article:how Android Studio looks at the resources or functions in which classes are referenced . Even though the reason for this article is 4, the shortcut key names are the same, but the functionality is different.

So how exactly do you look at operations or debug results in debug like Eclipse, there are three ways:

Method One: For a single variable, double-click the variable and you will see the value of the variable. But this approach is too restrictive.

Way two: This way in fact Eclipse also has, is also the same, select you want to view the east, right, pop-up dialog box, select the Box up options:

When selected, you can see the corresponding detections in the watches list. This can be either for a single variable or for a call or complex operation result.

Way three: This way is also today want to focus on, corresponding to the Ctrl+shift+i shortcut key way, in fact, in Android Studio also has the corresponding eclipse this shortcut key function, just not called inspect, concrete such as:

If you don't want to use the shortcut on this side, you can also change to ctrl+shift+i.

About debugging the related shortcut keys, you can go to this side to see, see, Run is all about the debug shortcut keys: