Path: utzoo!attcan!uunet!husc6!uwvax!rutgers!ucsd!ucsdhub!hp-sdd!hplabs!hpda!hpcuhb!hp-sde!hpfcdc!hpfclp!diamant
From: diamant@hpfclp.SDE.HP.COM (John Diamant)
Newsgroups: comp.windows.x
Subject: Re: Chicken or Egg Xtk Problem
Message-ID: <9740047@hpfclp.SDE.HP.COM>
Date: 5 Aug 88 20:55:45 GMT
References: <2926@nicmad.UUCP>
Organization: HP SDE, Fort Collins, CO
Lines: 17

> Regarding calling XtMoveWidget vs. doing an XtSetValues:
> 
> The "proper" way for client (i.e.non-parent) code to get a widget moved is
> always XtSetValues.  There are some bugs in early releases that keep this
> from working with shells; it's fixed in the next release (sorry).

Sorry for the misinformation earlier, and thanks for the clarification.  As
soon as XtSetValues works for the realized shell, I'll be perfectly happy
to switch to using it.  By the way, I started using XtMoveWidget because
I looked at the R2 xmh code, and that's what it did (probably because of
the bug).


John Diamant
Software Development Environments
Hewlett-Packard Co.		ARPA Internet: diamant@hpfclp.sde.hp.com
Fort Collins, CO		UUCP:  {hplabs,hpfcla}!hpfclp!diamant