Re: [Pyobjc-dev] Segmentation Fault on Jaguar
Brought to you by:
ronaldoussoren
From: Bob I. <bo...@re...> - 2004-09-30 20:43:11
|
On Sep 30, 2004, at 4:07 PM, Just van Rossum wrote: > Bob Ippolito wrote: > >>> Why is installInterrupt True by default? Most regular AppKit apps >>> should not be interruptable that way. >> >> Yeah they should, or at least they do if they're written in ObjC. > > They should? Why? You wouldn't want cntrl-C to interrupt an arbitrary > event handler. Or am I misunderstanding what installInterrupt does? Ctrl-C interrupts any process that doesn't explicitly replace the default signal handler for SIGINT. AppKit does not. Try it: /Applications/TextEdit.app/Contents/MacOS/TextEdit (press ^C) TextEdit dies. Now try it with TinyTinyTextEdit (modified to use installInterrupt=False) `pwd`/build/TinyTinyEdit.app/Contents/MacOS/TinyTinyEdit (press ^C) ... wait... wait... nothing happens. Ok, let's start using it.. Type some text. Click "save as" choose a filename. Click save. BOOM, dialog that says: An unexpected error has occurred (KeyboardInterrupt) Python bytecode finally got the chance to execute when the file was to be saved. Is this correct behavior? Hell no. -bob |