*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->HP-UX 11i man pages              
Title
Content
Arch
Section
 
 XmDirectionMatch(3) -- A function that checks for a specified direction component
    XmDirectionMatch compares two XmDirection values. The function returns a Boolean value depending on whether or not the two input values "match." The simplest match is when d1 and d2 are identical. However, other matches are possible. XmDirectionMatch attempts to compare specified bits only; nonspecified bits automatically match. For example, suppose that d1 equals XmTOP_TO_BOTTOM_RIGHT_TO_LEFT. ...
 XmDirectionMatchPartial(3) -- A function that checks for a specified direction component
    XmDirectionMatchPartial compares d1 and d2 along the direction component specified by dmask. For example, if dmask equals XmVERTICAL_MASK, then the function will compare only the vertical components of d1 and d2. d1 Specifies an XmDirection value to check. d2 Specifies an XmDirection value to check. dmask Specifies the direction component along which d1 and d2 are to be checked. Appropriate values...
 XmDirectionToStringDirection(3) -- A function that converts an XmDirection value to an XmStringDirection value
    XmDirectionToStringDirection converts the specified XmDirection direction value to its equivalent XmStringDirection value. Basically, if the XmDirection value has a horizontal direction specification, that horizontal element is used; otherwise, the XmStringDirection value is interpreted as XmSTRING_DIRECTION_L_TO_R. This function provides backward compatibility with the XmStringDirection data type...
 XmDisplay(3) -- The Display widget class
    The XmDisplay object is used by the Motif widgets to store information that is specific to a display. It also allows the toolkit to access certain information on widget hierarchies that would otherwise be unavailable. Each client has one XmDisplay object for each display it accesses. An XmDisplay object is automatically created when the application creates the first shell on a display (usually acc...
 XmDragCancel(3) -- A Drag and Drop function that terminates a drag transaction
    XmDragCancel terminates a drag operation and cancels any pending actions of the specified DragContext. This routine can only be called by the initiator client. dragcontext Specifies the ID of the DragContext widget associated with the drag and drop transaction to be terminated For a complete definition of DragContext and its associated resources, see XmDragContext(3).
 XmDragContext(3) -- The DragContext widget class
    DragContexts are special widgets used in drag and drop transactions. A DragContext is implemented as a widget, but a client does not explicitly create a DragContext widget. Instead, a client initiates a drag and drop transaction by calling XmDragStart, and this routine initializes and returns a DragContext widget. There is a unique DragContext for each drag operation. The toolkit frees a DragConte...
 XmDragIcon(3) -- The DragIcon widget class
    A DragIcon is a component of the visual used to represent the source data in a drag and drop transaction. During a drag operation, a real or simulated X cursor provides drag-over visuals consisting of a static portion that represents the object being dragged, and dynamic cues that provide visual feedback during the drag operation. The visual is attained by blending together various XmDragIcons spe...
 XmDragStart(3) -- A Drag and Drop function that initiates a drag and drop transaction
    XmDragStart initiates a drag operation. This routine returns the DragContext widget that it initializes for the associated drag transaction. The toolkit is responsible for freeing the DragContext when the drag and drop transaction is complete. widget Specifies the ID of the smallest widget and/or gadget that encloses the source elements selected for a drag operation. event Specifies the XEvent tha...
 XmDrawingArea(3) -- The DrawingArea widget class
    DrawingArea is an empty widget that is easily adaptable to a variety of purposes. It does no drawing and defines no behavior except for invoking callbacks. Callbacks notify the application when graphics need to be drawn (exposure events or widget resize) and when the widget receives input from the keyboard or mouse. Applications are responsible for defining appearance and behavior as needed in res...
 XmDrawnButton(3) -- The DrawnButton widget class
    The DrawnButton widget consists of an empty widget window surrounded by a shadow border. It provides the application developer with a graphics area that can have PushButton input semantics. Callback types are defined for widget exposure and widget resize to allow the application to redraw or reposition its graphics. If the DrawnButton widget has a highlight and shadow thickness, the application sh...
 XmDropSite(3) -- The DropSite Registry
    A client registers a widget or gadget as a drop site using the XmDropSiteRegister function. In addition, this routine defines the behavior and capabilities of a drop site by specifying appropriate resources. For example, the XmNimportTargets and XmNnumImportTargets resources identify respectively the selection target types and number of types supported by a drop site. The visual animation effects ...
 XmDropSiteConfigureStackingOrder(3) -- A Drag and Drop function that reorders a stack of widgets that are registered drop sites
    XmDropSiteConfigureStackingOrder changes the stacking order of the drop site specified by widget. The stacking order controls the manner in which drag-under effects are clipped by overlapping siblings, regardless of whether they are active. The stack mode is relative either to the entire stack, or to another drop site within the stack. The stack order can be modified only if the drop sites are sib...
 XmDropSiteEndUpdate(3) -- A Drag and Drop function that facilitates processing updates to multiple drop sites
    XmDropSiteEndUpdate is used in conjunction with XmDropSiteStartUpdate to process updates to multiple drop sites within the same hierarchy. XmDropSiteStartUpdate and XmDropSiteEndUpdate signal the beginning and the end respectively of a series of calls to XmDropSiteUpdate. Calls to XmDropSiteStartUpdate and XmDropSiteEndUpdate can be recursively stacked. Using these routines optimizes the processin...
 XmDropSiteQueryStackingOrder(3) -- A Drag and Drop function that returns the parent, a list of children, and the number of children for a specifi
    XmDropSiteQueryStackingOrder obtains the parent, a list of children registered as drop sites, and the number of children registered as drop sites for a given widget. The children are listed in current stacking order, from bottom-most (first child) to the top-most (last child). This function allocates memory for the returned data that must be freed by calling XtFree. widget Specifies the widget ID....
 XmDropSiteRegister(3) -- A Drag and Drop function that identifies a drop site and assigns resources that specify its behavior
    XmDropSiteRegister identifies the specified widget or gadget as a drop site and sets resource values that define the drop site's behavior. The routine assigns default values to any resources that are not specified in the argument list. The toolkit generates a warning message if a drop site is registered with XmNdropSiteActivity set to XmDROP_SITE_ACTIVE and the XmNdropProc resource is NULL. If th...
<<  [Prev]  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  52  53  
54  55  56  57  58  59  60  61  62  63  64  65  66  67  68  69  70  71  72  73  [Next]  >>
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service