On Wed, 7 Jul 1999 20:57:32 EDT ChrisRath at aol.com wrote: 
>Anyhow, enuf complaining. I was wondering if someone could point what classes 
>would need to be looked at, in order to intercept these characters for the 
>workspace and browser?  I've tried to track the code down from the workspace 
>and up from the raw keyboard handling, but I have not isolated where the 
>functionality meets.

Chris,

In Morphic, the normal path for reporting key strokes is (taa daa!) #keyStroke:. Looking at TextMorph>>keyStroke: leads us to ParagraphEditor>>readKeyboard and from there to ParagraphEditor>>dispatchOnCharacter:with:. This clearly decides whether characters represent special actions or normal characters. Looks like a good place to concentrate.

Cheers,
Bob