Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!paperboy!osf!dbrooks
From: dbrooks@osf.osf.org (David Brooks)
Newsgroups: comp.windows.x.motif
Subject: Re: Setting Widget Resources
Message-ID: <21258@paperboy.OSF.ORG>
Date: 22 Apr 91 03:16:11 GMT
References: <1991Apr18.003956.6310@latcs2.lat.oz.au> <9104212157.AA25272@bellcore.bellcore.com>
Sender: news@OSF.ORG
Reply-To: dbrooks@osf.org (David Brooks)
Distribution: inet
Organization: Open Software Foundation
Lines: 28

aw@BAE.BELLCORE.COM (Andrew Wason) writes:
>> I am trying to do the following in a resource file:
>> 
>>         app*widget.bottomAttachment: ATTACH_WIDGET
>>         app*widget.bottomWidget: bottom_widget
>
>In this case the resource type is XtRWidget and no String to Widget
>converter has been registered.
>
>Wcl (available on export) provides the converter you need.

You can also do this with UIL.

UIL (and presumably Wcl) can convert a widget name to a widget because the
interface is created in one swell foop.  They have enough information
sitting around to (almost) guarantee a successful conversion.

However, a more general mechanism like a resource specification can't make
these guarantees.  At the time the resource is converted, bottom_widget
will probably not exist.  If it does exist, there may be two widgets of the
same name in the app-context.  Given a conversion that's likely to fail
most of the time, I think the choice was not to provide it at all.

A clear case of advantage to using UIL :-)
-- 
David Brooks				dbrooks@osf.org
Systems Engineering, OSF		uunet!osf.org!dbrooks
Donnie Wahlberg is brought to you by three billion years of evolution.