Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!infonode!ingr!b11!doyle From: doyle@b11.ingr.com (Doyle Davidson) Newsgroups: ingr.x,comp.windows.x Subject: Re: Multiple top level windows Keywords: X, Xt Message-ID: <1991May2.214350.22721@b11.ingr.com> Date: 2 May 91 21:43:50 GMT References: <1991May2.185712.11423@b11.ingr.com> Organization: Intergraph Corp. Huntsville, AL Lines: 36 In article <1991May2.185712.11423@b11.ingr.com>, davis@b11.ingr.com (Chris Davis) writes: > We have an application that creates multiple top-level windows. Oooohhh! :-) :-) > We would like to provide a command line argument(s) that allows the > user to specify x number of these windows. Each window may use a > different resource name in order to specify alternate resource values. > > Pre-processing the command line is an option, but we were curious if there > was an alternative. How about using "XrmoptionSkipArg" or "XrmoptionSkipLine" to specify them. This should make life much easier to parse. You will only be left with these args after Xt rips out what it wants. So the user says: prog ... -window red ... -window blue ... (XrmoptionSkipArg style) or proc ... -windows red blue green (XrmoptionSkipLine style) Although it seems to me that these two Xrm options are useless and really don't change the argc/argv that you get back. It you must get these values into the resource database, use the Xrm* functions to put in resources programmatically. Ask me for details if you care. Doyle x8666 ------------------------------------------------------------------- Doyle C. Davidson | Intergraph Corp. | Intergraph - Everywhere you look!! Third Party Software | 1 Madison Industrial Park | Huntsville, AL 35806 | These comments are... (205) 730-2000 | | X-clusively my own. ..!uunet!ingr!doyle | -------------------------------------------------------------------