onError method question

Classic Servoy
1

Hello,

I am using a global onError method to nicely inform the user of a problem in case an error occurs. While I like this feature, I have the impression that it makes solving the problem more difficult.

  1. I don’t seem to be able to get the stack trace of the error. So I don’t really see which method/line caused it
  2. The error doesn’t get written to the client trace either

Is there something I am missing? If not, could a getStacktrace be added to the exception node?

Thanks
Patrick