On Mon, 07 Sep 1998 15:26:26 +0200, Stefan Matthias Aust wrote:

>A system event dispatcher will retrieve these VM events, process and
>dispatch them. It'll listen to all movement events, determining the active
>window widget, sending a "mouse entered" to that widget. It's now the
>responsibilty of the window widget to react.  The window might register
>itself as the active window. Key events are always forwared to the active
>window (if there's one). The window will then forward the key to the widget
>which currently has the focus.
>
>This has to be detailed, but it seems to be strait forward.
>
>But how to deal with concurrent processes? Any ideas?

I think that for each windowing application there should be a separate
process and event handler.  Dialogs generated by an application would
use the app's process and event handler.  This approach would make each
application look like a standard OS application.  One immediate advantage
would be that if an application hangs the entire image will not hang.

Terry Raymond
Crafted Smalltalk
(401) 846-6573    http://www.craftedsmalltalk.com