Community
Participate
Working Groups
3.3 and 3.4 builds If you trigger content assist in a manifest.mf file you get nice additional info for each entry on the right side. This window shows a wrong hint in the status line: "Press 'F2' for focus".
What's wrong with the status line text? Should it be removed?
The problem Daniel describes is that when you trigger contentassist to select a new header, you've got a popup where you can choose your header (Bundle-Category, Bundle-Classpath, etc). As soon as an entry in the list displayed in that popup is selected, a "subtooltip" is shown, and tells you that pressing F2 will give focus. But it don't. The best approach IMHO would be to keep the status line, and to forward the focus request to the second popup. My $0.02...
To me, the flyout tooltip in the PDE manifest editor (which we are talking about) looks quite different from the flyout tooltip in JDT. Maybe we should harmonize this for the sake of a more homogenous user experience. How about removing the "press F2" hint alltogether? I mean, what sense does it make to focus the tooltip? Does anyone need to copy text out of the tooltip window? Do we have any tooltip texts that exced the available space so one might want to scroll? I don't think so. Thus, I suggest removing the F2 hint.
Forgot to mention: the JDT tooltip flyout does not have an F2 hint.
>Thus, I suggest removing the F2 hint. Exactly. There will be some changes in the underlying code assist for 3.4 that will allow to move focus into the additional info but until then PDE should simply remove that F2 hint.
Is there an obvious way to do this? I browsed the code for a few minutes and couldn't find how to remove the F2 message.
Pass 'null' instead of EditorsUI.getTooltipAffordanceString() in org.eclipse.pde.internal.ui.editor.contentassist.TypeCompletionProposal.getInformationControlCreator() HTH Dani
Created attachment 96170 [details] Patch that removes the F2 message The patch removes the F2 message by passing in "null", as suggested by Dani. Sorry for not taking care of this for so long... In fact, a patch had been lurking in my workspace for quite some time - however, I had passed in the empy string.
Created attachment 96171 [details] mylyn/context/zip
available in HEAD>20090729 ; thanks :)
