"It's either all or nothing" - A2k4

Guru dudes:

As I work my way through the transition from AutoLisp to Vlisp ActiveX,
there's an important issue I need to consider. Can I mix AutoLisp functions
with Vlisp/ActiveX stuff? And related, how does A2k4 impact this question?

I've read the thread, quoted above, by R. Robert Bell dated 10/8/2001. Also
other threads related to the same topic, i.e., the eLock error in A2k2 and
previous A2kx versions. I have Stephan Koster's latest PreventLockError.arx
and I've run Stephan's "test" functions to confirm this mess is a problem
while running A2k2 without Stephan's ARX.

I think Jason said the eLock error does not occur under A2k4. So this leads
to my main question: what's the current read on all these issues? If indeed
the eLock error is fixed in A2k4, does that change the "all or nothing"
approach?

Thanks
Joe Burke

 

This problem appears to be greatly reduced. Mind you, I don't have TuFer in
production yet, but under my compatibility testing it is far better than the
earlier A2k series.


--
R. Robert Bell, MCSE
www.AcadX.com


| Guru dudes:
|
| As I work my way through the transition from AutoLisp to Vlisp ActiveX,
| there's an important issue I need to consider. Can I mix AutoLisp
functions
| with Vlisp/ActiveX stuff? And related, how does A2k4 impact this question?
|
| I've read the thread, quoted above, by R. Robert Bell dated 10/8/2001.
Also
| other threads related to the same topic, i.e., the eLock error in A2k2 and
| previous A2kx versions. I have Stephan Koster's latest
PreventLockError.arx
| and I've run Stephan's "test" functions to confirm this mess is a problem
| while running A2k2 without Stephan's ARX.
|
| I think Jason said the eLock error does not occur under A2k4. So this
leads
| to my main question: what's the current read on all these issues? If
indeed
| the eLock error is fixed in A2k4, does that change the "all or nothing"
| approach?
|
| Thanks
| Joe Burke
|
|

 

Thanks guys. That's good news.

Joe