Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> org >> eclipse >> swt >> [ widgets Javadoc ]

• org.eclipse.swt.widgets: Javadoc index of package org.eclipse.swt.widgets.


Package Samples:

• org.eclipse.swt.widgets

Classes:

• Shell: Instances of this class represent the "windows" which the desktop or "window manager" is managing. Instances that do not have a parent (that is, they are built using the constructor, which takes a Display as the argument) are described as top level shells. Instances that do have a parent are described as secondary or dialog shells. Instances are always displayed in one of the maximized, minimized or normal states: When an instance is marked as maximized , the window manager will typically resize it to fill the entire visible area of the display, and the instance is usually put in a state where ...
• Display: Instances of this class are responsible for managing the connection between SWT and the underlying operating system. Their most important function is to implement the SWT event loop in terms of the platform event model. They also provide various methods for accessing information about the operating system, and have overall control over the operating system resources which SWT allocates. Applications which are built with SWT will almost always require only a single display. In particular, some platforms which SWT supports will not allow more than one active display. In other words, some platforms ...
• Decorations: Instances of this class provide the appearance and behavior of Shells , but are not top level shells or dialogs. Class Shell shares a significant amount of code with this class, and is a subclass. IMPORTANT: This class was intended to be abstract and should never be referenced or instantiated. Instead, the class Shell should be used. Instances are always displayed in one of the maximized, minimized or normal states: When an instance is marked as maximized , the window manager will typically resize it to fill the entire visible area of the display, and the instance is usually put in a state where ...
• ScrollBar: Instances of this class are selectable user interface objects that represent a range of positive, numeric values. At any given moment, a given scroll bar will have a single selection that is considered to be its value, which is constrained to be within the range of values the scroll bar represents (that is, between its minimum and maximum values). Typically, scroll bars will be made up of five areas: an arrow button for decrementing the value a page decrement area for decrementing the value by a larger amount a thumb for modifying the value by mouse dragging a page increment area for incrementing ...
• Slider: Instances of this class are selectable user interface objects that represent a range of positive, numeric values. At any given moment, a given slider will have a single selection that is considered to be its value, which is constrained to be within the range of values the slider represents (that is, between its minimum and maximum values). Typically, sliders will be made up of five areas: an arrow button for decrementing the value a page decrement area for decrementing the value by a larger amount a thumb for modifying the value by mouse dragging a page increment area for incrementing the value ...
• Dialog: This class is the abstract superclass of the classes that represent the built in platform dialogs. A Dialog typically contains other widgets that are not accessible. A Dialog is not a Widget . This class can also be used as the abstract superclass for user-designed dialogs. Such dialogs usually consist of a Shell with child widgets. The basic template for a user-defined dialog typically looks something like this: public class MyDialog extends Dialog { Object result; public MyDialog (Shell parent, int style) { super (parent, style); } public MyDialog (Shell parent) { this (parent, 0); // your default ...
• Combo: Instances of this class are controls that allow the user to choose an item from a list of items, or optionally enter a new value by typing it into an editable text field. Often, Combo s are used in the same place where a single selection List widget could be used but space is limited. A Combo takes less space than a List widget and shows similar information. Note: Since Combo s can contain both a list and an editable text field, it is possible to confuse methods which access one versus the other (compare for example, clearSelection() and deselectAll() ). The API documentation is careful to indicate ...
• Listener: Implementers of Listener provide a simple handleEvent() method that is used internally by SWT to dispatch events. After creating an instance of a class that implements this interface it can be added to a widget using the addListener(int eventType, Listener handler) method and removed using the removeListener (int eventType, Listener handler) method. When the specified event occurs, handleEvent(...) will will be sent to the instance. Classes which implement this interface are described within SWT as providing the untyped listener API. Typically, widgets will also provide a higher-level typed listener ...
• Widget: This class is the abstract superclass of all user interface objects. Widgets are created, disposed and issue notification to listeners when events occur which affect them. Styles: (none) Events: Dispose IMPORTANT: This class is intended to be subclassed only within the SWT implementation. However, it has not been marked final to allow those outside of the SWT development team to implement patched versions of the class in order to get around specific limitations in advance of when those limitations can be addressed by the team. Any class built using subclassing to access the internals of this class ...
• IconBar: An icon bar like a ToolBar but can scroll and have more control of the appearance. The IconBar is actually a viewport on a Canvas where the icons located. And thus most operations (layout,key,mouse ... etc) are forwarded to the Canvas where interactions occurs. Default highlight is changing icon background color on enter instead of simulating a button. Also fix problem that ToolBar icons flash on enter/exit by custom Canvas with NO_BACKGROUND. Subclass can use setMouseEventHandler() and access to the layout parameters to install different highlight behaviour. Subclass can use setRenderer() to install ...
• Composite: Instances of this class are controls which are capable of containing other controls. Styles: NO_BACKGROUND, NO_FOCUS, NO_MERGE_PAINTS, NO_REDRAW_RESIZE, NO_RADIO_GROUP, EMBEDDED Events: (none) Note: The NO_BACKGROUND , NO_FOCUS , NO_MERGE_PAINTS , and NO_REDRAW_RESIZE styles are intended for use with Canvas . They can be used with Composite if you are drawing your own, but their behavior is undefined if they are used with subclasses of Composite other than Canvas . This class may be subclassed by custom control implementors who are building controls that are constructed from aggregates of other ...
• Table: Instances of this class implement a selectable user interface object that displays a list of images and strings and issue notificiation when selected. The item children that may be added to instances of this class must be of type TableItem . Note that although this class is a subclass of Composite , it does not make sense to add Control children to it, or set a layout on it. Styles: SINGLE, MULTI, CHECK, FULL_SELECTION, HIDE_SELECTION, VIRTUAL Events: Selection, DefaultSelection Note: Only one of the styles SINGLE, and MULTI may be specified. IMPORTANT: This class is not intended to be subclassed ...
• Tree: Instances of this class provide a selectable user interface object that displays a hierarchy of items and issue notificiation when an item in the hierarchy is selected. The item children that may be added to instances of this class must be of type TreeItem . Note that although this class is a subclass of Composite , it does not make sense to add Control children to it, or set a layout on it. Styles: SINGLE, MULTI, CHECK Events: Selection, DefaultSelection, Collapse, Expand Note: Only one of the styles SINGLE and MULTI may be specified. IMPORTANT: This class is not intended to be subclassed.
• TabFolder: Instances of this class implement the notebook user interface metaphor. It allows the user to select a notebook page from set of pages. The item children that may be added to instances of this class must be of type TabItem . Control children are created and then set into a tab item using TabItem#setControl . Note that although this class is a subclass of Composite , it does not make sense to set a layout on it. Styles: TOP, BOTTOM Events: Selection Note: Only one of the styles TOP and BOTTOM may be specified. IMPORTANT: This class is not intended to be subclassed.
• Label: Instances of this class represent a non-selectable user interface object that displays a string or image. When SEPARATOR is specified, displays a single vertical or horizontal line. Styles: SEPARATOR, HORIZONTAL, VERTICAL SHADOW_IN, SHADOW_OUT, SHADOW_NONE CENTER, LEFT, RIGHT, WRAP Events: (none) Note: Only one of SHADOW_IN, SHADOW_OUT and SHADOW_NONE may be specified. SHADOW_NONE is a HINT. Only one of HORIZONTAL and VERTICAL may be specified. Only one of CENTER, LEFT and RIGHT may be specified. IMPORTANT: This class is intended to be subclassed only within the SWT implementation.
• Button: Instances of this class represent a selectable user interface object that issues notification when pressed and released. Styles: ARROW, CHECK, PUSH, RADIO, TOGGLE, FLAT UP, DOWN, LEFT, RIGHT, CENTER Events: Selection Note: Only one of the styles ARROW, CHECK, PUSH, RADIO, and TOGGLE may be specified. Note: Only one of the styles LEFT, RIGHT, and CENTER may be specified. Note: Only one of the styles UP, DOWN, LEFT, and RIGHT may be specified when the ARROW style is specified. IMPORTANT: This class is intended to be subclassed only within the SWT implementation.
• ToolBar: Instances of this class support the layout of selectable tool bar items. The item children that may be added to instances of this class must be of type ToolItem . Note that although this class is a subclass of Composite , it does not make sense to add Control children to it, or set a layout on it. Styles: FLAT, WRAP, RIGHT, HORIZONTAL, VERTICAL, SHADOW_OUT Events: (none) Note: Only one of the styles HORIZONTAL and VERTICAL may be specified. IMPORTANT: This class is not intended to be subclassed.
• Tracker: Instances of this class implement rubber banding rectangles that are drawn onto a parent Composite or Display . These rectangles can be specified to respond to mouse and key events by either moving or resizing themselves accordingly. Trackers are typically used to represent window geometries in a lightweight manner. Styles: LEFT, RIGHT, UP, DOWN, RESIZE Events: Move, Resize Note: Rectangle move behavior is assumed unless RESIZE is specified. IMPORTANT: This class is not intended to be subclassed.
• MessageBox: Instances of this class are used used to inform or warn the user. Styles: ICON_ERROR, ICON_INFORMATION, ICON_QUESTION, ICON_WARNING, ICON_WORKING OK, OK | CANCEL YES | NO, YES | NO | CANCEL RETRY | CANCEL ABORT | RETRY | IGNORE Events: (none) Note: Only one of the styles ICON_ERROR, ICON_INFORMATION, ICON_QUESTION, ICON_WARNING and ICON_WORKING may be specified. IMPORTANT: This class is intended to be subclassed only within the SWT implementation.
• Synchronizer: Instances of this class provide synchronization support for displays. A default instance is created automatically for each display, and this instance is sufficient for almost all applications. IMPORTANT: Typical application code never needs to deal with this class. It is provided only to allow applications which require non-standard synchronization behavior to plug in the support they require. Subclasses which override the methods in this class must ensure that the superclass methods are invoked in their implementations
• Control: Control is the abstract superclass of all windowed user interface classes. Styles: BORDER LEFT_TO_RIGHT, RIGHT_TO_LEFT Events: FocusIn, FocusOut, Help, KeyDown, KeyUp, MouseDoubleClick, MouseDown, MouseEnter, MouseExit, MouseHover, MouseUp, MouseMove, Move, Paint, Resize, Traverse, DragDetect, MenuDetect Only one of LEFT_TO_RIGHT or RIGHT_TO_LEFT may be specified. IMPORTANT: This class is intended to be subclassed only within the SWT implementation.
• CoolBar: Instances of this class provide an area for dynamically positioning the items they contain. The item children that may be added to instances of this class must be of type CoolItem . Note that although this class is a subclass of Composite , it does not make sense to add Control children to it, or set a layout on it. Styles: FLAT Events: (none) IMPORTANT: This class is not intended to be subclassed.
• Group: Instances of this class provide an etched border with an optional title. Shadow styles are hints and may not be honoured by the platform. To create a group with the default shadow style for the platform, do not specify a shadow style. Styles: SHADOW_ETCHED_IN, SHADOW_ETCHED_OUT, SHADOW_IN, SHADOW_OUT, SHADOW_NONE Events: (none) Note: Only one of the above styles may be specified. IMPORTANT: This class is not intended to be subclassed.
• ProgressBar: Instances of the receiver represent is an unselectable user interface object that is used to display progress, typically in the form of a bar. Styles: SMOOTH, HORIZONTAL, VERTICAL, INDETERMINATE Events: (none) Note: Only one of the styles HORIZONTAL and VERTICAL may be specified. IMPORTANT: This class is intended to be subclassed only within the SWT implementation.
• Sash: Instances of the receiver represent a selectable user interface object that allows the user to drag a rubber banded outline of the sash within the parent control. Styles: HORIZONTAL, VERTICAL Events: Selection Note: Only one of the styles HORIZONTAL and VERTICAL may be specified. IMPORTANT: This class is intended to be subclassed only within the SWT implementation.

Home | Contact Us | Privacy Policy | Terms of Service