Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Does anyone have a fix for R4/PL1 XGetDefault?
Message-ID: <47970@lll-winken.LLNL.GOV>
Date: 9 Feb 90 20:59:50 GMT
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 20


  Under R4, XGetDefault doesn't work 100%.  If you attempt to do an
XGetDefault(dpy, prog, "foo.bar"), XGetDefault won't break the string
"foo.bar" up into separate ``Quarks'' and therefore won't match the
desired resource.  I've got a bug report in to MIT, but I don't know when
we'll see a fix from them.

  I know of two programs which are affected by this bug: xgraph and awm.
There are probably more.  I'm not worried about xgraph because it's
incorrect for it to use XGetDefault.  But awm really doesn't have a
choice.  It uses XGetDefault to go for it's ``<prog>*wm_option.foo''
resources.

  Normally I'd just wait till MIT came out with the official fix, but I
have users banging on me about awm being broken.  Also, normally I'd fix
the problem myself if I needed to, but I don't understand the code or
conventions in this area.  Please email patches to me and I will post the
one that works correctly and seems cleanest.  Thanks for your help.

Casey