This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 193034 - [Forms] Section should also set the toggle tooltip
Summary: [Forms] Section should also set the toggle tooltip
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 4.4 M1   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 411405
  Show dependency tree
 
Reported: 2007-06-17 13:25 EDT by Philipp Kursawe CLA
Modified: 2013-08-22 08:55 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Kursawe CLA 2007-06-17 13:25:21 EDT
When calling setTooltip on a section, the section should also update the toogle's tooltip so that the user also sees the tooltip when he hovers over the toggle hyperlink field.

Are there any reasons against such behaviour?
Comment 1 Kevin McGuire CLA 2007-06-18 11:42:37 EDT
Moving to forms team
Comment 2 Adam Archer CLA 2008-06-13 17:48:50 EDT
I just tried calling setToolTipText on a Section and found that the tooltip shows when I hover the header, but not the title text or the toggle control. I'm not sure how useful it is to put a tooltip on the section (the title/description should be enough), but since the API is there we may as well make it work better.

We should add the same tooltip to both the title text and the toggle link.
Comment 3 Robin Stocker CLA 2013-05-26 08:03:16 EDT
Proposed fix for this:

https://git.eclipse.org/r/13157
Comment 4 Robin Stocker CLA 2013-05-30 09:41:18 EDT
Would it be possible to include this in 4.3.1? The fix is simple and I plan to add some tooltips to the sections of the Git Staging view (Unstaged/Staged Changes).
Comment 5 Paul Webster CLA 2013-05-30 09:45:54 EDT
Sure.

PW
Comment 7 Dani Megert CLA 2013-08-22 07:04:40 EDT
(In reply to comment #4)
> Would it be possible to include this in 4.3.1? The fix is simple and I plan
> to add some tooltips to the sections of the Git Staging view
> (Unstaged/Staged Changes).

FYI: Using tool tips on larger areas/forms is usually not a good thing (e.g. it's discouraged on the preference pages). If the info is really needed, it should always be visible and otherwise be put into the F1 help.
Comment 8 Robin Stocker CLA 2013-08-22 08:47:06 EDT
(In reply to comment #7)
> (In reply to comment #4)
> > Would it be possible to include this in 4.3.1? The fix is simple and I plan
> > to add some tooltips to the sections of the Git Staging view
> > (Unstaged/Staged Changes).
> 
> FYI: Using tool tips on larger areas/forms is usually not a good thing (e.g.
> it's discouraged on the preference pages). If the info is really needed, it
> should always be visible and otherwise be put into the F1 help.

I was thinking about adding something like "Drag to Staged Changes to stage for commit, drag to editor area to open" as tooltip on "Unstaged Changes". It should only be shown when hovering over the title text or the rest of the section header, so the area would not be bigger than, say, a checkbox label.

Would that be considered a bad thing? There's not enough space to always display it, and I don't know if anyone will press F1 there.
Comment 9 Dani Megert CLA 2013-08-22 08:55:48 EDT
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #4)
> > > Would it be possible to include this in 4.3.1? The fix is simple and I plan
> > > to add some tooltips to the sections of the Git Staging view
> > > (Unstaged/Staged Changes).
> > 
> > FYI: Using tool tips on larger areas/forms is usually not a good thing (e.g.
> > it's discouraged on the preference pages). If the info is really needed, it
> > should always be visible and otherwise be put into the F1 help.
> 
> I was thinking about adding something like "Drag to Staged Changes to stage
> for commit, drag to editor area to open" as tooltip on "Unstaged Changes".
> It should only be shown when hovering over the title text or the rest of the
> section header, so the area would not be bigger than, say, a checkbox label.
> 
> Would that be considered a bad thing?

I'd say so, especially because the hit area is quite big. Users would get the hover often without a way to get rid of it once they know about the feature.


>  I don't know if anyone will press F1 there.
Probably not, but I guess lots of people try DnD already without the hint. We usually but such info into our Tips & Tricks document.