Another point is that the check wether you have an event-based VM is  
done only when you enter a Morphic project.  If you have an open  
project and you switch the handling in the VM (events/sensors), this  
will go unnoticed, so you can have the InputSensor generating  
synthetic events from sensor-data it synthesized from events coming  
from the VM.  These are then taken into Morphic where you once again  
have mouse-state data being generated, as well as mouse-moved events.

And yes, I have lost track of the layers here ;-)

Marcel

> From: Karl Ramberg <karl.ramberg at chello.se>

> The class comment on HandMorph>>processEvent
> "
> Process user input events from the local input devices.
> 	An interesting problem. Morphic is always supposed to run in  
an event
> driven environment but for now it is possible that a Morphic window is 
> run from MVC so that we have to synthesize events in the sensor. That's 
> quite a bit of a problem because it means that we'll get endless mouse 
> events. To compensate for this, EventSensor will always return keyboard 
> events first if synthesized so if we're running into a mouse event AND 
> Sensor doesn't have an event queue we can safely break out of the event 
> processing loop. See also EventSensor>>nextEventSynthesized."
>
> Now that morphic is default start up project, maybe there is time to  
> change some of this ?