jlevy@arisia.Xerox.COM (Jacob Levy) (03/29/89)
When using multiple application contexts together with toolkits which register resource converters, I noted an annoying problem. I would get X Toolkit warnings about unregistered resource converters even though the resource converters were being registered properly with XtAddConverter. Delving into the Xt code, I discovered that XtAddConverter adds the converter to a table maintained for the default application context. Thus, the bottom line is - either XtAddConverter should take another argument saying to which application context to add the converter, or else you can use only the default application context and the purpose of having multiple (or even a single one, but your own instead of the default one) application contexts is defeated. On the same note, how does one get a hold of the default application context? Right now I am using the unpublished function _XtDefaultAppContext() to get a handle on the default application context, which I found out about by reading the Xt code. Isnt there a better way? Am I right, or am I full of ballyhoo on this one? Has anyone else encountered this problem? --Jacob
net@TUB.BITNET (Oliver Laumann) (03/29/89)
> When using multiple application contexts together with toolkits > which register resource converters, I noted an annoying problem. [...] The recently published ``official patch number 9'' fixes this problem. Regards, -- Oliver Laumann net@TUB.BITNET net@tub.UUCP