How to detect Quiescent in R14.01

[Martin Hutton]

The Automation implementation in AutoCAD R14.01 gives the
"automation object not resonding/switch to/ignore/retry" message
while it is processing.

I noticed that R2000 has an "IsQuiescent" property - how can I
implement this in R14.01 - I'm currently using the paired
started-ended/cancelled events from the Reactors in AcVBExt to
track my own quiescent state (so I wait until idle before invoking
methods/properties) on the object.

Is there a better way?

Thanks

Martin

[Jorge Lopez]

Martin,

In R14.01 this will not be easy. Problem is any call you make to check for
quiescence will result in the dialog about being busy. The only thing I can
think of is to disable the message filter completely then checking the
CMDACTIVE variable. This won't be as accurate as IsQuiescent() in A2000 but
I can't think of anything better. This problem was recognized after R14.01
and that is why the AcadState object was introduced into A2000.

Cheers,

Jorge

Martin Hutton <hut...@basit.com> wrote in message
news:7td379$52...@adesknews2.autodesk.com...

[Martin Hutton]

Jorge:

Thanks - it's good to see that you are still active on this NG, lending your
AutoCAD expertise to us lesser mortals ;-)

I've no idea what you mean when you said

"disable the message filter completely"

I can't stop the "Component busy..." dialog with "On Error....". I do know
how
to get the CMDACTIVE variable.

I think if I can reliably get AcVBExt running over *ALL* installations (see
below)
and use the events from the reactors, I should be able to make a pretty
good,
cross-process event intensive, approximation to Quiescent.

BTW, I have an installation of AutoCAD R14.01 where the
AcVBExt refuses to load. Get the error object below.
Any ideas?
Err.Number = 0x800405E8 (error 1512 with Automation stuff)
Err.Source = AutoCAD
Err.Description = Problem loading app. HRESULT= 0x80040154
(Error 340 w/ Automation)

Thanks

Martin

Jorge Lopez wrote in message <7td47a$53...@adesknews2.autodesk.com>...

>Martin,
>
>In R14.01 this will not be easy. Problem is any call you make to check for
>quiescence will result in the dialog about being busy. The only thing I can
>think of is to disable the message filter completely then checking the
>CMDACTIVE variable. This won't be as accurate as IsQuiescent() in A2000 but
>I can't think of anything better. This problem was recognized after R14.01
>and that is why the AcadState object was introduced into A2000.
>
>Cheers
>
>

[Stuart Nathan]

if you have an external app (not a dll) in VB then use the app.oleserver
stuff