rusin@ux1.lbl.gov (David J Rusin) (06/14/89)
Recent questions here about the keyboard lead me to ask this one. I have some
TSR's I like to keep in the background, but their hot key combinations are
sometimes needed in applications; I need to circumvent this collision. I am
loathe to try to debug the TSR codes to find out where the hot key is defined.
Is there a way to redefine the keyboard in such a way that a conversion is
made applicable only to programs installed before/after the conversion? Better,
is there a TSR whose hot keys I can define and whose only job is to send the
activation request to the TSR's I specify? (That is, this TSR would allow me to
inform it that when I type alt-1 it should tell my backscroll program that I
have typed cntrl-space, which cues it to show me the previous screen,
without telling my database program that I haved typed a cntrl-space, which
it uses as a cue to change data fields.)
All leads appreciated. Thanks
Dave Rusin, rusin@ux1.lbl.gov, or {...}!ucbvax!ux1!rusin