🚀 go-pugleaf

In article <9105141520.AA20233@atlantis.coral.com>, don@atlantis.coral.com (Don Dewar) writes:
> Ok, uncle, I give.  I tried the following to be able to set resources
> for specfic epoch screens from my .Xresources file, which I load with
> xrdb.

Sigh. This isn't what the window name and class refer to. Resources
are loaded by the application name and class. The window name / class
default to the application name / class, but are primarily only for
the use of the window manager. The X resource information is loaded
only once, at startup time.

If you've applied patch 1 and 2, you should have a primitive available
called (get-default), which you could use to query the default values.
Again, because of the way X resources work, you'll get the value at
the time Epoch started, not the current value.

If you get really desperate, you can always just get the xrdb
informtion into a buffer and hack it directly.

On a related subject, Brian Kahn writes:
>I have had to give up on using the class and name from an attribute
>list to get what I want. [ ... ] My
>trouble is that WM_CLASS is of type string, but seems to be composed
>of two strings.  I have trouble setting these.

Yes, the WM_CLASS property consists of 2 strings, null seperated, the
name and class. If you want to set them inside Epoch, use a construct
like

(defvar xa-wm-class (intern-atom "WM_CLASS"))
(set-property xa-wm-class (list "Window name" "Window Class"))

You can examine the current value with (get-property xa-wm-class),
which should return a list of 2 strings. Note that a WM does not have
to notice changes to this property except upon an unmap / map of the X
window.

-- 
Alan M. Carroll          <-- Another casualty of applied metaphysics
Epoch Development Team   
Urbana Il.               "I hate shopping with the reality-impaired" - Susan