Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!acorn!ixi!ixi!pd From: pd@x.co.uk (Paul Davey) Newsgroups: comp.windows.x Subject: Re: Design problem in XtVaGetApplicationResources Message-ID: Date: 19 Mar 91 13:11:02 GMT References: <3108@laura.UUCP> Sender: paul@x.co.uk (Paul Davey) Organization: IXI Ltd. Lines: 31 In-Reply-To: klute@tommy.informatik.uni-dortmund.de's message of 18 Mar 91 16:45:46 GMT >>>>> On 18 Mar 91 16:45:46 GMT, klute@tommy.informatik.uni-dortmund.de (Rainer Klute) said: -> As every X toolkit programmer knows Xt offers a nice way to retrieve -> application resources: XtVaGetApplicationResources. The "normal" way to use -> this function is something like this: ... -> However, this stuff will only work if you already have a connection to an X -> server, because you have to pass a widget (hence a display connection) as -> parameter to XtVaGetApplicationResources. Now, what can I do if I don't have -> one? Before opening any display connection and creating any widgets my -> application *first* wants to read its resources - using -> XtVaGetApplicationResources - and only then open a display connection *upon the -> values of the retrieved resources*. ... -> Comments anyone? How can you check *all* your application resources when they may be held in the RESOURCE_MANAGER property on the root window? You have to open the display first. You`ve still got $DISPLAY and -display to tailor the server connection with. -- Regards, pd@x.co.uk IXI Limited Paul Davey pd@ixi.uucp 62-74 Burleigh St. ...!uunet!ixi!pd Cambridge U.K. "These are interesting times" +44 223 462 131 CB1 1OJ USA: 1 800 XDESK 57