Can you use DoIdle() too much?

Valued Contributor
Valued Contributor

Can you use DoIdle() too much? For instance, if you have it in a function, and someone calls that function from a loop, would that be too much. I know that you shouldn't call Update() and Save() inside a loop because that would slow things down quite a bit but was wondering if DoIdle() had the same kind of overhead.

Thanks,

Terry Tyson
Software Automation Designer
2 REPLIES

Re: Can you use DoIdle() too much?

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

I would say that it depends on the scenario and code. If you just wrote a tight loop calling DoIdle(), then yes, I'd say that's bad. If you were processing a lot of documents and calling calling DoIdle() after Document.Close(), then I would say no, that's not a bad.

 

Breadcrumb for those reading this years later: See DoIdle() documentation for more details.

Jason Newell
Applications Architect
www.jasonnewell.net

Re: Can you use DoIdle() too much?

Valued Contributor
Valued Contributor

Ah, I see. That makes sense. Thanks Jason.

Terry Tyson
Software Automation Designer