If you’ve worked with any Android code before, you’re sure to have used these useful little red circles many times to help locate a bug or simply to try and get a better understanding of your code. A breakpoint is an intentional place or pause in a program where you can suspend your program or data can be retrieved and logged.īreakpoints are the backbone of any good IDE and a powerful tool in a developer’s toolbox Android Studio is no different! 12.4 Best Practices for Energy Managementīreakpoints are used for debugging purposes in software development.12.3 Inspecting and Optimizing Energy Consumption.10.5 Identifying and Improving Memory Performance: Detecting Memory Leaks.Section II: The Android Profiler Section 2: 5 chapters Show chapters Hide chapters 8.5 Practical Example: A Simplified Work-Chain.8.1 Starting the Background Task Inspector.Locked Debugging WorkManager Jobs With Background Task Inspector.7.6 Exporting Data from the Database Inspector.6.6 Exporting a Layout Inspector Snapshot.6.5 Confirming Changes With the Layout Overlay.6.4 Condensing Layouts With ConstraintLayout.3.3 Filtering and Customizing the Logcat Window.Locked Logcat Navigation & Customization.2.6 Using Breakpoints to Log Information.2.2 Becoming Acquainted With the Debug Window.Locked Navigating Your Code With Breakpoints.Section I: Debugging Basics Section 1: 8 chapters Show chapters Hide chapters
0 kommentar(er)
