Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!apple!bloom-beacon!EXPO.LCS.MIT.EDU!kit From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) Newsgroups: comp.windows.x Subject: Re: Visuals, colors, resource db Message-ID: <8908281600.AA21878@expo.lcs.mit.edu> Date: 28 Aug 89 16:00:41 GMT References: Organization: The Internet Lines: 40 > 1. I tried XFlush and XSync to no avail... It seems to me that I must > force the root window to be displayed before I can use these calls. > What is there in XtMainLoop that does this? XtNextEvent? XtRealizeWidget(widget); XFlush(XtDisplay(widget)); [stuff] XtMainLoop(); This type of thing doesn't work? > 2. On the other hand, I need the window attr's in order to know which > Visual and Colormap where assigned to it. Thus, these 2 prblms are > related. I will try to write my own realize proc for the root widget. > Any other suggestions? In R3 the visual is always the default visual of the screen, and unless you explicitly change the colormap it is also the default colormap of screen. Also, once you have realized a widget the window ID should be valid, and you can get the attributes of it. Whether or not it is visable on the screen yet. > >How about using an app-defaults file instead? This way the toolkit > >will merge your resources in for you. > Yes, I thought of that. But I have at least 2 resource files which > must be loaded; one of them is (human) language dependent. Don't spend too long on this one, as we are come up with a solution to the human language problem for R4. Chris D. Peterson MIT X Consortium Net: kit@expo.lcs.mit.edu Phone: (617) 253 - 9608 Address: MIT - Room NE43-213