public interface IInformationControlExtension5
IInformationControl. Adds API
Important: Enriching this information control only works properly if
IInformationControl.isFocusControl() is implemented like this (
is the control's shell):
return fShell.getDisplay().getActiveShell() == fShellLikewise,
IInformationControl.addFocusListener(org.eclipse.swt.events.FocusListener)should install listeners for
SWT.Deactivateon the shell and forward events to the focus listeners. Clients are encouraged to subclass
AbstractInformationControl, which does this for free.
|Modifier and Type||Method and Description|
Computes the width- and height constraints of the information control in pixels, based on the given width and height in characters.
Tests whether the given control is this information control or a child of this information control.
Returns the rich information control creator for this information control.
boolean containsControl(Control control)
control- the control to test
trueiff the given control is this information control or a child of this information control
trueiff the information control is currently visible
Point computeSizeConstraints(int widthInChars, int heightInChars)
widthInChars- the width constraint in number of characters
heightInChars- the height constraint in number of characters
nullto use the subject control's font to calculate the size
The returned information control creator is used to create an enriched version of this
information control, e.g. when the mouse is moved into this control and it needs to be
or when it needs to be made sticky for other reasons.
The returned information control creator must create information controls
IInformationControlExtension2.setInput(Object) accepts all inputs that are
also supported by this information control.
Note that automatic enriching of this information control works only if it also implements
This method may be called frequently, so implementors should ensure it returns quickly, e.g. by caching the returned creator.
nullto disable enriching
Copyright (c) 2000, 2016 Eclipse Contributors and others. All rights reserved.Guidelines for using Eclipse APIs.