Question on QKGO in combination with auto=

Jonbickel@aol.com Jonbickel@aol.com
Tue, 24 Sep 2002 12:34:47 -0400


As I noted in my original mail, that does not appear to work in 
the UNIX implementation (HP-UX).  
Using the "quick auto=<screen name>.qkc" construct demonstrably
causes PHouse to ignore both the QKGO environment variable, and
the qkgo.qkg in the working directory (procloc) and fall back on
the default configuration.

Jon



In a message dated Tue, 24 Sep 2002 10:31:01 AM Eastern Standard Time, ntietz@MCARE.MED.UMICH.EDU writes:

> 
> 
> 
> You could set your default qkgo file to be the one that you have modified.
> FILE QKGO=MYQKGO.QKG
> QUICK AUTO=<screen object>
> 
> I hope that helps!
> nt
> 
> -----Original Message-----
> From: Jonbickel@aol.com [mailto:Jonbickel@aol.com]
> Sent: Tuesday, September 24, 2002 11:29 AM
> To: ntietz@MCARE.MED.UMICH.EDU; powerh-l@lists.swau.edu
> Cc: jonbickel@aol.com
> Subject: Re: Question on QKGO in combination with auto=
> 
> 
> 
> Currently, the situation is not conducive to using a main driver menu for
> all QUICK screens.  Given that, using the auto=<filename>.qkg (with first
> screen specified) would mean that I would need one .qkg for each .qkc.  That
> would be an unacceptable maintenance load.  
> 
> Jon Bickel
> 
> 
> 
> In a message dated Tue, 24 Sep 2002 8:12:32 AM Eastern Standard Time,
> ntietz@MCARE.MED.UMICH.EDU writes:
> 
> > 
> > 
> > Why bother with trying to change the default qkgo settings when it is so
> > easy to create your own personal qkgo file that just runs that one screen?
> > :setqkgo
> > 
> > :quick auto=<qkgo file>
> > 
> > Nancy
> > 
> > -----Original Message-----
> > From: Jonbickel@aol.com [mailto:Jonbickel@aol.com]
> > Sent: Tuesday, September 24, 2002 8:55 AM
> > To: powerh-l@lists.swau.edu
> > Cc: jonbickel@aol.com
> > Subject: Question on QKGO in combination with auto=
> > 
> > 
> > 
> > Good Morning all!
> > (Long time reader, first time writer...)
> > 
> > The setup that I'm currently working on is PowerHouse 8.23.D2 on HP-UX
> 11.0.
> > 
> > 
> > My question is this - Where does QUICK draw the QKGO parameters (e.g.
> screen
> > level limit) from when a screen is started with the command "quick
> > auto=<screen name>.qkc" ? 
> > 
> > I can successfully use the $QKGO environment variable and/or the qkgo.qkg
> in
> > the procloc directory (or "quick auto=<qkgo file>.qkg" with/without a
> start
> > screen in the qkgo) to apply custom parameters to a QUICK session, but
> > starting the session with the "auto=<screen name>.qkc" appears to cause
> > QUICK to ignore the $QKGO/qkgo.qkg and fall back on the default values.
> > Where are these values drawn from, and is it possible/advisable to change
> > these directly?
> > 
> > Thanks to all,
> > 
> > Jon Bickel 
> > 
> > 
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> > Mailing list: powerh-l@lists.swau.edu
> > Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
> > Unsubscribe: "unsubscribe" in message body to
> > powerh-l-request@lists.swau.edu
> > http://lists.swau.edu/mailman/listinfo/powerh-l
> > This list is closed, thus to post to the list you must be 
> a 
> > subscriber.