Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!agate!ucbvax!ucdavis!csusac!unify!openlook!openlook-request
From: smarks@Eng.Sun.COM (Stuart Marks)
Newsgroups: comp.windows.open-look
Subject: Re: Misc Openwindows 2.0 Questions
Message-ID: <ot5ud1y@openlook.Unify.Com>
Date: 26 Mar 91 21:35:20 GMT
Lines: 57


There are a bunch of different problems being intermixed here, so I'll try
to separate them.  There are indeed some problems with OpenWindows, but
not all bad behavior is caused by them.

    => Gee - I dont understand how you folks who have gotten the client
    => software from MIT X11R4 got some of it to work.  When I try to run
    => the makes there are missing libraries, header files, etc.  

This is probably because we don't ship the Athena widget set (libXaw) with
OpenWindows.  The Athena widgets are supported by MIT, and your best bet
is to use the X11R4 versions.

    => When I try
    => to run xman I get streams of msgs about widget problems 

Grumble.  This is caused by what some people (including me) consider to be
a misfeature.  When we were going to ship OpenWindows 2.0, we took the
latest version of Xt from MIT (up to patch level 9, I think), and compiled
and shipped it.  Unfortunately, the next patch changed the Xt revision
number.  So, if you compiled something using a recent patch of X11R4, and
ran it with OpenWindows, you'd get a bunch of error messages complaining
about a version mismatch.  You can probably replace the OpenWindows
version of libXt with the X11R4 versions.

    => and a window
    => which has only one button highlighted - the quit button.  When I tried
    => xpostit I got similar behaviour.

This is probably because the programs in question can't find their
app-defaults files.  Make sure that app-defaults files are installed
properly in /usr/lib/X11/app-defaults, or set up the XFILESEARCHPATH
environment variable so that the programs can find them.  If, for example,
you've installed programs in /usr/local (and their app-defaults files in
/usr/local/lib/app-defaults), you should set up your XFILESEARCHPATH
environment variable to contain

	/usr/local/lib/%T/%N%S

For an explanation of the %-sequences, see p. 860 of Asente & Swick, "The
X Window System Toolkit".

    Further, a number of the games, like Xtrek, refuse to accept keyboard
    input.  Mouse button input works just fine.

This is a bug in xtrek.  Programs need to set the input "hints" in order to
work properly under many window managers, and xtrek doesn't do this.  Some
popular window managers (such as twm) typically leave the focus in
PointerRoot mode, so applications like xtrek seem to "work".  However, if
you run them under other window managers (like olwm or mwm, the Motif
window manager), they will have problems accepting the input focus.

s'marks

Stuart W. Marks			ARPA: smarks@eng.sun.com
Windows & Graphics Software	UUCP: sun!smarks
Sun Microsystems, Inc.