| Summary: | Most "Show/Hide" buttons are reversed | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> |
| Component: | Debug | Assignee: | Darin Wright <darin.eclipse> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Whiteboard: | |||
The debugger should look at how the outliner manages to properly initialize the state of the sort button. |
When the "Show/Hide Qualified Names" button is pushed-in, it indicates that qualified names are being shown. Clicking the button so that it appears pulled-out means that qualified names aren't being shown. This feels like the intuitive behavior. The button is pressed in when it's showing qualified names, just as the "sort" button in the outliner is pressed in when the view is sorting. Buttons elsewhere in the Java UI ("Show/Hide Static", "Show/Hide Final", etc.) are backwards. Pressing a button *in* means that the affected items disappear. Depressed buttons mean activation. When the play button on your tape player is pressed, it means the tape is playing, when the power button on your computer is pressed, it means your computer is on. When the button for showing static variables is pressed, it should mean that statics are "active" in the view.