Skip to main content

Navigating Paused Code

While in debug mode , Android Studio pauses at any breakpoint that you have set . This is , as long as a breakpoint has been set on a reachable line of code (  a line of code that would be executed by system ) , Android Studio halts execution at that line until you tell it to continue.

When Android Studio hits , and pauses at , a breakpoint , the circle in the margin next to the corresponding line of code changes to circle with a check mark.


Once a breakpoint has been hit , the debug window opens at the bottom Android Studio , as show in Figure . The debug window contains many of the tools you use to navigate around your code.

Notice the navigation buttons located in the menu bar of the debug window . The most commonly used are Step Over and Step Into . Step Over advances you to the line of code that immediately follows the one at which you are currently paused . This means that if you are paused at a method call , and you press Step Over , Android Studio executes the method call without pausing and then pauses again when execution reached the next line. However , when if an exception happens in that method call and execution never reach the next line of code ? For these situations use Step Into.

Step Into follows execution wherever it leads in the code . Therefore , if you are paused at method call and click Step Into , Android Studio will shift the view to the method call and pause execution at the first line of code within that method. This allows you to then follow the execution of that method line-by-line before it returns to the calling block.

Comments

Popular posts from this blog

Creating Android Virtual Devices (AVDs)

The next step is to create an Android Virtual Device (AVD) you can use for testing your Android application. An AVD is an emulator instance that enables you to model an actual device. Each AVD consists of a hardware profile ; a mapping to a system image ; and emulated storage,such as a secure digital (SD) card.One important thing to remember about emulators is that they are not perfect. There are some applications , such as games (which are GPU heavy ) or application that use sensors such as the GPS or accelerometer. Theses types of application cannot be simulated with the same speed or consistency within an emulator as they can when running on an actual device. However , the emulator is good for doing some generalized testing of your applications. You can create as many AVDs as you want to test your applications with different configurations. This testing is important to confirm the behavior of you application when it is run on different devices with varying capabilities. Use ...

Hiding the Activity Title

You can also hide the title of an activity if desired ( Such as when you just want to display a status update to the user). To do so , use the requestWindowFeature() method and pass it the window .FEATURE_NO_TITLE constant, like This : import android.support.v7.app.AppCompatActivity; import android.os.Bundle; import android.view.Window; public class MainActivity extends AppCompatActivity{            @Override            protected void onCreate ( Bundle savedInstanceState )            {                         super.onCreate (savedInstanceState );                         setContentView (R.layout.activit...

Applying Styles and Themes to an Activity

By default , an activity is themed to the default Android theme. However , there been a push in recent year to adopt a new theme known as Material . The Material theme has a much more modern and clean look to it. There are two versions of the Material theme available to Android developers : Material Light and Material Dark , Either of these themes can be applied from the AndroidManifest.xml To apply one of the Material themes to an activity , simply modify the <Application> element in the AndroidManifest.xml file by changing the default android:theme attribute. (Please be sure to change all instances of "com.android" to whatever package name your project is using.) <?xml version="1.0" encoding="utf-8"?> <manifest xmls:android="http://schemas.android.com/apk/res/android"        xmlns:tools="http://schemas.android.com/tools"        package="com.android.activity101">        <application ...