Xref: utzoo comp.windows.x.motif:654 comp.windows.x:26572
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rutgers!uwm.edu!bionet!agate!linus!linus!mbunix!daf
From: daf@mbunix.mitre.org (Dennis Franciskovich)
Newsgroups: comp.windows.x.motif,comp.windows.x
Subject: Resource specs (was Re: XmLabel question)
Summary: Is space allowed?
Message-ID: <119117@linus.mitre.org>
Date: 5 Sep 90 13:29:10 GMT
References: <118526@linus.mitre.org> <141712@sun.Eng.Sun.COM> <6265@adobe.UUCP>
Sender: usenet@linus.mitre.org
Followup-To: comp.windows.x.motif
Organization: SEPTIC FOOLS
Lines: 25

(I've now crossposted to comp.windows.x; please followup appropriately)

asente@adobe.com (Paul Asente) writes:
| argv@turnpike.Eng.Sun.COM (Dan Heller) writes:
| >
| >    *label string.labelString: another label
| 
| [...] This bit, however, isn't quite right.  Space is not a legal character
| in a resource specification, so the above line is not a valid resource
| specification.

According to the man page for X(1), you are correct, but I have been using
spaces inside resource specs and have not (yet) had any problems.
I've been doing things like:

	XmCreateLabel(parent, "label string", NULL, 0);

and then in the resource file:

	*label string.x:  100
	*label string.y:  200

and it seems to work ok.
--
Dennis