Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!ico!auto-trol!marbru
From: marbru@auto-trol.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: Re: Form problem
Message-ID: <736@auto-trol.UUCP>
Date: 13 Feb 90 03:05:52 GMT
References: <BKILGORE.90Feb11220941@aiaia.nmsu.edu> <9002121640.AA10381@expo.lcs.mit.edu>
Reply-To: marbru@auto-trol.COM (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 32

In article <9002121640.AA10381@expo.lcs.mit.edu> kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) writes:
>
>> 	I am having a small problem with the form widget.  After I create a
>> ManagedChild on the form widget and try to move the widget by XtMoveWidget,
>> and then setting the XtSetValues with the new coordinates, upon
>
>Don't do that.
>

	I agree, BUT. The trouble is that R3 and R4 Intrinsics document
	does not distinguish between functionality designed for the
	application programmer, and functionality designed for a widget
	writer. Basically, R3/R4 Intrinsic document is for a widget
	writer. There is NO document for the poor user, besides the
	D Young's books (but his distinctions between user's calls and
	widget-writer's calls is also a little bit fuzzy).

	From my experience, X toolkit novices - for what ever reason -
	tend to use the most obscure Xt calls at first.

	So, for R5 or later, I would suggest to restructure the Intrinsics
	document so that it reflects audience:
	- a novice Xt user
	- an experienced Xt user ( several Xt calls fall into "use but bevare")
	- a widget writer


-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Martin Brunecky                   marbru@auto-trol.COM
(303) 252-2499                    {...}ncar!ico!auto-trol!marbru
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404