Re: X extensions bug

Harri Pasanen (pa@tekla.fi)
16 Jun 1994 07:11:48 GMT

References: <PA.94Jun15151247@ds1.tekla.fi>
Date: Wed, 15 Jun 1994 13:10:45 GMT
X-Phone: +31 20 5924127 (work), +31 20 6225521 (home), +31 20 5924199 (fax)
Lines: 49

I think the following quote from email I received from Adrian Phillips
applies (I got it privately and still haven't found the time to
integrate all bug fixes to the X11 interface -- shame on me!).

| I checked out Wafe to see what it did with XtConvertAndStore,
| etc. and it uses XtConvert. I tried this and it worked. You can
| remove all those hacks I gave you as they are now replaced by a four
| line change in python_to_res [...]:
|
| out.size = 0;
| out.addr = 0;
| #ifdef SCREWED_CONVERTANDSTORE
| XtConvert(w, typename, &in, ctype, &out);
| if (!out.addr) {
| #else
| if (!XtConvertAndStore(w, typename, &in, ctype, &out)) {
| #endif
| err_setstr(Xt_Error, "can't convert resource type");
| return 0;
| }

Note that in fact you don't need the #ifdef -- the code using
XtConvert always works as far as I can tell. Let me know if this
helps or not.

--Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>

Yes, this indeed cures the problem.

Thanks,

Harri

--
------------------------------------------------------
Harri Pasanen		pa@tekla.fi