Hi Raza, 

No, programming errors don't, in general, make sense to end-users. Remedial measures could be taken if the error is related to end-user actions. For example, feeding unexpected content (not only by Pier, but also by its plug-ins). But in all cases, for end-users it seems better to have an application that keeps responsive, eventually with meaningful error messages, instead of a *wall back* window.


I agree that you don't want to display walk-back errors to end users though is there a problem changing WAWalkbackErrorHandler to something that makes more sense to the end user?

Nick