Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hpcvlx!gabe
From: gabe@hpcvlx.HP.COM (Gabe Begeddov)
Newsgroups: comp.windows.x
Subject: Re: Using XtAddConverter with XtGetApplicationContext ?
Message-ID: <100920103@hpcvlx.HP.COM>
Date: 22 Aug 89 17:09:27 GMT
References: <242@auto-trol.UUCP>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 18


	/ hpcvlx:comp.windows.x / marbru@auto-trol.UUCP (Martin Brunecky) /  9:46 am  Aug 21, 1989 /

	How to use an explicit application_context along with XtAddConverter ???

	Since we are trying to "finalize" our widget set, I would wellcome any
	suggestions how to approach the scenario above. May be the R4 Intrinsics
	do something about it ????

The problem you describe was addressed in the patches (patch 9 ?) for R3. The 
approach used was that any converters added/overriden to the "default"
app_context are also added/override to all other existing and future
app_contexts.

The R4 intrinsics will most likely include some additional capabilities in the
area of converters. Two of the areas being addressed are lack of per-display
information in the converters (for errors and freeing of stale data) and lack
of control over whether results are cached or not.