• Page
• Discussion
• View source
• History

From Eclipsepedia

You do not have permission to do that, for the following reason:

You can view and copy the source of this page:

[[Comparison SWT / RWT|Back to RWTOverview]] RWT will have the same behavior for all basic controls as SWT does. Currently there exists an incomplete implementation that provides basic functionality. ===Class Label=== Currently implemented: * get/set text * get/set image : '''Note''': Just like in SWT, the label can only display a string or an image but not both at the same time. When both is set, the label displays the object that was set last. However, the behavior of the RWT label differs slightly from SWT in that that setting an image clears the text and vice versa. As a result, calling <code>getImage()</code> after setting a text using <code>setText()</code> returns <code>null</code> even though an image has been set previously. * alignment (<code>LEFT</code>, <code>CENTER</code>, <code>RIGHT</code>) * <code>SEPARATOR</code> style, both horizontal and vertical with the same styles as supported by SWT: <code>SHADOW_NONE</code>, <code>SHADOW_IN</code>, <code>SHADOW_OUT</code> ===Class Button=== Currently implemented: * the types <code>PUSH</code>, <code>CHECK</code>, <code>RADIO</code>, and <code>TOGGLE</code> * get/set text and image (image is only displayed on PUSH and TOGGLE buttons yet) * selection * alignment (<code>LEFT</code>, <code>CENTER</code>, <code>RIGHT</code>) * SelectionListener * Default button behavior (see [[11_Controls%2C_Composites%2C_Groups%2C_and_Shells#Class_Shell|Shell]]). Please note that the default button is not yet highlighted (e.g. with a thick border) as it should be. ===Class Text=== Currently implemented: * get/set text * <code>SINGLE</code>, <code>MULTI</code> and <code>PASSWORD</code> styles * <code>READ_ONLY</code> and the get/setEditable methods which control whether the content of a text widget can be altered once it is created. * A first implementation of the ModifyEvent exists which is by far not meant to be final. With this we would like to get insight on what timings etc. are useful in practice. Through the distributed nature of RWT the inner workings are different from SWT (also see [[1_Widget_Fundamentals#Events_and_Listeners.|Events and Listeners]]). The current implementation sends a Modify Event in two cases: ** when a keystroke event in the Text widget is detected, then, after a delay of 500 ms, the ModifyEvent is sent ** when the Text widget loses focus, a ModifyEvent is sent immediately * The <code>textLimit</code> property can be use to control the number of characters that may be entered * Methods to control the text selection are implemented (<code>setSelection</code>, <code>getSelection</code>, <code>getSelectionCount</code>, <code>getSelectionText</code>, <code>clearSelection</code>, <code>selectAll</code>) ===Class List=== Currently implemented: * all selection-related methods * handling of focused item * all item operations * control scroll behaviour similar to SWT via <code>H_SCROLL</code> and <code>V_SCROLL</code> style flags: scroll never, scroll horizontal only, scroll vertical only, automatically scroll when necessary * SelectionListener including <code>widgetDefaultSelected</code> ===Class Combo=== Currently Implemented: * all selection-related methods * all item operations * SelectionListener

Return to 7 Basic Controls.