|
That's true. I was doing Copy/Paste with Windows accelerator keys. If I don't use accelerator keys, but instead use the keyboard handler that I wrote for the other control keys I could do what you describe and have copy/paste work with Ctrl-V and Ctrl-C. (I'm already doing this for all of the other control keys, why didn't I think of it in conjunction with the copy/paste functions?!) But, in the unix version, ctrl-c is SysReq. I'm not sure that I want the default key sequences to vary between OSes. But, I can certainly make Ctrl-C and Ctrl-V an option that can be enabled. On Fri, 29 Mar 2002, Douglas Handy wrote: > > Seems to me the solution is to detect the difference between a press and > release of Ctrl with no modifiers, vs getting other key down/up scan > codes while Ctrl is depressed. > > IOW, for the Ctrl key, don't act on the key down event. Set a flag and don't > act until the key up event. Then only perform the assigned "Ctrl" action when > no other key events have occured in the interim. That may have the side >effect > of not allowing key repeats for Ctrl, but I can live without repeating Error > Resets. :) While repeating Field Exits have more potential, IMHO, I'd gladly > trade that for the ability to define an action for the key when used alone, > which does not occur when used as a modifier to other keys. > > Doug
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.