Bug 157668 - [UX][Help] Gray out help button when no help
Summary: [UX][Help] Gray out help button when no help
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-18 14:33 EDT by Tim Casperson CLA
Modified: 2019-09-06 16:05 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Casperson CLA 2006-09-18 14:33:18 EDT
If dynamic help is not available for a certain box that you have the focus on, the help button should be grayed-out instead of confusing the user by not doing anything when you click on the help button.
Comment 1 Curtis d'Entremont CLA 2006-09-19 10:10:29 EDT
Not sure if we want to do it this way or not - context-sensitive help isn't the only thing useful when you click the help button. You can also see the table of contents, search, and browse the keyword index.
Comment 2 Tim Casperson CLA 2006-09-19 13:35:18 EDT
Perhaps just the help button for Dynamic Help should be grayed-out and not the entire help feature such as table of contents, search, and browse?  The user can still have access to those features but just not through the Dynamic Help button.
Comment 3 Curtis d'Entremont CLA 2006-09-19 14:00:34 EDT
That's what I was referring to actually.. the help tray that appears inside the dialog. If the user is at page 7 of 8 of a long and complicated wizard, they would need to completely cancel out (and later start over) in order to get to Help -> Help Contents, however with the help button they could keep the wizard up while browsing.
Comment 4 Dani Megert CLA 2010-11-25 03:35:48 EST
This is in TrayDialog.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:05:48 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.