Eclipse uses tip 3--to optimize debug code

1. Format:ctrl+shift+f

A) Set formatting style:

I. Open windows->preferences-"java-"code style-" Formatter, edit the format or create a new format as required

Ii.

2, member Sort:Source-"sort Members"

3, finishing import:source-"organize import

4. Code refactoring:

A) Open refactor->rename

b) Mobile Refactor->move

c) The anonymous class is changed to an external class:Convert Anonymous class to Nested

D

View Code

5. View display structure:ctrl+t

6. View Code fallback:ALT +←

7. View Code forward:ALT +→

8. View method Call: Select the method name, press ctrl+alt+h

9. Quick Positioning class:ctrl+shift+t

10. Quick positioning of the selected word:ctrl+k

11. Quick Position match:Ctrl+shift+p

12, Incremental Search:

A) Forward:ctrl+j

b) Reverse:ctrl+shift+j

13. Quick Jump switch:ctrl+l

14, quick comparison: Set windows-"preferences-"editors-"text editors-"quit diff, check"show Differences in overview ruler"

15. Open Bookmark:windows-"Show view->other-> find Bookmarks

16. Open:windows-"Show View->tasks

17. Conditional breakpoint:

A) Set breakpoints, right-click to select "Breakpoint Properties",

b) Set "Hitcount" or "Conditional", "hitcount" means that after this breakpoint several times, the breakpoint takes effect, " Conditional"indicates that the breakpoint takes effect when this condition is established.

Hit Count indicates that the breakpoint takes effect 5 times after the breakpoint, andconditional indicates that only i equals 5 , the breakpoint does not take effect.

18. Exception Breakpoint:

Eclipse uses tip 3--to optimize debug code