| Summary: | TrayDialog closes the tray if the help button is pressed with a cheat sheet open | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Chris Goldthorpe <cgold> | ||||
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert, markus.kell.r, remy.suen | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | 3.7 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Chris Goldthorpe
Created attachment 190929 [details] Patch 0.1 The problem is that the TrayDialog creates a help button, but it doesn't really know if the tray contains help or something else. Here's a potential solution that would work without new APIs. It fixes comment 0, but it doesn't set the help button to 'pressed' state when the user opened help via F1 (and not via the help button). For the perfect solution, we'd have to add something like DialogTray#isHelpTray(), which would be false for cheat sheets but true for actual help. I think that Patch 0.1 is a perfectly good solution. I don't think that users who open the tray using F1 will expect that pressing the (?) will close the tray. (In reply to comment #2) > I think that Patch 0.1 is a perfectly good solution. Thanks, released to HEAD. Verified in I20110426-2000. |