> I see the same ( 1-4 ) on Windows, but I also see it on 3.6. Sometimes
> something strange happens, and from there on, a morphic project ( only
> that single project ) seems to delay event related things endlessly, e.
> g. buttons which have an action for a 1 sec hold registered, are not
> reacting to std clicks anymore, they always think I pressed them 1 sec
> :)

Looks like a weird combination of things. First of all I believe for some
reason your system has "dropped" Sensor's event queue (this is possible - it
happens for example under certain error conditions - check out "Sensor
eventQueue" to see if it's nil). When that happens, Sensor's ioProcess will
start to "throw away" events it receives from the VM (since it doesn't have
an event queue any longer it's the only reasonable thing to do :-). Lastly,
if you look at, e.g., SimpleButtonMorph>>mouseDown: you will see a delay
which is triggered if the button action does not happen on #mouseDown.

So what probably happens is somewhere along the lines of:
* you mouse down on the close button
* the delay in SimpleButtonMorph is activated
    * you release the mouse
    * the event is thrown away by ioProcess
    * you move the mouse to a new position
    * the event(s) get thrown away as well
* ages later, the delay ends
* hand morph asks for the new event from Sensor
* Sensor synthesizes a mouse up but because it doesn't have the (buffered)
position of the mouse up event it uses the current one
* the mouse up happens in the wrong place.

Interesting that it works at all. How to fix it? Either make sure Sensor
*does* have an event queue (Sensor eventQueue: SharedQueue new) or just try
the recent change set I sent out for dealing with the ioProcess.

Cheers,
  - Andreas