App class resource descriptions

All of the following resources are only used if the Application programmer directly creates an App object. If they simply use the NhlOpen function, then these resources are not necessary.

One thing that is a little tricky about these resources is that they can be specified in the $(NCARG_USRRESFILE) and the $(NCARG_SYSRESFILE), but they will not affect anything if they are placed in the application specific resource file. This is simply because these resources are used to find those files, so they can't be specified in them.

This resource is used to indicate what directory the App object should look in for the User's application specific resource file.

Default: ./ (Current Working Directory)

This resource is used to indicate what directory the App object should look in for the System application specific resource file.

Default: <dynamic>
This resource defaults to the value of the $(NCARG_SYSAPPRES) environment variable.

This resource is used to specify a suffix for the Application specific resource files. It is useful to set this resource in the $(NCARG_USRRESFILE) and $(NCARG_SYSRESFILE), if an application programmer wants to provide more than one Application Specific Resource file. For example, if some of the end users do not have color monitors, then there could be two resource files. One, and another appname.color.res. Then the appFileSuffix resource can be specified to indicate which Application specific resource file to use.

Default: .res

This resource is only True for one App object at a time. If it is True in a given App object, then that App object is the one that will be used as the parent of any objects created with the parentid argument of NhlCreate set to NhlDEFAULT_APP or 0.

Default: <dynamic>
This resource defaults to True for the First App object created, otherwise it is False.

This resource specifies an array of names. Each one of these names dynamically becomes a valid resource for the App object. This is a very useful feature for developers of multi-user applications because configuration parameters for the application can become resources to the App object. Then, users of the application can configure the application using the same resource files that they use to configure the HLU portion of the application.

Default: NULL

Reference Manual Control Panel

NG4.1 Home, Index, Examples, Glossary, Feedback, Ref Contents, Ref WhereAmI?

$Revision: 1.10 $ $Date: 1998/08/19 01:09:13 $