Examining variables while debugging in Android Studio - android-studio

I'm looking for a way to examine the value of variables while debugging in Android Studio. In Xcode, you can type commands into the terminal window to execute code. For example: po user.name would print the user's name. There is a similar facility in the Chrome debugger. You could just type user.getFriends() and it would output the list of friends.
Does something like this exist in Android Studio? At the moment I'm limited to having to examine the variables in the Variables window which is slower and much less flexible because you can't print the value of functions.

When debugging an application, you can set a breakpoint and when that triggers, you can right click in the editor and select 'Evaluate Expression...' I believe this will give you close to what you are looking for.

Related

Is there a way to enable interactive search in properties window?

I just started to use Android Studio and wondering if there is a way to search interactively in property window.
I mean like Xcode does. (It's not a properties, though.)
Is there a plugin or configuration for the function like this?
Android Studio actually has a search tool for properties similar to the one in Xcode. But it's implemented in a very unusual and un-intuitive way. Which makes it hard to find.
In Android Studio version 1.5.1, you have to click either on the 'Properties' header or any property-name below the header, and then you need to start typing the property you want, even though there is no text-box or any other indication that your typing will produce any effect.
When you do this, then a text-box appears with the characters you've typed in. And Android Studio highlights all the properties that contain your character sequence. You can then look only at the highlighted properties to find the one you want.
There is no filter like in Xcode, but if you start typing property name the selection will jump to the first match and the rest of the matches will be highlighted.

Where is the warnings screen option in Android Studio?

I want to see warnings of my code in Android Studio, But i am unable to find the option to display warnings view. In case of eclipse we can see the warnings in the "Problems" view.
Can anyone suggest me, how to view warnings in android studio?
If, on the toolbar, you click Analyze -> Inspect Code; then in the window that pops up select how much of your project you want to inspect (I usually do Whole Project, but you might want to select a specific module), then click okay.
Android Studio will work for a bit, then the inspection window will pop up from the bottom with a list of results, subdivided by inspection.
Build -> Make Project (Ctrl + F9) gives what we can get equivalent of Eclipse's “Problems” view on Android Studio
you can use F2 to next problems, see more here: Navigating to Next/Previous Error
GO to View-->Tool Windows-->Messages to view the warnings
Even i searched all the settings in Android Studio, but couldn't find a separate window for it.
The warnings are actually visible to the right end of a particular line as a small yellow marker and clicking on that show the warnings in the status bar below. The colors of them can be editted in the inspection options.
Hope this helps you.
The closest thing Android Studio/IntelliJ has to the Problems view in Eclipse is to use the Problems section of the Project tool window. With that open, navigate down to any classes that appear there and open them in the editor. Once in the editor, you can use F2 to jump between errors in the open file.
Unfortunately, IntelliJ's Problems tool window shows classes with errors nested by folder/package, so you have to expand several levels and it takes up a lot of screen real estate to see even one error. It also doesn't list the errors individually, forcing you to first open the problematic file and then use F2 to navigate to each one. I also had the problem that errors in files that weren't open, didn't show up there.
[opening warning screen in android studio
Click the warning icon as marked in the image.
Warning screen will open.
][click to see image] here

Can you configure the Visual Studio Find Options?

Is it possible to get the VS 2012 find dialog to always use Current Document and reset case & whole-word when I press Ctrl+F? Currently it remembers my last options and I often forget to turn them off.
Also it sometimes switches to All open documents on its own which totally throws me off. I haven't yet figured out why or when this happens.
I've searched for registry keys and extensions but so far nothing useful has turned up.
It's not possible to get the dialog or the quick find UI to always choose a specific scope out of the box. During beta of VS 2012, this behavior was implemented where CTRL+F would always set the scope to Current Document and Ctrl+Shift+F would set the scope Entire Solution upon invocation of the commands. A lot of users were unhappy with this behavior, so it was reverted. There are no registry keys that you can set to alter this behavior.
Visual Studio always tries to reuse the last used scope. There are circumstances at which that scope is not available, and that'll cause the IDE to change the scope on you. Let's suppose you do a search in "Current Project", after that you close the entire solution and then invoke the dialog. The scope will have to change to something else.
You probably know about this, but Ctrl+F3 will search for the word that is under the caret and it'll always perform that search with the Whole Word option on in the current document. Perhaps that'll suit your needs.
I've published a Visual Studio "SmartFind" extension to fix this issue.
http://visualstudiogallery.msdn.microsoft.com/015611c4-b357-4672-8977-f3ec92f0b808

How to fix Visual Studio debugger watch window showing decompiled values

I have recently installed the RTM version of VS 2012, and when I run the debugger the watch window gives me what appears to be a decompiled vision of the local values. My initial thought was that I accidently hit the "Hexadecimal" display, but that is not the case. When I try to look at sub-properties off a given object, I get nothing, not even a representation if the object is null.
I won't know exactly what I may have set that is causing this, but VS 2010 did not do this, and the first day with VS2012RTM also didn't do this. I'm reasonably certain this is a setting I clicked, but for the life of me I can't figure out what it is.
Here are a couple screen shots of what the watch window looks like, and my debugging settings. As an aside, I have tried resetting my settings to factory, and turning IntelliTrace on and off.

No memory window in Visual Studio 2010

I have VS2010 Premium RTM version on Windows 7 Ultimate x64.
In the documentation they refer to the Memory 1-4 windows, supposedly under Debug->Windows->Memory.
I have "Enable address-level debugging" enabled in VS (Options->Debugging).
The problem is that I have no Memory menu item under Debug->Windows during debug of a c++ program.
Under Debug->Windows I have only:
Breakpoints
Parallel Tasks
Parallel Stacks
Watch ->
Locals
Call Stack
Threads
Have anyone else experienced this (and hopefully solved it)?
During the first run of VS after installation it asks you which "mode" it should run in, depending on your selection it shows or hides various menu items etc. Maybe you selected an option that hid those windows? This is described at this page.
I think you can use the information on this page to change those settings.
You might also be able to just run Devenv /ResetSettings to reset them, but not sure exactly what you'd end up with then...
Go to command Window and type in memory. It will show the Memory 1 watch window. I had to do that because I still can't find the debug command for it under customize even.
You can switch to expert mode by checking :
Tools > Settings > Expert Settings
Now you can show up Registers Window and much more other windows
The Memory window is available only if address-level debugging is enabled in the Options dialog box, Debugging node. The Memory window is not available for Script or SQL, which are languages that do not recognize the concept of memory.
or go here for other details:
http://msdn.microsoft.com/en-us/library/s3aw423e.aspx

Resources