From: Venn Ghavral 
@Date: Tue, 11 Feb 2003 22:43:00 GMT
@Sender: semware-owner{at}sawasdi.apana.org.au



  Jan A. Nauta 
> I know of the new keybinding type:  that I could
> use in this instance. But I have a lot of AFTER-hotkeybinding-
> procs that depend on checking the Shiftkey status.

 Since  and  are different keys, you can't
 make  do things based on the Shift state, since by
 definition it only works unshifted.  You could make it work
 differently based on the Scroll State, say, but not Shift.
 I do some things differently (in 2.50e) based on NumLock:

          if GetKeyFlags() & _num_lock_depressed_
                     EndLine() else InsertText("1") endif
  if GetKeyFlags() & _num_lock_depressed_
                     Right() else InsertText("6") endif

 and so on.  But basically, it seems you're used to pressing
  and having one thing happen, and  and
 having another happen.  So just use those keybindings for
 the procs.  There's no need at all to check Shift within the
 procs, since the key assignments have it built in, at zero
 computational cost.


                                             
--
TSEPro mailing list



---
[sawasdi.apana.org.au] (3:800/846.13)