Re: [Newbies] User Interrupt window

Okay, such process-switching code can be tricky. If you keep that suspended process around for a while the Transcript's semaphore will block other semaphore uses. So, try this:

Am 15.12.2017 09:29:10 schrieb Marcel Taeumel <[hidden email]>:

...hmmm... this test seems to lock the Transcript's input semaphore. So, after CMD+Dot via MyToolSet, any calls to "Transcript show:" will freeze. Interesting.

Any ideas?

Best,

Marcel

Am 15.12.2017 09:22:52 schrieb Marcel Taeumel <[hidden email]>:

Hi Jim,

well, the Debugger takes care of re-spawning a new UI process in case the interrupted one was the UI process. :-) You should do that, too:

interrupt: process label: string

"ToolSet register: self; default: self"

Project current spawnNewProcessIfThisIsUI: process.

self inform: string.

Best,

Marcel

Am 14.12.2017 17:30:06 schrieb obrienj <[hidden email]>:

Hi Marcel,

I made MyToolSet, a subclass of StandardToolSet, and added a copy of #interrupt:label to it.

I next created HaltExperiment as an Object subclass and added this simple, infinite loop method:

infiniteLoop

| x |

ToolSet register:  MyToolSet.

ToolSet default:  MyToolSet.

Transcript clear. x := 0.

[x >= 0] whileTrue: [x := x + 1. Transcript show: 'x = ', x; cr.].

As a test, I commented out the code in StandardToolSet’s #interrupt:label:, which stops the User Interrupt window from appearing but also causes Squeak to freeze after typing the interrupt key. Unfortunately, running HaltExperiment new infiniteLoop didn't restore the appearance of the User Interrupt window or stop Squeak from freezing even though MyToolSet has a complete copy of #interrupt:label:.

What am I doing wrong? How do I implement MyToolSet's #interrupt:label so that a dialog window appears with its own message to the user when infiniteLoop is interrupted?

Thanks,

Jim

-------- Original Message --------

Subject: Re: [Newbies] User Interrupt window

Local Time: December 9, 2017 9:54 AM

UTC Time: December 9, 2017 5:54 PM

From: [hidden email]

To: obrienj <[hidden email]>, [hidden email]

Hi, there.

1) Subclass StandardToolSet.

2) There, implement #interrupt:label: as you want it.

3) Set your new tool set via "ToolSet register: MyToolSet" and "ToolSet default: MyToolSet".

Note that ToolSet is an AppRegistry and hence a wrapper whereas StandardToolSet is an actual tool set. :-) Other app registries include WebBrowser and SoundService.

The user interrupt is not implemented with exceptions but a watchdog process and a special semaphore. See EventSensor >> #userInterruptWatcher for more information.

Best,

Marcel

Am 09.12.2017 18:09:51 schrieb obrienj <[hidden email]>:

_______________________________________________ Beginners mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/beginners

Is there a way to intercept the 'User Interrupt'  window that pops up when the user types the interrupt key and replace it with a customized dialog window? I've used on: do: to intercept Error messages but can't seem to do the same with EventSensor messages.