| Previous | Contents | Index |
Controls whether the user can select a particular entry.
void DXmSvnSetEntrySensitivity(widget, entry, sens)
Widget widget;
int entry;
Boolean sens;
|
widget
The identifier (widget ID) of the SVN widget.entry
An integer that represents the number of the entry whose sensitivity will be set or changed.sens
A Boolean value that, when True, means the entry is sensitive (the user can select it). If the value is False, the SVN widget will dim the display of the entry to indicate that the entry is not sensitive (the user cannot select it).
The DXmSvnSetEntrySensitivity routine changes the sensitivity of an entry ("sensitivity" means whether the SVN widget will allow the user to select a particular entry). When using this routine, note the following:
- Make the call in your application between calls to DXmSvnDisableDisplay and DXmSvnEnableDisplay.
- If the newly specified sensitivity is the same as the current sensitivity, the call is ignored.
- If the newly specified sensitivity for the entry is different from the current sensitivity, that entry is redisplayed if necessary.
- If an entry is being changed to no longer be sensitive (the user cannot select the entry) and that entry is currently selected, the entry will be cleared (canceled) and then redisplayed.
Assigns an entry tag to a specified entry.
void DXmSvnSetEntryTag(widget, entry, tag)
Widget widget;
int entry;
unsigned int tag;
|
widget
The identifier (widget ID) of the SVN widget.entry
An integer that represents the number of the entry for which information will be set or changed.tag
A value that the application will associate with this entry. This value is returned in all callbacks that set the entry_number field in the DXmSvnCallback structure.
The DXmSvnSetEntryTag routine assigns an entry tag to a specified entry, enabling an application to respond to a DXmSvnNgetEntryCallback callback requesting information about that entry. The function of this routine is similar to the DXmSvnSetEntry routine but is more limited in scope, requiring only a subset of the information you would specify for the DXmSvnSetEntry routine.See the DXmSvnSetEntry and DXmCreateSvn routines for related information.
Sets the position of the tree in tree display mode.
void DXmSvnSetTreePosition(widget, x, y)
Widget widget;
int x;
int y;
|
widget
The identifier (widget ID) of the SVN widget.x
An integer that represents the x position for the tree. This value is obtained by a previous call to the DXmSvnGetTreePosition routine.y
An integer that represents the y position for tree. This value is obtained by a previous call to the DXmSvnGetTreePosition routine.
The DXmSvnSetTreePosition routine enables applications to set the exact position of the display from previously stored coordinates. It is valid to call this routine only when the DXmSvnNdisplayMode resource is set to DXmSvnKdisplayTree. (The DXmSvnGetTreePosition routine retrieves the x- and y-coordinates from the SVN widget.)Note that if the application does not currently have the exact same characteristics (for example, the same mode, fonts, or size and number of entries) as when the DXmSvnGetPosition routine was last called, calling the DXmSvnSetTreePosition routine may generate an incorrect display.
Make this call in your application between calls to DXmSvnDisableDisplay and DXmSvnEnableDisplay.
Specifies that the SVN widget use highlight graphics when showing highlighted entries.
void DXmSvnShowHighlighting(widget)
Widget widget;
|
widget
The identifier (widget ID) of the SVN widget.
The DXmSvnShowHighlighting routine shows all highlighting by displaying a box (drawn with dashes) around an entry. Make this call in your application between calls to DXmSvnDisableDisplay and DXmSvnEnableDisplay.
Specifies that the SVN widget use selection graphics when displaying selected entries.
void DXmSvnShowSelections(widget)
Widget widget;
|
widget
The identifier (widget ID) of the SVN widget.
The DXmSvnShowSelections routine allows the SVN widget to use reverse video selection graphics when displaying selected entries. Make this call in your application between calls to DXmSvnDisableDisplay and DXmSvnEnableDisplay.
Ensures that all entries are valid.
void DXmSvnValidateAll(widget)
Widget widget;
|
widget
The identifier (widget ID) of the SVN widget.
The DXmSvnValidateAll routine examines all entries to ensure that each is valid. If other entries are added while a particular entry is being validated, the routine validates those new entries as well. (The routine calls DXmSvnNgetEntryCallback to obtain entries from the application.) This routine will not complete its operation until all entries are valid. Make this call in your application between calls to DXmSvnDisableDisplay and DXmSvnEnableDisplay.
This chapter explains how to use the extensions that Digital has added to the Motif User Interface Language (UIL). Specifically, it explains how to use nested compound strings, the new command line qualifiers in the UIL compiler, and the Widget Meta Language (WML) binary databases.
In addition, Appendix A documents the UIL built-in tables (which
include the additional routines provided by Digital) that you can use
to check whether your UIL specification is consistent with the Motif
Toolkit. This checking operation occurs during compilation.
3.1 Nested Compound Strings
A nested compound string allows you to nest a given compound string within another relative to the direction in which the string will be displayed. Use the NESTED_COMPOUND_STRING function when one compound string segment needs to be read right-to-left and another needs to be read left to right.
The result of the NESTED_COMPOUND_STRING function is a compound string containing a nested direction. The NESTED_COMPOUND_STRING has one of the following as its value:
The NESTED_COMPOUND_STRING function has the following syntax:
|
NESTED_COMPOUND_STRING(nested_string_expression ...) |
Where:
nested_string_expression :==
{nested_string_expression nested_string_expression ... (1)
|RTOL (nested_string_expression) (2)
|LTOR (nested_string_expression) (3)
|string_expression [SEPARATE=Boolean_expression]}; (4)
|
The compiler evaluates each string expression to see if it is one of the previously described four types, and then concatenates them all into one compound string with nested directional settings.
The following example shows UIL code for a nested compound string:
(RTOL ("Hello"
LTOR ("123", separate=TRUE)
"World"
))
|
123 olleH
dlroW
|
The UIL compiler uses the OSF/Motif Release 1.2 and DXm widgets by
default. However, you may use other versions or other widgets by using
different compiler command options. The following sections describe how
to use the UIL compiler on OpenVMS, UNIX, and Windows NT operating
systems.
3.2.1 UIL Compiler Command Qualifiers on OpenVMS Systems
Table 3-1 lists the qualifiers for the UIL compiler on OpenVMS systems.
| Qualifier | Default | Description |
|---|---|---|
| /MOTIF | /MOTIF | Uses the OSF/Motif and Digital extended widget database. |
| /LOCALE | no value | Instructs the compiler to use the current locale when creating localized compound strings. (See the OSF/Motif Programmer's Guide for a description of the UIL -s flag.) |
| /WIDGET_META_DESCRIPTION=filespec |
Selects the Widget Meta Description (WMD) file to be used when
processing the UIL source. UIL comes with two WMD files: a standard
OSF/Motif widget set, and a Digital extended widget set. To use the
standard OSF/Motif widget set, supply the following file specification
with this qualifier:
DECW$SYSTEM_DEFAULTS: DECW$UIL_OSF_MOTIF_1_1.WMD
|
|
|
If you want to use the Digital extended widget set, use this qualifier
with the following file specification:
DECW$SYSTEM_DEFAULTS: DECW$UIL_DXM_MOTIF.WMD
(Ask your system manager if there are additional WMD files that you can use.) |
||
| /[NO]LIST |
/NOLIST for interactive mode
/LIST for batch mode |
Directs the compiler to produce a listing file. The listing file goes in the current default directory and has the same name as the input file but with a .LIS file extension. If you include a file specification with the /LIST qualifier, the compiler uses that specification to name the listing file. |
| /[NO]MACHINE_CODE | /MACHINE_CODE | Functions like the /MACHINE_CODE (or equivalent) qualifier available for most high-level language compilers. If you specify both /LIS and /MACHINE_CODE on the UIL command line, the compiler places in the listing file a description of the records that it wrote to the UID file. This is analogous to a compiler placing the machine code it generates for a high-level language in the listing. The primary purpose of this listing is to isolate errors in the UIL compiler. |
| /[NO]OUTPUT | /OUTPUT |
Directs the compiler to produce a User Interface Definition (UID) file.
By default, /OUTPUT create a UID file in the current default directory
with the same name as the input file, but with the UID extension. If
you include a file specification with the /OUTPUT qualifier, the
compiler uses that specification to name the UID file.
The compiler does not produce a UID file when you use the /NOOUTPUT qualifier or when the compiler issues any diagnostics categorized as error or severe. You can use the /NOOUTPUT qualifier when you want to verify only that your UIL module is syntactically correct. |
| /[NO]WARNINGS | /WARNINGS | Directs the UIL compiler to suppress warning or informational messages or both. |
On UNIX and Windows NT operating systems, you use the following command format to invoke the OSF/Motif UIL compiler:
|
uil [-flags] filename |
Table 3-2 lists the uil command flags.
| Flag | Default | Description |
|---|---|---|
| -s | Instructs the compiler to use the current locale when creating localized compound strings. | |
| -wmd filename |
Selects the Widget Meta Description (WMD) file to be used when
processing the UIL source. UIL comes with two WMD files: a standard
OSF/Motif widget set and a Digital extended widget set. If you want to
use the standard OSF/Motif widget set, use the following file name with
the -wmd flag. The location of this file varies.
motif.wmd |
|
If you want to use the Digital extended widget set, you can use the
following file with the -wmd flag. The location of this file varies.
dxm-motif.wmd (Ask your system administrator if there are additional WMD files that you can use.) |
||
| -o filename | a.uid |
Directs the compiler to produce a User Interface Definition (UID) file.
By default, UIL creates a UID file with the name a.uid.
No UID file is produced if the compiler issues any diagnostics categorized as error or severe. |
| -v filename | No listing is generated | Directs the compiler to produce a listing file. If the -v flag is not present, the compiler does not generate a listing. |
| -m | No machine code is listed | Directs the compiler to place in the listing file a description of the records that it added to the UID file. This feature helps you to isolate errors. |
| -w | Warning messages are generated | Directs the compiler to suppress all warning and informational messages. Only error messages and severe messages are generated. |
| -I[ pathname] | /usr/include |
If you specify the -I flag followed by a full pathname, the compiler
searches for include files whose names do not begin with a slash (/) in
the following order:
If you specify -I alone, the compiler searches only the directory in which the main file is located; it does not search for include files in the standard directory (/usr/include). |
The version of Motif supplied by Digital supports the Widget Meta Language (WML) in a binary form called Widget Meta Description (WMD). WML generates a WMD file describing widgets and other attributes for use with the UIL compiler. Digital has included two WML source files on each operating system. You can copy these files to your own subdirectory and modify them so that you can refer to your own widgets by name without making them user-defined.
The following sections describe WML support provided on OpenVMS, UNIX,
and Windows NT operating systems. For additional information about the
WML, see the OSF/Motif Programmer's Guide.
3.3.1 WML Files on OpenVMS Systems
Digital includes the following files to support WML databases on OpenVMS operating systems:
When adding new widgets or changing widget characteristics, start with a copy of one of the two WML files. Use DECW$DXM_MOTIF.WML if you are using any Digital widgets. Use the OSF/Motif WML files if your application requires a strict OSF widget set.
Digital has also included the following two WMD files (which correspond to the two WML files):
To allow you to add UIL support for additional widgets, Digital has provided you with the following files:
DECW$SYSTEM_DEFAULTS:DECW$UIL_OSF_MOTIF_1_1.WMLUse either of the previous files as a template for your own WML file.
DECW$SYSTEM_DEFAULTS:DECW$UIL_DXM_MOTIF.WML
The procedure is as follows:
|
@DECW$EXAMPLES:UILWMDCREATE filename.WML |
This command procedure performs three major functions:
|
UIL/MOTIF/WIDGET_META_LANGUAGE=filename.WMD filename.UIL |
| Previous | Next | Contents | Index |