This was the first issue that popped up when I put a halt in eventMillisecondClock.

I see a number of other senders of eventMillisecondClock that handle the case
of an event buffer with time stamp of 0. Is that even possible?

Dave

On Tue, Sep 15, 2020 at 08:04:34PM +0000, commits at source.squeak.org wrote:
> David T. Lewis uploaded a new version of Morphic to project The Trunk:
> http://source.squeak.org/trunk/Morphic-dtl.1680.mcz
> 
> ==================== Summary ====================
> 
> Name: Morphic-dtl.1680
> Author: dtl
> Time: 15 September 2020, 4:04:29.45022 pm
> UUID: ecb7a7fd-061d-44e0-802f-b08ac8ae9778
> Ancestors: Morphic-mt.1679
> 
> For MouseEvent>>asMouseMove retain the original event timeStamp. Removes an unnecessary dependency on eventMillisecondClock.
> 
> =============== Diff against Morphic-mt.1679 ===============
> 
> Item was changed:
>   ----- Method: MouseEvent>>asMouseMove (in category 'converting') -----
>   asMouseMove
>   	"Convert the receiver into a mouse move"
> + 	^MouseMoveEvent new setType: #mouseMove startPoint: position endPoint: position trail: {position. position} buttons: buttons hand: source stamp: timeStamp!
> - 	^MouseMoveEvent new setType: #mouseMove startPoint: position endPoint: position trail: {position. position} buttons: buttons hand: source stamp: Time eventMillisecondClock!
> 
>