Mike Kupfer writes:
Stephen J. Turnbull wrote:
> Mike Kupfer writes:
> >> With:data, the specifier has tty and stream clauses
that it lacks when
> >> created with :file. Is that to be expected?
> "Yes, at least sometimes." For example, if the :data
were simply a
> string, then it would be displayable in all those cases, and the
> specifier code would try to instantiate. I suppose the media type
> guessing code is invoked separately for each domain, maybe different
> code is involved.
logo-data
"/* XPM */
[...]
};
"
;; Create glyph using :data:
(make-glyph `[xpm :data ,logo-data])
#<glyph (buffer) #<image-specifier global=
(((x) . [xpm :color-symbols ...
:data "/* XPM */ ..."])
((tty) . [xpm :color-symbols ... :data "/* XPM */ ..."])
((stream) . [xpm :color-symbols ... :data "/* XPM */ ..."]))
fallback=((nil . [nothing])) 0xd0f>0x17b>
In both cases, the specifier includes the format (xpm). So there
shouldn't be any need for XEmacs to guess the format, should there?
I guess not. I don't know why this happens. You can dig into the
specifier code if you like. It will be a couple of weeks before I
can, though.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta