/******************************************************************************* * * * prefFile.c -- Nirvana utilities for providing application preferences files * * * * Copyright (c) 1991 Universities Research Association, Inc. * * All rights reserved. * * * * This material resulted from work developed under a Government Contract and * * is subject to the following license: The Government retains a paid-up, * * nonexclusive, irrevocable worldwide license to reproduce, prepare derivative * * works, perform publicly and display publicly by or for the Government, * * including the right to distribute to other Government contractors. Neither * * the United States nor the United States Department of Energy, nor any of * * their employees, makes any warrenty, express or implied, or assumes any * * legal liability or responsibility for the accuracy, completeness, or * * usefulness of any information, apparatus, product, or process disclosed, or * * represents that its use would not infringe privately owned rights. * * * * Fermilab Nirvana GUI Library * * June 3, 1993 * * * * Written by Mark Edel * * * *******************************************************************************/ static char SCCSID[] = "@(#)prefFile.c 1.11 9/1/94"; #include #include #ifdef VMS #include "VMSparam.h" #else #include #endif #include #include "prefFile.h" #define N_BOOLEAN_STRINGS 13 char *TrueStrings[N_BOOLEAN_STRINGS] = {"True", "true", "TRUE", "T", "t", "Yes", "yes", "YES", "y", "Y", "on", "On", "ON"}; char *FalseStrings[N_BOOLEAN_STRINGS] = {"False", "false", "FALSE", "F", "f", "No", "no", "NO", "n", "N", "off", "Off", "OFF"}; static int stringToPref(char *string, PrefDescripRec *rsrcDescrip); static char *removeWhiteSpace(char *string); /* ** Preferences File ** ** An application maintains a preferences file so that users can ** quickly save and restore program options from within a program, ** without being forced to learn the X resource mechanism. ** ** Preference files are the same format as X resource files, and ** are read using the X resource file reader. X-savvy users are allowed ** to move resources out of a preferences file to their X resource ** files. They would do so if they wanted to attach server-specific ** preferences (such as fonts and colors) to different X servers, or to ** combine additional preferences served only by X resources with those ** provided by the program's menus. */ /* ** Preference description table ** ** A preference description table contains the information necessary ** to read preference resources and store their values in a data ** structure. The table can, so far, describe four types ** of values (this will probably be expanded in the future to include ** more types): ints, booleans, enumerations, and strings. Each entry ** includes the name and class for saving and restoring the parameter ** in X database format, the data type, a default value in the form of ** a character string, and the address where the parameter value is ** be stored. Strings and enumerations take an additional argument. ** For strings, it is the maximum length string that can safely be ** stored. For enums, it is an array of string pointers to the names ** of each of its possible values. The last value in a preference ** record is a flag for determining whether the value should be written ** to the save file by SavePreferences. */ /* ** CreatePreferencesDatabase ** ** Process a preferences file and the command line options pertaining to ** the X resources used to set those preferences. Create an X database ** of the results. The reason for this odd set of functionality is ** to process command line options before XtDisplayInitialize reads them ** into the application database that the toolkit attaches to the display. ** This allows command line arguments to properly override values specified ** in the preferences file. ** ** fileName Name only of the preferences file to be found ** in the user's home directory ** appName Application name to use in reading the preference ** resources ** opTable Xrm command line option table for the resources ** used in the preferences file ONLY. Command line ** options for other X resources should be processed ** by XtDisplayInitialize. ** nOptions Number of items in opTable ** argcInOut Address of argument count. This will be altered ** to remove the command line options that are ** recognized in the option table. ** argvInOut Argument vector. Will be altered as argcInOut. */ XrmDatabase CreatePreferencesDatabase(char *fileName, char *appName, XrmOptionDescList opTable, int nOptions, unsigned int *argcInOut, char **argvInOut) { char fullName[MAXPATHLEN]; XrmDatabase db; int argcCopy; char **argvCopy; static XrmOptionDescRec xrmOnlyTable[] = {{"-xrm", NULL, XrmoptionResArg, (caddr_t)NULL}}; /* read the preferences file into an X database. On failure prefDB will be NULL. */ #ifdef VMS sprintf(fullName, "%s%s", "SYS$LOGIN:", fileName); #else sprintf(fullName, "%s/%s", getenv("HOME"), fileName); #endif /*VMS*/ db = XrmGetFileDatabase(fullName); /* parse the command line, storing results in the preferences database */ XrmParseCommand(&db, opTable, nOptions, appName, (int *)argcInOut, argvInOut); /* process -xrm (resource setting by resource name) arguments so those pertaining to preference resources will be included in the database. Don't remove -xrm arguments from the argument vector, however, so XtDisplayInitialize can still read the non-preference resources */ argvCopy = (char**)XtMalloc(sizeof(char *) * *argcInOut); memcpy(argvCopy, argvInOut, sizeof(char *) * *argcInOut); argcCopy = *argcInOut; XrmParseCommand(&db, xrmOnlyTable, XtNumber(xrmOnlyTable), appName, &argcCopy, argvCopy); XtFree((char *)argvCopy); return db; } /* ** RestorePreferences ** ** Fill in preferences data from two X databases, values in prefDB taking ** precidence over those in appDB. */ void RestorePreferences(XrmDatabase prefDB, XrmDatabase appDB, char *appName, char *appClass, PrefDescripRec *rsrcDescrip, int nRsrc) { char rsrcName[256], rsrcClass[256], *valueString, *type; XrmValue rsrcValue; int i; /* read each resource, trying first the preferences file database, then the application database, then the default value if neither are found */ for (i=0; idataType) { case PREF_INT: cleanStr = removeWhiteSpace(string); *(int *)rsrcDescrip->valueAddr = strtol(cleanStr, &endPtr, 10); if (strlen(cleanStr) == 0) { /* String is empty */ *(int *)rsrcDescrip->valueAddr = 0; XtFree(cleanStr); return False; } else if (*endPtr != '\0') { /* Whole string not parsed */ *(int *)rsrcDescrip->valueAddr = 0; XtFree(cleanStr); return False; } XtFree(cleanStr); return True; case PREF_BOOLEAN: cleanStr = removeWhiteSpace(string); for (i=0; ivalueAddr = True; XtFree(cleanStr); return True; } if (!strcmp(FalseStrings[i], cleanStr)) { *(int *)rsrcDescrip->valueAddr = False; XtFree(cleanStr); return True; } } XtFree(cleanStr); *(int *)rsrcDescrip->valueAddr = False; return False; case PREF_ENUM: cleanStr = removeWhiteSpace(string); enumStrings = (char **)rsrcDescrip->arg; for (i=0; enumStrings[i]!=NULL; i++) { if (!strcmp(enumStrings[i], cleanStr)) { *(int *)rsrcDescrip->valueAddr = i; XtFree(cleanStr); return True; } } XtFree(cleanStr); *(int *)rsrcDescrip->valueAddr = 0; return False; case PREF_STRING: strncpy(rsrcDescrip->valueAddr, string, (int)rsrcDescrip->arg); return strlen(string) < (int)rsrcDescrip->arg; } return False; } /* ** Remove the white space (blanks and tabs) from a string and return ** the result in a newly allocated string as the function value */ static char *removeWhiteSpace(char *string) { char *outPtr, *outString; outPtr = outString = XtMalloc(strlen(string)+1); while (TRUE) { if (*string != ' ' && *string != '\t') *(outPtr++) = *(string++); else string++; if (*string == 0) { *outPtr = 0; return outString; } } } /******************* Implementation Note: Q: Why aren't you using the Xt type conversion services? A: 1) To create a save file, you also need to convert values back to text form, and there are no converters for that direction. 2) XtGetApplicationResources can only be used on the resource database created by the X toolkit at initialization time, and there is no way to intervene in the creation of that database or store new resources in it reliably after it is created. 3) The alternative, XtConvertAndStore is not adequately documented. The toolkit mauual does not explain why it overwrites its input value structure. 4) XtGetApplicationResources and XtConvertAndStore do not work well together because they use different storage strategies for certain data types. *******************/