Disabling the Debugger for Distribution

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Disabling the Debugger for Distribution

Darius Clarke
Hi All,

Is there a way to disable the debugger for a distribution version of a Squeak app.?
Something like hitting the abandon button before the debugger appears.
Thanks in advance.

- Darius


Reply | Threaded
Open this post in threaded view
|

Re: Disabling the Debugger for Distribution

Andreas.Raab
On 12/20/2010 11:20 PM, Darius Clarke wrote:
> Hi All,
>
> Is there a way to disable the debugger for a distribution version of a
> Squeak app.?
> Something like hitting the abandon button before the debugger appears.
> Thanks in advance.

Changing ToolSet default should do the trick. You can install a ToolSet
that just displays a polite information instead of opening a debugger.

Cheers,
   - Andreas

Reply | Threaded
Open this post in threaded view
|

Re: Disabling the Debugger for Distribution

Darius Clarke
Thank you.
I'll try subclassing the standard one.
Seems like some errors keep looping if they somehow remain unhandled... like 'does not understand'. DivideByZero doesn't have the problem. 

However, I have enough info to proceed for now. 
Thank you again. 

- Darius


Reply | Threaded
Open this post in threaded view
|

Re: Disabling the Debugger for Distribution

Darius Clarke
Thanks again for the pointer to ToolSet. I use my own new subclass tool set to override common errors like ZeroDivide. 

However, just returning w/o handling an error like #doesNotUnderstand: seems to leave the process in a loop trying to handle the unhandled error, freezing the UI (until interrupted). 


For now, I've changed Object>>doesNotUnderstand: to test if my toolset is the default and just return, but this has the effect of a continue rather than an abandon. 

Cheers,
Darius
________

On Mon, Dec 20, 2010 at 11:57 PM, Darius Clarke <[hidden email]> wrote:
Thank you.
I'll try subclassing the standard one.
Seems like some errors keep looping if they somehow remain unhandled... like 'does not understand'. DivideByZero doesn't have the problem. 

However, I have enough info to proceed for now. 
Thank you again. 

- Darius