Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!kth!sunic!ericom!erix.ericsson.se!per From: per@erix.ericsson.se (Per Hedeland) Newsgroups: comp.windows.x Subject: Strangeness with keypress sequence in translation table Message-ID: <2084@erix.ericsson.se> Date: 17 Jul 89 13:20:47 GMT Reply-To: per@erix.ericsson.se (Per Hedeland) Organization: Ellemtel Utvecklings AB, Stockholm, Sweden Lines: 40 Please excuse me if this has come up before, or I just don't understand how translations works (but in either case tell me about it:-). I tried to add some translations to the Text Widget, in particular I wanted sequences like Escape,f to have the same action as Meta-f. For simplicity, let's assume that the original translation table was just MetaF: forward-word() \n\ : insert-char() To this I added (with XtOverrideTranslations) my Escape,F: forward-word() and it worked fine, *but* Meta-f and unmodified f *stopped* working, i.e. they were effectively ignored! After much experimenting, I found that I had to use all of Escape,~MetaF: forward-word() \n\ ~MetaF: insert-char() for XtOverrideTranslations in order to achieve the desired effect. Is this the way it is supposed to work, or a bug? If the former, could someone please explain the logic of the translation manager to me? - Obviously, I think that the ~Meta and the second translation are redundant. N.b. I got similar results when replacing the translation table rather than overriding, i.e. the mininum table I found to work in this case was Escape,~MetaF: forward-word() \n\ MetaF: forward-word() \n\ ~MetaF: insert-char() \n\ : insert-char() Thanks In Advance --Per Hedeland per@erix.ericsson.se or per%erix.ericsson.se@uunet.uu.net or ...uunet!erix.ericsson.se!per