After reading some of the Uninterruptable thread I started playing with the
following code:

[[true] whileTrue: 
	[|halt| 
	halt _ Sensor shiftPressed.
	halt ifTrue: [self halt.].
	Transcript show: halt; cr.
	(Delay forSeconds: 1) wait]] forkAt: 7

If I doit and then depress the shift key nothing happens, except the
transcript continues to print false! Then moving (or clicking) the mouse
while continuing to hold the shift key down will result in a halt within a
second. Is this the expected behaviour? 

Joerg

> -----Original Message-----
> From: Ned Konz [mailto:ned at bike-nomad.com]
> Sent: March 7, 2001 11:56 PM
> To: squeak at cs.uiuc.edu
> Subject: Re: Uninterruptable Squeak
> 
> 
> On Wednesday 07 March 2001 23:43, Doug Way wrote:
> 
> > Or maybe a quicker (no doubt uglier) hack for the Process 
> Browser would be
> > to optionally turn on CPU metering, which would be a 
> special high priority
> > (6 or 7?) process which would sample all lower level 
> processes and report
> > usage. (?)  This would probably kill performance, but might be an
> > interesting debugging tool to turn on temporarily when needed.
> 
> I did it with a highest-priority (8) process every 10 msec, 
> which isn't too 
> noticeable on my machine. I haven't integrated it into the 
> ProcessBrowser yet 
> since I'm busy on my Connectors stuff still. But the guts of 
> it work and dump 
> to the Transcript (see my message of about 20 minutes ago).
> 
> All I'm doing is tallying into a Bag (whose contents have 
> been replaced by a 
> higher-performance IdentitySet). This would be available from 
> the UI task for 
> reading (I think), so it could be added to the ProcessBrowser.
> 
> Would you have such a thing attached to the ProcessBrowser?
> 
> -- 
> Ned Konz
> currently: Stanwood, WA
> email:     ned at bike-nomad.com
> homepage:  http://bike-nomad.com
>