Path: utzoo!attcan!uunet!wuarchive!decwrl!ucbvax!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph Swick)
Newsgroups: comp.windows.x
Subject: Re: problem with xtex fonts
Message-ID: <9008151517.AA02255@lyre.MIT.EDU>
Date: 15 Aug 90 15:17:18 GMT
References: <24632@boulder.Colorado.EDU>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 36


    ... deletes a widget tree in which
    an InstallAccelerators has been done.

    The core dump traces back to a call to RemoveAccelerators or somesuch;
    ...allegedly, this only occurs with X fixes 13,14
    installed.

Right.  This is a recently-discovered problem with fixes 13,14.

    Does some Wise Person know if these problems have any semantic affect
    on programs?

(Not that I necessarily claim to qualify, but...:-)
The patch changed the manner in which translation tables
containing installed accelerators are stored.  The bug
is triggered when multiple accelerator tables are installed
on the same destination widget and any of the accelerator
source widgets are subsequently destroyed.

One additional side-effect of {13,14} is that repeated
calls to XtGetValues for XtNtranslations will not necessarily
return the same value each time.  It's not clear from the
specification whether or not applications should be surprised
by this behavior.  I'd be happy to discuss this separately
if there is interest.

At present there is no work-around for the accelerator source
widget destruction bug.  Fix 15 is in the works.  Sorry for
the aggravation; we were hustling to get things out that various
people were depending upon and made too many testing shortcuts.
(It was supposedly tested by 3 independent groups, too!:-(
You might want to temporarily back out {13,14} until 15 is
published.

-Ralph