[mailto:xemacs-patches-bounces＠xemacs.org] On Behalf Of
Stephen J. Turnbull
Sent: Wednesday, February 23, 2005 3:12 AM
To: Ben Wing
Cc: 'David Kastrup'; xemacs-patches(a)xemacs.org
Subject: Re: [R21.4] [COMMIT] Update glyph documentation
>>>>> "Ben" == Ben Wing <ben(a)666.com> writes:
>> Yeah, I noticed that. I've been planning to take a look at
Ben> `make-glyph' returns a glyph object, and to me, the docs do
Ben> say that:
Ben> "Create a new glyph of type TYPE.
I would write something like this:
"Return a new glyph object, which describes a single
A glyph object contains an image specification and several
other display properties. See [the relevant accessors and
mutators, with mention of the type of each property].
If non-nil, optional argument SPEC-LIST should an image
specification. The most common image specification is the
name of an image file. The default is nil, in which case you
must specify the image using set-glyph-image'.
If non-nil, optional argument TYPE should be one of the
symbols `buffer', `mouse-pointer', or `icon' specifying the
context in which the glyph will be used. The default is
`buffer'. `mouse-pointer' and `icon' should only be used by
the XEmacs initialization code.
An image specification may be a single image instantiator, a
list of instantiators which are tried in order, or a complex
mapping from display locales to instantiators. See
`canonicalize-spec' for a description of the various formats.
An image instantiator is one of the following: [...]."
I'm not entirely happy with that, but I think it partly
addresses David's concern.
Institute of Policy and Planning Sciences
University of Tsukuba Tennodai 1-1-1
Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.