On 28 November 2011 23:36, Sean P. DeNigris <sean@clipperadams.com> wrote:
Igor Stasenko wrote
the default behavior of it, when any interaction with user is requested, it signals ErrorNonInteractive error, and default action for this error is to print stack trace to log file and leave to OS. signaling any other unhandled error leading to opening a debugger window, which is considered a user interaction request, and consequently bails out to OS as well by signaling ErrorNonInteractive.
Igor, I added your response to the class comment, but could you expand the above paragraph (maybe some periods, lol). I don't understand it.
here what happens: [ some error signal ] -> attempt to open debugger -> [signal ErrorNonInteractive] -> leave to OS
-- View this message in context: http://forum.world.st/Problem-with-NonInteractiveUIManager-tp4115412p4116981... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Best regards, Igor Stasenko.