DCL error and lockup in R2004

I never see any mention of this problem, so I wonder if I'm living in an alternate universe? I used to routinely get full-on lock-up when my imperfect lisp code made an error while a dcl dialog was up, until I set my *error* to do this first thing:

(if (= 8 (logand 8 (getvar "cmdactive")))
(done_dialog 0)
)

Worked like a charm, until I started using R2004. I even tried (term_dialog) instead of (done_dialog 0). Anybody figure out a solution, other than perfect code the first time, for R2004?

Or does nobody else ever have the problem?

 

It's now how it works, it's how it's executed.

Excuse my ignorance, but what exactly are you doing in the dialog?
--

AUTODESK
Authorized Developer
www.Cadentity.com
MASi

alternate universe? I used to routinely get full-on lock-up when my
imperfect lisp code made an error while a dcl dialog was up, until I set my
*error* to do this first thing:

(term_dialog) instead of (done_dialog 0). Anybody figure out a solution,
other than perfect code the first time, for R2004?

 

Well, my face is a little red right now. It's not that I don't still have the problem, but I went ahead and did some testing in a naked environment, with no other customization and no *error*, with a test function that does a divde by zero at the press of a button. The lock-up does not occur.

It must be something in my fancy error handler.

Thanks anyway.