A rendition is simply a collection of all the information necessary to render text. Each segment of text on display (segments can be as long or as short as circumstances warrant) is tagged with a "tag," indicating which of a list of possible renditions is to be used for that text. That list, containing one or more renditions, is called a render table and is described in Section 7.1.2.

---

Note: Some of the Motif widgets used for text input do not use renditions. This means that a user can change the fonts used in these widgets but not the color or tabs or other rendition properties. In these cases, a font list structure is available that is analogous to the render table.

---

A rendition is neither a widget nor a gadget. However, the style used to specify resources for widgets and gadgets is a simple and familiar way to set data values, and it has been implemented for renditions and render tables as well. To change the foreground color for a rendition, for example, a user must set a "resource" called renditionForeground for that rendition, in the same way a user would change the color resource for some widget.

A rendition can have any of the following resources:

Any of these resources (except tag, tabList, and fontType) can have the value AS_IS, which specifies that the resource take its default value, which is usually inherited from the parent widget. If a tabList resource is missing, the widget will usually have default tab stops set. Note that the application foreground and background use unspecified pixel colors.

*renderTable.rend1.fontName:  -Adobe-Courier-*-*-*--12-120-100-100-*-*
*renderTable.rend1.fontType:  FONT_IS_FONT

*renderTable.rend1.fontName:  -JIS-Fixed-Medium-R-Normal--26-180-100-100-C-240,\
                              -JIS-Fixed-Medium-R-Normal--26-180-100-100-C-120,\
                              -Adobe-Courier-Bold-R-Normal--24-240-100-100-M-100
*renderTable.rend1.fontType:  FONT_IS_FONTSET

resource_spec: tab [, tab ]*

tab = [ + ]  float [ units ]

*List.renderTable.rend1.tabList: 1in, +1in

Render tables are specified in resource files with the following syntax:

resource_spec: [ tag [, tag ]* ]

where tag is some string suitable to be the name of a rendition. This line creates an initial render table containing one more rendition than the number of tags specified. The renditions are attached to the specified tags, with the untagged rendition going with the tag _MOTIF_DEFAULT_LOCALE. If no tags are specified, then a render table will be created that contains only a rendition with a tag of _MOTIF_DEFAULT_LOCALE.

Specific values for specific rendition resources are specified using the following syntax:

resource_spec [*|.] rendition[*|.] resource_name:value

where resource_spec specifies the render table, rendition is a tag (or is omitted), resource_name is the name of a particular resource, and value is the specification of the value to be set.

Any resource line that consists of just a resource name or class component with no rendition component will be assumed to specify resource values for a rendition with a tag of _MOTIF_DEFAULT_LOCALE.

For example, the following:

*List.renderTable: green, variable
*List.renderTable.green.renditionForeground: Green
*List.renderTable.green.fontName: AS_IS
*List.renderTable.variable.underlineType: SINGLE_LINE
*List.renderTable.variable.renditionForeground: Red
*List.renderTable.variable.fontName: variable
*List.renderTable.variable.fontType: FONT_IS_FONT
*List.renderTable.variable.underlineType: DOUBLE_LINE
*List.renderTable.renditionForegound: black
*List.renderTable.fontName: fixed
*List.renderTable.fontType: FONT_IS_FONT
*List.renderTable.variable.underlineType: NO_LINE
*List.renderTable*tabList: 1in, +1.5in, +3in

would set the renderTable resource of List to a render table consisting of three renditions tagged with _MOTIF_DEFAULT_LOCALE, green, and variable with values for resources set as described in the resource specifications. Note that the tabList resource will be shared by all three renditions.

There are two types of protocols that can be in effect during a drag and drop transaction: preregister and dynamic. Generally, the preregister protocol is more efficient, uses fewer system resources, and provides more attractive drag-over effects. The dynamic protocol provides more attractive and powerful drag-under effects. Motif applications based on Release 2.0 should support both protocols.

You can specify which protocol you want in effect for drag sources and drop sites with the following resources. However, due to other constraints, the system may not be able to use the protocol you requested.

These resources can have the following values (the letters in parentheses are used as abbreviations for the values in Table 7-1):

The following example specifies that an application named myapp uses the dynamic protocol both when it is a drag source and when it is a drag receiver.

myapp*dragInitiatorProtocolStyle:    DRAG_DYNAMIC
myapp*dragReceiverProtocolStyle:     DRAG_DYNAMIC

It may take some experimentation to find the best values for these resources for the applications you are running on your particular system configuration. Here are some guidelines:

Table 7-1 shows how a conflict between the source and destination protocols is resolved.

The following resources allow you to provide your own default graphics for drag-over situations. These graphics are used only if an application has not specified its own graphics.

You can specify a pixmap and a mask to use for any part of the drag icon by using the following resources:

Provide the name of the icon you are creating in addition to the resource. For instance, to specify a pixmap and mask for the invalid state icon, use the following resource specifications:

*defaultInvalidCursorIcon.pixmap:     mypixmap
*defaultInvalidCursorIcon.mask:       mypixmask

You can specify which of the three parts of the drag icon you want to see with the blendModel resource. This resource can take the following values:

You can specify how you want the source, state, and operation icon to be located with respect to each other with the attachment resource. This resource is used for state and operation icons and ignored for the source icon. The attachment point for these icons is the lower right corner. Use the attachment style that gets the icons closest to the position you want, then use an offset for final adjustment.

The attachment resource can take the following values:

If you specify the attachment resource in a resource file, include the name of the icon to which it refers. For instance, to attach the valid state icon at the upper left corner of the source icon, use the following specification:

*defaultValidCursorIcon.attachment:  ATTACH_NORTH_NORTHWEST

You can move the state and operation icons from the basic attachment point by using offsets. Select the attachment point nearest to the location you want, then make final adjustments with the the following offset resources:

You can specify how you want the drop site's drag-under visual effects to appear with the animationStyle resource. This resource can take the following values:

Use the animationPixmap, animationMask, and animationPixmapDepth resources to specify the pixmap to use if the animation style is DRAG_UNDER_PIXMAP.

Use the following resources to set colors for the drag icon:

For example, the following specifications set the drag icon to blue when it is over a valid drop site, to red when it is over an invalid drop site, and to green when it is not over a drop site.

*validCursorForeground:     Blue
*invalidCursorForeground:   Red
*noneCursorForeground:      Green