madshi.net

Hey, great. It works! Now, the form is still there when gathering additional DB information.

Thanks!

Bye
Sneak-L8

Yes, that's the point. Is there a way to do my handling things before ProcessMessages is performed? Or you even issue an Application.ProcessMessages?

Yes, within Form.ShowModal (presumably when performing an internal Application.ProcessMessages)

With madExcept:
- TTGUserListEditDlg.Destroy
- TG (name of the project)

Without:
- TTGUserListEditDlg.Destroy
- TErrorForm.HandleException (initial class method of my exception handler)
- TTGMainForm.ApplException (method Application.OnException is assigned to)
- TG (name of the project)

Thanks. Testing by breakpointing Destroy was a good idea. But, unfortunately behaviour differs between Application.OnException and madExcept. Using OnException the form is freed after the error form was created. Using madExcept the form is freed before my registered ExceptionHandler is called. Is th...

Hi, the name of the topic sounds strange, but I don't know how to express it a better way :-) Before using madExcept, I had my own ExceptionHandler established in Application.OnException. When I created a new form or dialog and there was an error inside the constructor Create, I was able to find thi...