Ouch. Whatever the problem is, I'm pretty sure it is my fault.

I did the updates on a Linux platform. But I do not see anything at
all in the original InputSensor or EventSensor that should be platform
dependent.

The updates for InputSensor removal require class initialize methods.
The most likely explanation is that I screwed something up in the update
maps when I moved these changes from inbox to trunk.

The updates involved in InputSensor removal are Kernel-dtl.981, Kernel-dtl.982, 
Kernel-dtl.983, Kernel-dtl.984, and Kernel-dtl.985.

The related update maps are update-dtl.346.mcm, update-dtl.347.mcm, and
update-dtl.348.mcm.

My apologies for the disruption, and I hope to have fix soon. Meanwhile
if someone can confirm the problem on a non-Windows platform, I would
appreciate it (I really do not think it is anything related to Windows
but I could be wrong).

Dave


On Wed, Feb 03, 2016 at 10:04:29PM +0100, karl ramberg wrote:
> I downloaded latest trunk and it has the same problem on Windows
> 
> Best,
> Karl
> 
> Best,
> Karl
> 
> On Wed, Feb 3, 2016 at 9:40 PM, Chris Cunningham <cunningham.cb at gmail.com>
> wrote:
> 
> > Right.  CMD+. brings up debug windows - which you can't interact with
> > because the mouse doesn't work.
> > No ideas - also on a Windows machine. I just picked up the previous image
> > (luckily saved off just before doing an update - not something I normally
> > do!)
> >
> > -cbc
> >
> > On Wed, Feb 3, 2016 at 11:58 AM, marcel.taeumel <Marcel.Taeumel at hpi.de>
> > wrote:
> >
> >> Hi, there!
> >>
> >> I cannot use mouse or keyboard anymore after saving and re-opening the
> >> image. CMD+. works but this is implemented via a semaphore.
> >>
> >> Any ideas? I am on a Windows machine.
> >>
> >> Best,
> >> Marcel
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://forum.world.st/Latest-Changes-in-InputSensor-EventSensor-lock-up-image-after-save-restart-tp4875654.html
> >> Sent from the Squeak - Dev mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> >
> >

>