If the action icon is double-clicked, theĪction opens an empty fax composer window. See Specifying the Window Support for the Action.ĮXEC_STRING-the syntax %Arg_1% accepts a dropped file. Keyword specifies that the action does not have to run in a terminal emulator The WINDOW_TYPE and EXEC_STRING fields describe the behavior of the action. Put the following action definition into the file: ACTION FaxComposerĮXEC_STRING /usr/fax/bin/faxcompose -c %Arg_1% The command for starting the fax application is: /usr/fax/bin/faxcompose Ĭreate the file HomeDirectory /.dt/types/Fax.dt. Steps create a personal action that starts a fax application on remote systemĪppServerA. To create the action file, create an executable file with the same nameĪs action_name. (If theĪction is written to start an application, the icon is called an application icon.) In File Manager or Application Manager that represents the action. The default language isįor more information, see Specifying the Icon Image Used by an Action.ĭouble-click Reload Actions in the Desktop_Tools application group.Ĭreate an action file for the action. System-wide icons: /etc/dt/appconfig/icons/ language. If you want the action icon to have a unique image, create the iconsįor the action. Many of the action fields are covered in this chapter. Of the required or optional fields for this type of action. See the previous section, Configuration Files for Actions.Ĭreate the action definition using the syntax: ACTION action_name Open an existing database file or create a new one. You should not use this directory.įor information on modifying the actions/data types search path, see Setting the Value of a Search Path. System-wide actions- /etc/dt/appconfig/types/ languageīuilt-in actions- /usr/dt/appconfig/types/ language. Personal actions- HomeDirectory /.dt/types The files must be located on the database (actions and data The files must use the naming convention name.
Configuration Files for ActionsĬonfiguration files containing action definitions must meet these requirements: Creating an Action Manually: General StepsĬreate a configuration file for an action definition. TT_MSG (ToolTalk Message) ActionsĪ ToolTalk message. Other map actions must be created manually. This lets the user start Icon Editorīy selecting a bitmap or pixmap file in File Manager and then choosing OpenĬreate Action provides limited mapping for Open and Print actions. The database also includes an Open action, restricted in the definition toīitmap and pixmap files (by the ARG_TYPE field), Mapping provides the ability to specify alternative names for actions.įor example, a built-in command action named IconEditor starts Icon Editor. Than directly specifying a command or ToolTalk message
#Figure 1 action strings password
User (for example, to prompt for the root password and then run as root).Ī map action is an action that is ``mapped'' to another action rather On a system other than the one containing the action definition.Ĭhange of user-the ability to run the action as a different Multiple-file arguments with a different prompt for each argument.Īction invocation-the ability of actions to invoke otherĪrgument-count dependent behavior-the ability to createĪn action that has very different behaviors for different numbers of fileĪ remote execution host-the ability to run an application The action manually for example, you must create a COMMAND However, there may be some situations where you must create The Create Action tool can be used to create the most common types ofĬommand actions. The command to be executed (the EXEC_STRING). COMMAND ActionsĮxecutes a command that starts an application or utility, runs a shell script, All TT_MSG actions must be created manually.įor more information, see Limitations of Create Action. The Create Action tool is designed to create certain types of COMMAND and MAP actions. įor information about using Create Action, see Chapter 11, Creating Actions and Data Types Using Create Action.įor reference information about action definitions, see the Using Variables in Action and Data Type DefinitionsĬreating Actions for ToolTalk Applicationsįor an introduction to actions, see Chapter 10, Introduction to Actions and Data Types. Windowing Support and Terminal Emulators for COMMAND ActionsĬreating Actions that Run Applications on Remote Systems
Reasons You Must Create an Action ManuallyĬreating an Action Manually: General Stepsīuilding the Execution String for a COMMAND Action
#Figure 1 action strings how to
ThisĬhapter describes how to manually create action definitions.
Using the Create Action desktop applicationĬreating an action manually requires you to edit a database file.
0 kommentar(er)
