Comment 4 for bug 203763

Hm, I'm slightly concerned by this patch - there's the problem of return value and which event gets called first...and what happens if more than one event wants to handle ctrl-a...? bah, this is more of an architectural issue - any good ideas? I considered splitting the events into pure listeners which don't affect return value and at most one control-listener which determines what to return (and if defwindowproc should be called)....