Path: utzoo!attcan!uunet!husc6!bbn!oberon!sdcrdcf!hplabs!sr -unixKhulc6!bloom-beacon!ardent.UUCP!jkh
From: sr@hplabs.UUCP
Newsgroups: comp.windows.x
Subject: resources in toolkit
Message-ID: <8805122159.AA07168@BigMomithedent.com>
Date: 12 May 88 21:59:48 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 50
urom: jkh@ardent.UUCP (Jordan Hubbard)

Ever since I installed Jef Poskanser's patches for a string->pixmap
converter, I've been trying to figure out how to get icon pixmaps to
be displayed properly. An entry of the form:

xterm*iconPixmap: /foo/bar/somepixmapfile

works fine. However, this sets it for *all* xterms, not just the ones
with an application name of "xterm". I was under the impression that
you could specify an alternate application name with -n (and an alternate
window manager name with -T). Shouldn't it be possible to say something
like:

(~/.Xdefaults)
xterm*iconPixmap: /stuff/generic-xterm-icon
goofy*iconPixmap: /stuff/goofy-machine-icon

(shell)
% xterm -g 80x24+0+0
% xterm -n goofy -e rlogin goofy

And have two different pixmaps displayed? It would be all well and fine
if the toolkit (or xterm at least) supported a -iconPixmap flag so you
could specify something in the absense of a resource, but that's not
the case. I notice that -n in xterm is also looked for as the resource
"iconName"... Is that right? I suppose if -T sets the application
name, fine, but....
How *does* one select a potentially different icon pixmap for
each invocation of xterm?

Also, am I completely confused about the resource manager or shouldn't
it be possible to say:

Xterm*iconPixmap: ...

It doesn't work for me.. Perhaps I just don't understand the name/class
concept well enough. q?

And while we're on this subject, I guess I'll ask how exactly does
the toolkit handle command line options? I notice that XtInititialize()
is interested in argc, argv and a list of client-specific options
which it seems to kindly parse and initialize for you, but wouldn't
it be logical for the toolkit to have its own set of "standard"
arguments that would be used to init the top level widget? I notice
quite a few things that are searched for in the resource database, but
there doesn't see to be any way of specifying them on the command line.
Que Pasa?


				Jordan Hubbard
				jkh@violet.berkeley.edu