Widget is the base class of all widgets. It provides the methods to attach and detach signals.

• This modules reexports everything a normal widget needs from GObject and Object.

TODO

• unimplemented methods that seem to be useful in user programs: widgetSizeRequest, widgetAddAccelerator, widgetRemoveAccelerator, widgetAcceleratorSignal, widgetIntersect, widgetGrabDefault, widgetGetPointer, widgetPath, widgetClassPath, getCompositeName, widgetSetCompositeName, widgetModifyStyle, widgetGetModifierStyle, widgetModifyFg, widgetModifyBG, widgetModifyText, widgetModifyBase, widgetModifyFont, widgetPango*, widgetSetAdjustments
• implement the following methods in GtkWindow object: widget_set_uposition, widget_set_usize
• implement the following methods in GtkDrawingArea object: widgetQueueDrawArea, widgetSetDoubleBufferd, widgetRegionIntersect

Allocation

• for Widget's size_allocate signal

Retrieve the current state of the widget.

• The state refers to different modes of user interaction, see StateType for more information.

Retrieve the current state of the widget.

• If a widget is turned insensitive, the previous state is stored in a specific location. This function retrieves this previous state.

Queue a show request.

• Flags a widget to be displayed. Any widget that isn't shown will not appear on the screen. If you want to show all the widgets in a container, it's easier to call widgetShowAll on the container, instead of individually showing the widgets. Note that you have to show the containers containing a widget, in addition to the widget itself, before it will appear onscreen. When a toplevel container is shown, it is immediately realized and mapped; other shown widgets are realized and mapped when their toplevel container is realized and mapped.

Queue a show event and wait for it to be executed.

• If the widget is an unmapped toplevel widget (i.e. a Window that has not yet been shown), enter the main loop and wait for the window to actually be mapped. Be careful; because the main loop is running, anything can happen during this function.

Queue a hide request.

• Reverses the effects of widgetShow, causing the widget to be hidden (make invisible to the user).

Destroy a widget.

• The widgetDestroy function is used to shutdown an object, i.e. a widget will be removed from the screen and unrealized. Resources will be freed when all references are released.

Prepare text for display.

• The Layout represents the rendered text. It can be shown on screen by calling drawLayout.
• The returned Layout shares the same font information (Context) as this widget. If this information changes, the Layout should change. The following code ensures that the displayed text always reflects the widget's settings:

 l <- widgetCreateLayout w "My Text."
 let update = do
                layoutContextChanged l
 		    <update the Drawables which show this layout>
 w `onDirectionChanged` update
 w `onStyleChanged` update

A Button was pressed.

• This widget is part of a button which was just pressed. The event passed to the user function is a Button event.

The widget will be destroyed.

• The widget received a destroy event from the window manager.

The widget is about to receive all events.

• It is possible to redirect all input events to one widget to force the user to use only this widget. Such a situation is initiated by addGrab.

The widget will be destroyed.

• This is the last signal this widget will receive.

The widget was asked to hide itself.

• This signal is emitted each time widgetHide is called. Use connectToUnmap when your application needs to be informed when the widget is actually removed from screen.

The toplevel window changed.

• When a subtree of widgets is removed or added from a tree with a toplevel window this signal is emitted. It is emitted on each widget in the detached or attached subtree.

Track mouse movements.

• If hint is False, a callback for every movement of the mouse is generated. To avoid a backlog of mouse messages, it is usually sufficient to sent hint to True, generating only one event. The application now has to state that it is ready for the next message by calling drawWindowGetPointer.

The input device became active.

• This event indicates that a pen of a graphics tablet or similar device is now touching the tablet.

The input device became inactive.

• The pen was removed from the graphics tablet's surface.

The mouse wheel has turned.

• The Event is always Scroll.

The widget was asked to show itself.

• This signal is emitted each time widgetShow is called. Use connectToMap when your application needs to be informed when the widget is actually shown.

Inform widget about the size it has.

• After querying a widget for the size it wants to have (through emitting the "sizeRequest" signal) a container will emit this signal to inform the widget about the real size it should occupy.

Query the widget for the size it likes to have.

• A parent container emits this signal to its child to query the needed height and width of the child. There is not guarantee that the widget will actually get this area.