Re: Defaults problem

[bob at fla dot fujitsu dot com (Bob Carragher)]

Bob-> Hmmm, never thought about it before.  If you were working on a
Bob-> new game, and the file was in your working directory, then it
Bob-> would be a pain to have it start in ~/.xconq every time, but in
Bob-> the more common case of a player restarting a saved game,
Bob-> showing the saved game makes more sense.  One could perhaps
Bob-> be extra-flavorful by offering .xconq if a save.xcq is present,
Bob-> and the working dir otherwise, but that I can people becoming
Bob-> superstitious because they can't figure out Xconq asks for
Bob-> different directories sometimes.

This occurred to me as well as I was composing my message to
the list.  I have a couple of questions regarding this issue.

     1.  Is it possible to specify a "save" file other
         than save.xcq?  One could imagine a command-line
         option like "-S" which loads up a saved game and
         bypasses the first couple of dialog boxes (i.e.
         the "new" vs "saved" game dialog box, and the
         dialog box which does a file search).  So, you
         might invoke xconq as

              xconq -S ./my_saved_game.xconq

     2.  Could extra resources be added to the game?  I'm
         thinking of maybe "xconq*savedGameName" and perhaps
         "xconq*savedGameDirList."  The former is self-
         explanatory; the latter might be a colon-separated
         list of directories to search for "savedGameName,"
         and might be ".:~/xconq" by default.  (Of course,
         then you might need "xconq*loadGameDefaultDir" or
         somesuch for the dialog box that performs file
         searching ....)

				Bob