<!-- $XConsortium: file.sgm /main/10 1996/11/15 15:24:47 cdedoc $ -->
<!-- (c) Copyright 1995 Digital Equipment Corporation. -->
<!-- (c) Copyright 1995 Hewlett-Packard Company. -->
<!-- (c) Copyright 1995 International Business Machines Corp. -->
<!-- (c) Copyright 1995 Sun Microsystems, Inc. -->
<!-- (c) Copyright 1995 Novell, Inc. -->
<!-- (c) Copyright 1995 FUJITSU LIMITED. -->
<!-- (c) Copyright 1995 Hitachi. -->
<RefEntry Id="CDEMX.MAN11.rsml.1" Remap="">
<RefMeta>
<RefEntryTitle>dtfile</RefEntryTitle>
<ManVolNum>user cmd</ManVolNum>
</RefMeta>
<RefNameDiv>
<RefName><Command>dtfile</Command></RefName>
<RefPurpose>the CDE File Manager
</RefPurpose>
</RefNameDiv>
<RefSynopsisDiv>
<CmdSynopsis>
<Command>dtfile</Command>
<Arg Choice="opt">options...</Arg>
</CmdSynopsis>
</RefSynopsisDiv>
<RefSect1>
<Title>DESCRIPTION</Title>
<note>
<para>Although <Command>dtfile</Command> may be invoked from the command line, developers
who wish to interface to File Manager function should use CDE Actions
(see "CDE Actions" in "RELATED INFORMATION").
</para>
</note>
<Para>The CDE File Manager is the Desktop's
primary interface to the file system. It provides a GUI for file
manipulation and application execution.
</Para>
<Para>The main File Manager interface consists of a top-level window which
shows the contents of a single folder or a set of nested folders
(folder tree). A single File Manager process may provide many
top-level windows each of which may show the contents of a different
folder.
</Para>
<Para>The File Manager has many manipulation features. It will allow a user
to:
</Para>
<!--Start of RS / RE range-->
<Para>- Traverse folders via a double-click, menu options, or a
click-and-type mechanism.
</Para>
<Para>- Change folder display modes (i.e. large icons, small icons,
alphabetical order, date order, single folder, folder tree,
etc.) and filtering options.
</Para>
<Para>- Create, move, copy, link, and delete objects via menu options
and/or drag-and-drop.
</Para>
<Para>- Rename objects via menu options or a click-and-type mechanism.
</Para>
<Para>- Modify object file system attributes via menu options.
</Para>
<Para>- Invoke actions (applications such as Edit or Print) on objects
via a double-click, menu options, or drag-and-drop.
</Para>
<Para>- Locate objects by name or by contents.
</Para>
<Para>- Place frequently used objects on a desktop/workspace.
</Para>
<!--End of RS / RE range-->
<Para>The File Manager also supports additional features for two special
types of top level windows: application views and the trash container.
</Para>
<Para>Application views are designed to organize application objects such as
actions.
</Para>
<Para>Application view windows have the same general appearance and function
as folder windows with the following exceptions:
</Para>
<!--Start of RS / RE range-->
<Para>- The user is not allowed to traverse above the main application
view.
</Para>
<Para>- When a user drags an object from an application view to another
application view or to a folder, the object is copied to the new
location (as opposed to being moved as is the case in a folder.)
</Para>
<!--End of RS / RE range-->
<Para>The trash container is designed to be a holding area for objects that
users wish to delete. Like application views, the trash container
window has the same general appearance as a folder window; however,
trash container function differs as follows: Users may move, restore,
or delete a trash object and may change the display mode for the trash
container. Users MAY NOT:
</Para>
<!--Start of RS / RE range-->
<Para>- Traverse out of the trash container.
</Para>
<Para>- Copy, rename, or execute any other manipulation on a trash
object.
</Para>
<!--End of RS / RE range-->
<RefSect2>
<Title>Key Supported Tasks</Title>
<Para></Para>
</RefSect2>
<RefSect2>
<Title>Desktop</Title>
<Para>A Desktop is a place where users can store commonly used objects for
easy access. Within the CDE, each workspace is
considered a Desktop. A user may place any object on the background of
a workspace and the object will remain there. The user can also select
actions for that object via a popup menu which is activated by
selecting mouse button 3.
</Para>
</RefSect2>
<RefSect2>
<Title>Folder Window</Title>
<Para>A folder window is a top-level window which shows the contents of a
single folder or a set of nested folders (folder tree).
Folder windows may be launched from the Front Panel, actions, or a
command line interface. The objects in a folder are displayed in a
user-selected icon/text combination. The icon visual shows the icon
type. Users can use menu options to reread folder views, open new
folder views, and to select/unselect all objects in a folder. In tree
mode, buttons next to icons representing subfolders allow users to
expand or collapse folder branches and to control whether all
objects in a folder or only the folder structure is shown in the
window.
</Para>
</RefSect2>
<RefSect2>
<Title>Application View Window</Title>
<Para>A application view window is a top-level window which shows the
contents of a single application folder. An application folder
is a restricted folder which is designed to organize application
objects such as actions. Application views are launched from the Front
Panel or a predefined action.
</Para>
</RefSect2>
<RefSect2>
<Title>Trash Container Window</Title>
<Para>When an object is no longer needed, a user can move the object to the
trash container. The trash container is a restricted folder which
is used to store files temporarily until the user asks to permanently
remove them. A user can view the contents of the trash container in a
top level window which is launched from a menu option in a folder or
application view, the Front Panel, or a predefined action. Users can
also restore objects from the trash container provided that actions
have not been taken to permanently remove them.
</Para>
</RefSect2>
<RefSect2>
<Title>Object Movement and Modification</Title>
<Para>Menu options are provided which allow users to create objects, rename
objects, copy objects, modify object properties, and move objects to a
desktop or to the trash container. (NOTE: In addition to the menu
options, users can rename objects with the following steps: 1. Click
mouse button 1 on the text portion of an object icon, 2. An edit box
will appear; type the new file name, 3. Select Enter.)
</Para>
</RefSect2>
<RefSect2>
<Title>File System Awareness</Title>
<Para>The File Manager is file system aware. It can be enabled to launch
dialogs that allow editing of file system specific parameters (See
FILES - <filename>dtfile.config</filename>).
</Para>
</RefSect2>
<RefSect2>
<Title>Object Search</Title>
<Para>A menu option/dialog box combination is provided to allow users to
search for objects by name or by content. During a name search, the
File Manager looks for an object whose name matches specified search
criteria. During a content search, the File Manager looks for an
object which contains specified character strings. Content searches
are case insensitive. When an object is located, the File Manager can
either open a window to display the folder where the object is
located or place the object on the desktop.
</Para>
</RefSect2>
<RefSect2>
<Title>Folder Traversal</Title>
<Para>Simple folder traversal can be accomplished by double-clicking on a
folder icon. This action displays the contents of the selected folder.
If the user moves the mouse before releasing the mouse button on the
second click of a double click ("double-click-drag" action), a new
window will pop up to show the contents of the selected folder. The
new window will be placed at the position where the user released the
mouse button.
</Para>
<Para>In addition, the File Manager provides the following folder
traversal mechanisms:
</Para>
<VariableList>
<VarListEntry>
<Term></Term>
<ListItem>
<Para>This dialog lists folders that are frequently used.
A user may traverse to a new folder by double-clicking on
a folder in this list.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Click-and-Type Mechanism</Term>
<ListItem>
<Para>When a user clicks on the "Text Path",
it is remapped to a text edit widget. Again the user may
traverse to a new folder by typing a new folder title and
then selecting Enter.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Iconic Path Selection</Term>
<ListItem>
<Para>If a user double-clicks on a folder icon in the iconic
path, the File Manager will update the current window to show
the contents of the selected folder.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Find Dialog</Term>
<ListItem>
<Para>This dialog searches the file system for a folder or
folders whose name(s) match user-supplied criteria. The
user may open new windows for folders located by the
Find dialog.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Home and Up Menu Options</Term>
<ListItem>
<Para>These options allow the user to traverse
to $HOME and parent folders respectively.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Tree Display Mode</Term>
<ListItem>
<Para>In this mode, the folder hierarchy is displayed as
a tree that can be traversed by selecting the buttons located
next to the folder icons (See Tree Mode below)
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Tree Mode</Term>
<ListItem>
<Para>In tree mode, the current folder and its subfolders are
shown initially. Traversing into subfolders can be
accomplished by single-clicking on the button next to the
folder icon. Clicking the left mouse button over the folder
button cycles through three states: partially expanded, fully
expanded, and collapsed. Clicking the middle mouse button
cycles through these three states in reverse order. When the
user first clicks on the folder button, the contents of the
subfolder are read and added to the tree (partially
expanded state). If the user clicks on the button a second
time, the non-folder contents of the folder are added to
the tree (fully expanded state). If the user clicks on the button
a third time, the folder contents are removed from the tree
(collapsed state). If a folder does not have subfolders,
the partially expanded state is skipped. If a folder does not
contain non-folder objects, the fully expanded state is
skipped. If a folder is empty, the folder button is
desensitized.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Setting Display Preferences</Title>
<Para>The File Manager provides many options for displaying objects. For
example, objects can be displayed in iconic or non-iconic formats. The
user may also choose to position files in either a grid or random
pattern. (NOTE: The File Manager provides a Clean Up menu option which
can be used to align randomly placed objects to a grid pattern.) If
the user has write permission in a folder and the user chooses to
randomly place files, the positioning information is saved when the
user leaves the folder. Therefore, each time the user reenters the
folder the files will be positioned as they were when the user left
the folder.
</Para>
</RefSect2>
<RefSect2>
<Title>Object Filtering</Title>
<Para>Folders can contain many different types of objects. The File
Manager's filtering mechanism allows the user to selectively display
objects depending on their type. The File Manager also provides a Show
Hidden Files menu toggle option which allows the user to turn the
filtering mechanism on and off.
</Para>
</RefSect2>
<RefSect2>
<Title>Object Type/Action Association</Title>
<Para>When an object is selected, the File Manager builds an Actions menu
for that object based on the type of the object. For example, data
files are provided with a menu containing the following actions: Open,
Print. Folders are provided with a menu containing: OpenNewView,
OpenInPlace. Actions can be run on an object by selecting an object
and then selecting an action from the Actions menu. Also,
double-clicking on an object will activate the default action for the
object.
</Para>
</RefSect2>
<RefSect2>
<Title>Quick Help</Title>
<Para>The File Manager provides quick help via F1 throughout the <Command>dtfile</Command>
application. This includes quick help on object icons. To access quick
help, position the cursor/pointer over the item for which you wish to
get help, then press F1.
</Para>
</RefSect2>
<RefSect2>
<Title>Popup Menus</Title>
<Para>The File Manager provides popup menus for objects within a File
Manager view or on the Desktop. To access the popup menu for a
particular object, position the cursor over the object and press and
hold mouse button 3. A popup menu will appear. The menu will contain a
list of the actions which can be performed on that particular object.
If multiple objects are selected, the popup menu will show all of
those actions which can be done on all of the selected objects at
once.
</Para>
</RefSect2>
<RefSect2>
<Title>Direct Manipulation</Title>
<Para>Objects can be dragged between different
File Manager views, to Desktops, and to cooperating clients.
Direct manipulation may be used to copy, move, or link objects as well
as to supply objects as input to applications.
See the REGISTERING OBJECTS AS DROP SITES section.
The File Manager also supports drops of buffers on its views and objects
such as CDE Mailer attachments.
</Para>
</RefSect2>
<RefSect2>
<Title>Terminal Access</Title>
<Para>A menu option is provided which gives users access to terminal
windows.
</Para>
</RefSect2>
<RefSect2>
<Title>Exit Services</Title>
<Para>Menu options are provided which allow users to close File Manager
views and which allow users to save setting information before exiting
a File Manager session.
</Para>
</RefSect2>
<RefSect2>
<Title>Object Name Completion</Title>
<Para>The File Manager supports object name completion in the following text
widgets: the "Text path", the "Destination Folder" field of
the "Go To" dialog, the "Search Folder" field of the "Find"
dialog. Press control+spacebar and the name will complete to the extent
that it can.
</Para>
</RefSect2>
<RefSect2>
<Title>Multibyte Character Set Support</Title>
<Para>The File Manager is fully internationalized. It supports both
single-byte and multi-byte locales.
</Para>
</RefSect2>
<RefSect2>
<Title>Error Condition Notification</Title>
<Para>The File Manager uses dialog boxes to report various error conditions.
</Para>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>OPTIONS</Title>
<Para>The following options are available from the command line:
</Para>
<RefSect2>
<Title>-noview</Title>
<Para><Command>Dtfile</Command> runs in "server mode". In other words, a window is not
displayed until a cooperating client makes a request to display a
folder.
</Para>
</RefSect2>
<RefSect2>
<Title>-session <symbol>session_file</symbol></Title>
<Para><Command>Dtfile</Command> runs with the session file specified in the session_file
parameter. Session files are generated as a <Command>dtfile</Command> session shuts down.
</Para>
</RefSect2>
<RefSect2>
<Title>-dir <symbol>folder</symbol></Title>
<Para>OR
</Para>
</RefSect2>
<RefSect2>
<Title>-folder <symbol>folder</symbol></Title>
<Para><Command>Dtfile</Command> displays a window for each folder specified in the folder
parameter (Note: No spaces are allowed in folder). If this option is
not used, the user's current folder (the folder from which
<Command>dtfile</Command> was started) is displayed.
</Para>
</RefSect2>
<RefSect2>
<Title>-title <symbol>title_name</symbol></Title>
<Para>This option allows the user to specify a title (title_name) for the
File Manager windows. All windows and dialogs generated by this
session will use this title. If this option is not used, the name of
the folder shown in a window will be used as the window title.
</Para>
</RefSect2>
<RefSect2>
<Title>-help_volume <symbol>help_volume_name</symbol></Title>
<Para>This option allows the user to specify a help volume
(<symbol>help_volume_name</symbol>) to use with the File Manager windows. This option
is useful if the user is using the File Manager to display a specific
folder and wants to have specific help for that folder. Note:
All File Manager views that are created from this folder will also
use this help volume.
</Para>
</RefSect2>
<RefSect2>
<Title>-restricted</Title>
<Para><Command>Dtfile</Command> will not display folders above the restricted folder. If
the <literal>-dir</literal> option is used, the folder specified by that option is the
restricted folder. If the <literal>-dir</literal> option is not used, the user's
current folder is the restricted folder.
</Para>
</RefSect2>
<RefSect2>
<Title>-grid on/off</Title>
<Para><Command>Dtfile</Command> displays files in a pattern specified by the on/off parameter.
As the name implies, on/off will either have a value of <literal>on</literal> or a value
of <literal>off</literal>.
</Para>
<VariableList>
<VarListEntry>
<Term>on</Term>
<ListItem>
<Para>Files are always displayed in a grid pattern. The
File Manager automatically rearranges the files if a file is moved.
This is the default pattern.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>off</Term>
<ListItem>
<Para>Files are always displayed where they are placed
by the user. The File Manager does not rearrange the files.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>-tree on/off</Title>
<Para>This option controls whether <Command>dtfile</Command> displays files in single folder
mode (off) or in folder tree mode (on).
</Para>
</RefSect2>
<RefSect2>
<Title>-tree_files <symbol>never/always/choose</symbol></Title>
<Para>This option controls whether or not files may be displayed in the
folder tree mode.
</Para>
<VariableList>
<VarListEntry>
<Term>never</Term>
<ListItem>
<Para>Files are never displayed. The user may toggle
between two states: partially expanded and collapsed.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>always</Term>
<ListItem>
<Para>Files are always displayed. The user may toggle
between two states: fully expanded and collapsed.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>choose</Term>
<ListItem>
<Para>Files may or may not be displayed. The user may
toggle between three states: partially expanded, fully expanded, or
collapsed.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>-order <symbol>order_type</symbol></Title>
<Para><Command>Dtfile</Command> displays files in the order specified by the order_type
parameter. Order_type must have one of the following values:
</Para>
<VariableList>
<VarListEntry>
<Term>alphabetical</Term>
<ListItem>
<Para>Files are displayed in alphabetical
order. This is the default order.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>file_type</Term>
<ListItem>
<Para>Files are displayed in groups based on their
filetypes.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>date</Term>
<ListItem>
<Para>Files are displayed in an order based on the date
when they were last modified.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>size</Term>
<ListItem>
<Para>Files are displayed in an order based on their size.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>-view <symbol>view_type</symbol></Title>
<Para><Command>Dtfile</Command> displays files in the format specified by the view_type
parameter. <symbol role="variable">View_type</symbol> must have one of the following values:
</Para>
<VariableList>
<VarListEntry>
<Term>no_icon</Term>
<ListItem>
<Para>Files are displayed by name.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>large_icon</Term>
<ListItem>
<Para>Files are displayed by name and large icon.
The icon shows the type of the file. This is the default format.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>small_icon</Term>
<ListItem>
<Para>Files are displayed by name and small icon.
The icon shows the type of the file.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>attributes</Term>
<ListItem>
<Para>Files are displayed by attributes. A small
icon is used to represent the file type. (This format is similar to
the listing obtained by issuing ls -l from an aixterm command line.)
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>-direction <symbol>direction</symbol></Title>
<Para><Command>Dtfile</Command> displays files in the direction specified by the direction
parameter. Direction must have one of the following values:
</Para>
<VariableList>
<VarListEntry>
<Term>ascending</Term>
<ListItem>
<Para>Files are displayed in an ascending
direction. This is the default direction.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>descending</Term>
<ListItem>
<Para>Files are displayed in a descending
direction.
</Para>
<Para>Both the <literal>-noview</literal> and the <literal>-session</literal> options are normally used by the
session manger to start <Command>dtfile</Command>. The <literal>-title</literal>,
<literal>-help_volume</literal>, and
<literal>-restricted</literal> options can also be set via resources (See the RESOURCES
section.) The <literal>-grid</literal>, <literal>-tree</literal>, <literal>-treefiles</literal>, <literal>-order</literal>,
<literal>-view</literal>, and <literal>-direction</literal>
options can also be set by 1) selecting the Set Preferences option
from the View pulldown menu or by 2) resources (See the RESOURCES
section.)
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>-small_icon_width <symbol>size</symbol></Title>
<Para>The default small icon width is 24 pixels. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this option to specify small icon width. Size must be in pixel.
</Para>
</RefSect2>
<RefSect2>
<Title>-small_icon_height <symbol>size</symbol></Title>
<Para>The default small icon height is 24 pixels. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this option to specify small icon height. Size must be in pixel.
</Para>
</RefSect2>
<RefSect2>
<Title>-large_icon_width <symbol>size</symbol></Title>
<Para>The default large icon width is 38 pixels. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this option to specify large icon width. Size must be in pixel.
</Para>
</RefSect2>
<RefSect2>
<Title>-large_icon_height <symbol>size</symbol></Title>
<Para>The default large icon height is 38 pixels. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this option to specify large icon height. Size must be in pixel.
</Para>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>EXAMPLES</Title>
<RefSect2>
<Title>dtfile -view no_icon -order date -direction</Title>
<Para>The File Manager will display files in text format, ordered by date,
most current to oldest date.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile -dir /u/guest -restricted</Title>
<Para>The File Manager will begin execution by displaying a window showing
the /u/guest folder. The user will not be allowed to navigate above
this folder.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile -session session.jan.12</Title>
<Para>The File Manager will run with the session file called session.jan.12.
</Para>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>RESOURCES</Title>
<informaltable remap="center" orient="port">
<tgroup cols="4" colsep="0" rowsep="0">
<colspec align="left" colwidth="123*">
<colspec align="left" colwidth="128*">
<colspec align="left" colwidth="76*">
<colspec align="left" colwidth="129*">
<tbody>
<row>
<entry align="left" valign="top"><literal>Name</literal></entry>
<entry align="left" valign="top"><literal>Class</literal></entry>
<entry align="left" valign="top"><literal>Type</literal></entry>
<entry align="left" valign="top"><literal>Default</literal></entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">dirWidth</systemitem></entry>
<entry align="left" valign="top"><classname>DirWidth</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRDimension</structname></entry>
<entry align="left" valign="top">555</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">dirHeight</systemitem></entry>
<entry align="left" valign="top"><classname>DirHeight</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRDimension</structname></entry>
<entry align="left" valign="top">305</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">appWidth</systemitem></entry>
<entry align="left" valign="top"><classname>AppWidth</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRDimension</structname></entry>
<entry align="left" valign="top">365</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">appHeight</systemitem></entry>
<entry align="left" valign="top"><classname>AppHeight</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRDimension</structname></entry>
<entry align="left" valign="top">365</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">rereadTime</systemitem></entry>
<entry align="left" valign="top"><classname>RereadTime</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">10 (s)</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">checkBrokenLink</systemitem></entry>
<entry align="left" valign="top"><classname>CheckBrokenLink</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">180 (s)</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">maxDirectoryProcesses</systemitem></entry>
<entry align="left" valign="top"><classname>MaxDirectoryProcesses</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">10</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">maxRereadProcesses</systemitem></entry>
<entry align="left" valign="top"><classname>MaxRereadProcesses</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">5</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">maxRereadProcsPerTick</systemitem></entry>
<entry align="left" valign="top"><classname>MaxRereadProcsPerTick</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">1</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">moveThreshold</systemitem></entry>
<entry align="left" valign="top"><classname>MoveThreshold</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">4 (pix)</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">title</systemitem></entry>
<entry align="left" valign="top"><classname>Title</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRString</structname></entry>
<entry align="left" valign="top">NULL</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">rootTitle</systemitem></entry>
<entry align="left" valign="top"><classname>RootTitle</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRString</structname></entry>
<entry align="left" valign="top">"ROOT"</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">help_volume</systemitem></entry>
<entry align="left" valign="top"><classname>Help_volume</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRString</structname></entry>
<entry align="left" valign="top">NULL</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">fileManagerIcon</systemitem></entry>
<entry align="left" valign="top"><classname>FileManagerIcon</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRString</structname></entry>
<entry align="left" valign="top">home.i.bm</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">restrictMode</systemitem></entry>
<entry align="left" valign="top"><classname>RestrictMode</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRBoolean</structname></entry>
<entry align="left" valign="top">false</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">showFilesystem</systemitem></entry>
<entry align="left" valign="top"><classname>ShowFilesystem</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRBoolean</structname></entry>
<entry align="left" valign="top">true</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">grid</systemitem></entry>
<entry align="left" valign="top"><classname>Grid</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">on</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">treeView</systemitem></entry>
<entry align="left" valign="top"><classname>TreeView</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">off</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">treeFiles</systemitem></entry>
<entry align="left" valign="top"><classname>TreeFiles</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">never</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">order</systemitem></entry>
<entry align="left" valign="top"><classname>Order</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">alpha</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">view</systemitem></entry>
<entry align="left" valign="top"><classname>View</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">large_icon</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">direction</systemitem></entry>
<entry align="left" valign="top"><classname>Direction</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">ascend</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">desktopIcon</systemitem></entry>
<entry align="left" valign="top"><classname>DesktopIcon</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">large</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">objectPlacement</systemitem></entry>
<entry align="left" valign="top"><classname>ObjectPlacement</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">top rt</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">openFolder</systemitem></entry>
<entry align="left" valign="top"><classname>OpenFolder</classname></entry>
<entry align="left" valign="top"><structname role="typdef">string</structname></entry>
<entry align="left" valign="top">current</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">smallIconWidth</systemitem></entry>
<entry align="left" valign="top"><classname>SmallIconWidth</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">16</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">smallIconHeight</systemitem></entry>
<entry align="left" valign="top"><classname>SmallIconHeight</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">16</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">largeIconWidth</systemitem></entry>
<entry align="left" valign="top"><classname>LargeIconWidth</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">32</entry></row>

<row>
<entry align="left" valign="top"><systemitem class="resource">largeIconHeight</systemitem></entry>
<entry align="left" valign="top"><classname>LargeIconHeight</classname></entry>
<entry align="left" valign="top"><structname role="typdef">XmRInt</structname></entry>
<entry align="left" valign="top">32</entry></row>

</tbody></tgroup></informaltable>

<RefSect2>
<Title>Dtfile *dirWidth</Title>
<Para>Specifies the width of a File Manager folder window.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *dirHeight</Title>
<Para>Specifies the height of a File Manager folder window.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *appWidth</Title>
<Para>Specifies the width of a File Manager application view window
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *appHeight</Title>
<Para>Specifies the height of a File Manager application view window.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *rereadTime</Title>
<Para>Determines how often the File Manager rereads the open folders and
monitors the Desktop objects. This resource must be specified in
seconds. If it is set to 0, the reread will not occur and the user
must manually reread the folders. This will conserve processor
cycles but may cause views to become stale as well.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *checkBrokenLink</Title>
<Para>Determines how often the File Manager checks open folders for
broken links. This resource must be specified in seconds. If it is set
to 0, the check for broken links will not occur.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *maxDirectoryProcesses</Title>
<Para>Specifies the maximum number of background processes which may be
devoted to folder activities (ie. reading the folder, updating
the folder, writing positional information for the folder,
checking for broken links or checking for other folder updates).
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *maxRereadProcesses</Title>
<Para>Specifies the maximum number of background processes which may be
devoted to folder reread activities (ie. checking for broken links
or checking for other folder updates).
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *maxRereadProcsPerTick</Title>
<Para>Specifies the number of reread processes that may be started per
reread timer tick. In other words, the currently displayed folders
will be checked for changes in a round- robin fashion, x folders
per timer tick where x is equal to maxRereadProcsPerTick.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *moveThreshold</Title>
<Para>Specifies the number of pixels that the cursor must move while a
button is held down before the drag controller recognizes the button
down action as a drag.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *title</Title>
<Para>Specifies the title for all File Manager windows. If this resource is
set to NULL, then the title of each File Manger window will be the
name of the folder displayed in the window.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *rootTitle</Title>
<Para>Specifies the title of the root folder. This title will appear in
the title bar of any File Manager window which is showing the root
folder. It will also be the name shown with the icon representing
the root folder on the Desktop.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile *help_volume</Title>
<Para>Specifies the help volume.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*fileManagerIcon</Literal></Title>
<Para>Specifies the icon to display when a File Manager window is minimized.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*restrictMode</Literal></Title>
<Para>Determines whether or not the user is operating in restricted mode. If
this resource is set to true, the user is operating in restricted
mode. The user is restricted to the user's $HOME folder and below.
All folder change requests are interpreted relative to the user's
$HOME folder. All folders above the user's $HOME folder are
hidden from the user. If this resource is set to false, the user's
folder requests are not limited in any way.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*showFilesystem</Literal></Title>
<Para>Determines whether or not the path name for the current folder is
visible. If this resource is set to TRUE, the path name is visible. If
it is set to FALSE, the path name is not visible. This resource can be
used to hide the file system from the user.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*grid</Literal></Title>
<Para>Determines the pattern used to display files. This resource must have
one of two values:
</Para>
<VariableList>
<VarListEntry>
<Term>on</Term>
<ListItem>
<Para>Files are always displayed in a grid pattern. The
File Manager automatically rearranges the files if a file is moved.
This is the default pattern.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>off</Term>
<ListItem>
<Para>Files are always displayed where they are placed
by the user. The File Manager does not rearrange the files.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>treeView</Literal></Title>
<Para>Determines whether files are displayed in single folder mode (on)
or folder tree mode (off).
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*treeFiles</Literal></Title>
<VariableList>
<VarListEntry>
<Term>This</Term>
<ListItem>
<Para>folder tree mode.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>never</Term>
<ListItem>
<Para>Files are never displayed. The user may toggle
between two states: partially expanded and collapsed.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>always</Term>
<ListItem>
<Para>Files are always displayed. The user may toggle
between two states: fully expanded and collapsed.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>choose</Term>
<ListItem>
<Para>Files may or may not be displayed. The user may
toggle between three states: partially expanded, fully expanded, or
collapsed.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*order</Literal></Title>
<Para>Determines the order used to display files. This resource must have
one of four values:
</Para>
<VariableList>
<VarListEntry>
<Term>alphabetical</Term>
<ListItem>
<Para>Files are displayed in alphabetical
order. This is the default order.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>file_type</Term>
<ListItem>
<Para>Files are displayed in groups based on their
filetypes.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>date</Term>
<ListItem>
<Para>Files are displayed in an order based on the date
when they were last modified.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>size</Term>
<ListItem>
<Para>Files are displayed in an order based on their
size.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*view</Literal></Title>
<Para>Determines the format used to display files. This resource must have
one of four values:
</Para>
<VariableList>
<VarListEntry>
<Term>no_icon</Term>
<ListItem>
<Para>Files are displayed by name.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>large_icon</Term>
<ListItem>
<Para>Files are displayed by name and large icon.
The icon shows the type of the file. This is the default format.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>small_icon</Term>
<ListItem>
<Para>Files are displayed by name and small icon.
The icon shows the type of the file.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>attributes</Term>
<ListItem>
<Para>Files are displayed by attributes. A small
icon is used to represent the file type. (This format is similar to
the listing obtained by issuing ls -l from an aixterm command line.)
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*direction</Literal></Title>
<Para>Determines the direction used to display files. This resource must
have one of two values:
</Para>
<VariableList>
<VarListEntry>
<Term>ascending</Term>
<ListItem>
<Para>Files are displayed in an ascending
direction. This is the default direction.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>descending</Term>
<ListItem>
<Para>Files are displayed in a descending
direction.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*desktopIcon</Literal></Title>
<Para>Determines the type of icon used to represent files/folders on the
Desktop. This resource must have one of two values:
</Para>
<VariableList>
<VarListEntry>
<Term>large</Term>
<ListItem>
<Para>Large icons are used to represent
files/folders on the Desktop.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>small</Term>
<ListItem>
<Para>Small icons are used top represent
files/folders on the Desktop.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile *objectPlacement</Title>
<Para>Specifies the placement scheme used to place objects on the Desktop.
This resource has the following syntax: primary_layout
secondary_layout. The primary_layout determines whether an object
placed on the Desktop is put into a row or a column. The
secondary_layout determines where to place new rows or columns. The
layouts must have one of four values:
</Para>
<VariableList>
<VarListEntry>
<Term>top</Term>
<ListItem>
<Para>Objects are placed top to bottom. (vertical value)
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>bottom</Term>
<ListItem>
<Para>Objects are placed bottom to top. (vertical
value)
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>left</Term>
<ListItem>
<Para>Objects are placed left to right. (horizontal
value)
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>right</Term>
<ListItem>
<Para>Objects are placed right to left. (horizontal
value)
The user should use one value from each
category--vertical and horizontal. For example if the primary_layout
is top, then the secondary_layout should be either left or right. In
this case, the secondary_layout should NOT be top or bottom. Likewise,
if the primary_layout is left, then the secondary_layout should be
either top or bottom. In this case, the secondary_layout should NOT be
left or right.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*openFolder</Literal></Title>
<Para>Determines how a folder is opened when a user double clicks on a
folder icon. This resource must have one of two values:
</Para>
<VariableList>
<VarListEntry>
<Term>current</Term>
<ListItem>
<Para>Open the folder in the current window.
(This is the same as using the OpenInPlace action.)
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>new</Term>
<ListItem>
<Para>Open the folder in a new window or, if a window showing this
folder currently exists, move the existing window to this
workspace and place it in the forefront. (Note: Only one view
of a folder can be opened at once under these conditions.
If the user defines an 'open folder' file type, the folder icon
will change state to indicate when a given folder is currently
open somewhere in the user's environment. In order to define
an 'open folder' file type, the user should 1) define a file
type with the same name as the normal folder file type
except that the name is preceded with <filename>OPEN_</filename>, 2) create an
'open folder' icon, and 3) use the name of the 'open folder' icon
as the icon name in the 'open folder' file type definition.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*smallIconWidth</Literal></Title>
<Para>The default small icon size is 16 pixel. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this resource to specify small icon width.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*smallIconHeight</Literal></Title>
<Para>The default small icon height is 16 pixel. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this resource to specify small icon height.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*largeIconWidth</Literal></Title>
<Para>The default large icon width is 32 pixel. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this resource to specify large icon width.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile <Literal>*largeIconHeight</Literal></Title>
<Para>The default large icon height is 16 pixel. Any customized icons
that have larger size will be clipped. To avoid clipping,
use this resource to specify large icon height.
</Para>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>ASYNCHRONOUS EVENTS</Title>
<RefSect2>
<Title>Tool Talk Messages</Title>
<Para>The following Tool Talk Desktop and Media requests
are supported by the File Manager:
</Para>
<VariableList>
<VarListEntry>
<Term>Edit (Document and Media Exchange Message Set)</Term>
<ListItem>
<Para>The specified file is opened for editing in a separate window.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Display (Document and Media Exchange Message Set)</Term>
<ListItem>
<Para>The specified file is opened for viewing only in a separate window.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Quit (Desktop Message Set)</Term>
<ListItem>
<Para>This request will terminate the File Manager and its children.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>RELATED INFORMATION</Title>
<RefSect2>
<Title>CDE Actions</Title>
<Para>The following Desktop actions can be used to access File Manager
folder and application view windows as well as the File Manager trash
container window. These actions are defined in
<filename>/usr/dt/appconfig/types/$LANG/dtfile.dt</filename>.
</Para>
<VariableList>
<VarListEntry>
<Term>Dtfile</Term>
<ListItem>
<Para>Opens a folder window for a specified folder.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Dtappmgr</Term>
<ListItem>
<Para>Opens an application view window.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>Dttrash</Term>
<ListItem>
<Para>Opens a window to display the contents of the Trash Container.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>OpenNewView</Term>
<ListItem>
<Para>Opens a new window to show the contents of the selected folder.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>OpenInPlace</Term>
<ListItem>
<Para>Displays the contents of the selected folder in the current window.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>FILESYSTEM_MOVE</Term>
<ListItem>
<Para>Moves a set of dragged objects to the selected drop site.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>FILESYSTEM_COPY</Term>
<ListItem>
<Para>Copies a set of dragged objects to the selected drop site.
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>FILESYSTEM_LINK</Term>
<ListItem>
<Para>Creates symbolic links to a set of dragged objects
from the selected drop site.
</Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
<RefSect2>
<Title>Registering Objects As Drop Sites</Title>
<Para>Every CDE data type has three associated drop
attributes: <literal>MOVE_TO_ACTION</literal>, <literal>COPY_TO_ACTION</literal>,
and <literal>LINK_TO_ACTION</literal>. The File
Manager registers every object whose data type has a value for at
least one of these attributes as a drop site.
</Para>
<Para>When an object is dragged to a drop site, the File Manager is
triggered by the drag-and-drop API. The drag-and-drop API provides the
File Manager with a gesture code (Move, Copy, or Link) which
is dictated by a combination of the modifier keys used and the manner
in which the drop site was registered. Based on the gesture code and
the data type of the drop site, the File Manager retrieves a drop
attribute (ie. <literal>MOVE_TO_ACTION</literal>) from the Datatypes database. The File
Manager then calls the CDE API, <command>DtActionInvoke</command> according to the following rules:
</Para>
<Para>1. If objects A and B are dropped on object C, then the parameters to
<command>DtActionInvoke</command> are as follows:
</Para>
<VariableList>
<VarListEntry>
<Term>DtActionInvoke (drop action name, C, A, B)</Term>
<ListItem>
<Para>2. There is one exception, if object C is an action, then the
parameters will not include object C. ie
</Para>
</ListItem>
</VarListEntry>
<VarListEntry>
<Term>DtActionInvoke (drop action name, A, B)</Term>
<ListItem>
<Para></Para>
</ListItem>
</VarListEntry>
</VariableList>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>FILES</Title>
<Para>File Manager uses the following files.
</Para>
<RefSect2>
<Title>dtfile</Title>
<Para>Executable file. This file is located in <filename>/usr/dt/bin</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile_copy</Title>
<Para>Utility to support folder copy. This executable file is located in
<filename>/usr/dt/bin</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile_error</Title>
<Para>This script can be used by applications to display an error
dialog when it would be difficult or impossible to do in the
context of the executing program. For example, it can be used
when exec fails in a child process or if an error is detected
before an applications main window can be realized.
This executable file is located in
<filename>/usr/dt/bin</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtfile</Title>
<Para>App-defaults file. This file is located in <filename>/usr/dt/app-defaults/$LANG</filename>.
See the RESOURCES section for a list of those resources which can be
set using the app-defaults file.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile.config</Title>
<Para>Configuration file. This file is located in <filename>/usr/dt/config/$LANG</filename>. It may be
used to add a file system specific button to the File Properties
dialog. This button launches an additional dialog allowing the user to
modify file system specific parameters. For example, the user can add
a stanza defining a dialog for setting the Access Control List for a
file from the Andrew File System. If the user also adds a stanza
defining a dialog for setting the Access Control List for the
Distributed File System, then the File Manager will determine which
dialog is associated with the selected file and will display that
dialog. See the text in the <filename>dtfile.config</filename> file for instructions on how
to create stanzas.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile.dt</Title>
<Para>CDE type/action definition file. This file is
located in <filename>/usr/dt/appconfig/types/$LANG</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>Dtinf.*, Dtlink.*, DtdirR.*, Fphome*, Fpapps*, Fptrsh*</Title>
<Para>Icon files. These files are located in <filename>/usr/dt/appconfig/icons/$LANG</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile.cat</Title>
<Para>Message catalog. This file is located in <filename>/usr/dt/lib/nls/msg/$LANG</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>Filemgr.sdl, FM*.tif, FM*.pm</Title>
<Para>Help files. These files are located in <filename>/usr/dt/appconfig/help/$LANG/Filemgr</filename> and
<filename>/usr/dt/appconfig/help/$LANG/Filemgr/graphics</filename>.
</Para>
</RefSect2>
<RefSect2>
<Title>dtfile.1</Title>
<Para>Man page.
</Para>
</RefSect2>
</RefSect1>
<RefSect1>
<Title>SEE ALSO</Title>
<Para>- Data Interchange Mechanisms (drag-and-drop library)
</Para>
<Para>- Window Manager
</Para>
<Para>- Object Services (action/filetype database)
</Para>
<Para>- ICCCM Messaging
</Para>
<Para>- ToolTalk
</Para>
</RefSect1>
</RefEntry>
<!--fickle 1.12 mancsf-to-docbook 1.3 08/21/95 21:30:04-->
