Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!xebra.Eng.Sun.COM!nannette From: nannette@xebra.Eng.Sun.COM (Nannette Simpson) Newsgroups: comp.windows.x Subject: Re: tvtwm, cm, and key bindings Message-ID: <1477@exodus.Eng.Sun.COM> Date: 18 Oct 90 01:00:34 GMT References: Sender: news@exodus.Eng.Sun.COM Distribution: comp Organization: Sun Microsystems, Mt. View, Ca. Lines: 56 In article hmp@frc2.frc.ri.cmu.edu (Henning Pangels) writes: > >I'm running tvtwm patchlevel 3 (on a sparcstation 1+), and I have some >of the "L" keys on the left side of the keyboard bound to f.scroll* >functions, to be executed no matter what (e.g. "L9" = : all :f.scrollleft) >On startup, everything's OK, but when I run the xview calendar manager >(cm), it screws up these bindings for when the cursor is over a window >such that they insert some generic code like ESC-[200z into the >window. >While I'm assuming cm is to blame for screwing around and/or not >cleaning up after itself (things stay messed up after cm exits), I'd >like to find a workaround or a way to reset the bindings correctly. >kbd_mode report unencoded events both before and after things get >screwed up, so that's no help. >Any ideas? > >-Henning > > > >-- >Henning Pangels Research Programmer Field Robotics Center >ARPAnet/Internet: hmp@frc2.frc.ri.cmu.edu Robotics Institute >(412) 268-7088 Carnegie-Mellon University Calendar Manager doesn't fiddle with the keymap. The only code in it that resembles what you're describing is: calendar->canvas = (Canvas) xv_create(calendar->frame, CANVAS, XV_WIDTH, WIN_EXTEND_TO_EDGE, CANVAS_FIXED_IMAGE, FALSE, CANVAS_RETAINED, FALSE, WIN_BIT_GRAVITY, ForgetGravity, CANVAS_NO_CLIPPING, TRUE, CANVAS_X_PAINT_WINDOW, TRUE, CANVAS_REPAINT_PROC, repaint_proc, CANVAS_RESIZE_PROC, resize_proc, OPENWIN_AUTO_CLEAR, TRUE, XV_X, 0, WIN_BELOW, calendar->panel, ------> WIN_CONSUME_PICK_EVENT, LOC_DRAG, ------> WIN_CONSUME_KBD_EVENTS, WIN_TOP_KEYS, WIN_UP_EVENTS, 0, WIN_CLIENT_DATA, calendar, 0); It consumes the DRAG event and the TOP_KEYS only; but this should in no way impact your keymap. You might have uncovered a generic interpose problem .... I'll look into it. -- Nannette Simpson Internet: nannette@Eng.Sun.COM Sun Microsystems, Inc. UUCP: ...!sun!nannette 2550 Garcia Ave. MS 1-40 Phone: (415) 336-2969 Mountain View, CA 94043