Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!lll-winken!lll-crg.llnl.gov!hbrand
From: hbrand@lll-crg.llnl.gov (Hal Brand)
Newsgroups: comp.windows.x
Subject: VMS DECWindows Problem with Window Picking ala xwd
Summary: xwd window picking code in dsimple.c fails with VMS server.
Keywords: DECWindows, VMS, xwd
Message-ID: <88647@lll-winken.LLNL.GOV>
Date: 3 Jan 91 04:59:45 GMT
Sender: usenet@lll-winken.LLNL.GOV
Organization: Lawrence Livermore National Laboratory
Lines: 32
Nntp-Posting-Host: lll-crg.llnl.gov

I have tried using the function Select_Window found in
mit/clients/xwd/dsimple.c and this fails when talking to the DEC VMS
monochrome server on a VAXStation 3100 but works just fine with
non-VMS servers. The problem seems to be related to two (2) full
screen size windows (created by ???) that are situated in the window
hierarchy between the root window and all standard application
windows, i.e. the window hierarchy looks roughly like:

	<root window>
	  <Funny full screen window #1>
	    <Funny full screen window #2>
	      <Normal application hierarchy top window>
[Note: Indentation represents parent-child relationship.]
For comparison, on other servers, i.e. my VAX/Ultrix server, I get:
	<root window>
	  <Normal application hierarchy top window>

I have found that if I substitute the window ID of
<Funny full screen window #2> for the root window ID in the call to
XGrabPointer, then Select_Window() works with the VMS server just fine.
However, this is a REAL HACK!

So... Two questions (in order of importance to me):

1) What is the right way to code Select_Window() to work in both environments?

2) Why (oh WHY!) is VMS DECWindows doing this AND who (what application) is
    responsible - and what is gained??

						Hal Brand
						LLNL
						hbrand@lll-crg.llnl.gov