>> leaving the control key
>> free to be used for its normal purposes.
>
>Precisely!
>
>> If we were to allow an option to turn off the control key sequences listed
>> above, we have to write code at the lowest level to intercept all keyboard
>> strokes and decide what to do with the specific key before Windows itself
>> interprets the key. This isn't particularly difficult. We already have the
>> code in place.
>
>so...that doesn't affect the o verriding need to do the right thing!
>
>You're  high on  consistency...how consistent is it that *some* con trol
>chars are executed locally ^C, etc., and some are (oresumably)
>passed on (^M, ^Y, ^H)?

How about away to map the key stokes to functions in the program. That
way you could have it both ways?

Lane "Still using a Mac and stuck with reflections" Rollins