It looks as though using signalException:, and a UserInterrupt notification whose defaultAction is to open the debugger will do the trick ... An exception handler on the stack for UserInterrupt can intercept the interrupt and do something different than opening a debugger.
I've attached two fileIns with an example implementation...a quick review by a knowledgeable soul would be appreciated (not much code involved at all). If there aren't any other alternatives and this approach is deemed to be acceptable, I can go through the standard process and submit a bug/bugfix (bullet-proofing the code a bit as well). Dale ----- "Dale Henrichs" <[email protected]> wrote: | For the GLASS GemTools client, I would like to intercept Alt-. and | instead of opening a debugger, I would like to send an interrupt to | the GemStone process. | | In Squeak and earlier variants of Pharo, it was possible to replace | the interruptSemaphore with one of our own while we were waiting and | it worked well enough. | | With the new structure of InputSensor and friends it doesn't appear to | be possible to hack into the event handling system for user | interrupts. | | The class UserInterruptHandler is tantalizingly close, however, there | is no obvious way to insinuate myself as an interested party....It's | pretty much hard-wired to open a debugger on the interrupted | process.... | | There are probably several ways to allow for the user interrupt to be | intercepted: | | - use a dynamic variable | - use a process local | | Both techniques have the advantage of being process specific... | | On the other hand if it is easier/preferable to use Ctl-ALT-. then | that would work for me. | | Thanks in advance, | | Dale | | _______________________________________________ | Pharo-project mailing list | [email protected] | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
UserInterrupt.st
Description: Binary data
UserInterruptHandler-handleUserInterrupt.st
Description: Binary data
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
