Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!mcsun!ukc!harrier.ukc.ac.uk!rlh2 From: rlh2@ukc.ac.uk (R.L.Hesketh) Newsgroups: comp.windows.x Subject: Re: Using Xt to create an override shell Message-ID: <4379@harrier.ukc.ac.uk> Date: 12 Apr 90 17:45:18 GMT References: <134170@sun.Eng.Sun.COM> <9004111939.AA01109@expo.lcs.mit.edu> <134360@sun.Eng.Sun.COM> Reply-To: rlh2@ukc.ac.uk (Richard Hesketh) Organization: Computing Lab, University of Kent at Canterbury, UK. Lines: 38 In article <134360@sun.Eng.Sun.COM> argv@sun.UUCP (Dan Heller) writes: >Now, to have my application consist entirely of a single override shell >with a plain core widget underneith it, I simply ignore the toplevel >shell returned by XtInitialize() and just use the new override shell as >my toplevel shell. You don't have to do this with R4. Why not use .. XtToolkitInitialize(); dpy = XtOpenDisplay(XtCreateApplicationContext(), NULL, "xlock", "XLock", options, XtNumber(options), &argc, argv); shell = XtVaAppCreateShell("xlock", "XLock", overrideShellWidgetClass, dpy, XtNwidth, 100, ...., NULL); ?? (I'll send you a full test program if you want). I assume the "App" part of the Xt{Va}AppCreateShell() comes from the "per display data" of the passed display pointer (?). >* There is no XtVa (varargs) version for XtAppCreateShell(). Hmm.. yes there is... XtVaAppCreateShell() in Xt/VarCreate.c >* There doesn't seem to be any way to specify shell-specific > resources via XtInitialize(). Yes, you can use the "options" > parameter, but this isn't quite the same thing as the Arg lists > used in the other XtCreateWidget-style calls. Why not have the > "args" and "nargs" parameters to XtInitialize (et al.) routines? If you decide to do things this way then why not use Xt{Va}AppInitialize() ? XtInitialize() is old hat 8-). Richard Hesketh : @nsfnet-relay.ac.uk:rlh2@ukc.ac.uk : rlh2@ukc.ac.uk ..!mcvax!ukc!rlh2 --- Computing Lab., University of Kent at Canterbury, Canterbury, Kent, CT2 7NF, United Kingdom. Tel: +44 227 764000 ext 3682/7620