Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: oj@saber.COM
Newsgroups: comp.windows.x
Subject: Re: Is this a problem with Saber or XtGetApplicationResources.
Message-ID: <9103271546.AA19856@shiva>
Date: 27 Mar 91 15:46:59 GMT
Sender: oj@saber.com
Organization: Saber Software, Inc.
Lines: 34

In message <14373@life.ai.mit.edu> Sundar Narasimhan asked:
   ... I have a program that
   when compiled and executed behaves differently than when it is executed
   under Saber....

   I have a program that [uses XtAppInitialize and 
   XtGetApplicationResources together with an XrmOptionDescRec array
   and an XtResource array.]...

   Now, the program compiles and executes fine. But I'd like to run this
   under Saber. Unfortunately, when I try to do this, XtGetApplicationResources
   doesn't seem to notice the passed in argc, argv when I do this.

What's happening here is that Saber-C provides an argv[0] value of
"a.out" when you run the program (just like dbx).  This baffles 
the X resource manager.

To get around this, issue the following Saber-C command before
issuing the Saber-C run command (supposing your
program's executable file is ordinarily named "mygraph"):

      -> setopt program_name mygraph

If you do this the XtGetApplicationResources call should start to 
recognize the stuff put into the resource list via your XrmOptionDescRec.

(When I'm using Saber-C to hack Xt stuff, I put the following line
 in my $HOME/.saberinit file in case I forget):

     setopt program_name test

Ollie Jones       Saber Software, Inc.       oj@saber.com
Project Leader    185 Alewife Brook Parkway  uunet!saber.com!oj
+1(617)876-7636   Cambridge, MA 02138-9887   fax +1(617)547-9011