OpenDCL Forums

OpenDCL => Runtime/AutoLISP => Topic started by: Peter2 on March 31, 2014, 02:40:17 AM

Title: Silent work of DelayedInvoke?
Post by: Peter2 on March 31, 2014, 02:40:17 AM
I have  a self-recursive loop, based on Freds suggestion:

Code (autolisp) Select
(defun c:loop_for_jobs ()
    (to_something_in_this_code)
    (dcl_DelayedInvoke (* 1000 dwgr_waitseconds) "(c:loop_for_jobs)")
)


Everything is fine, but every "invoke" returns a
Code (autolisp) Select
Command: (c:loop_for_jobs)
Command: (c:loop_for_jobs)
Command: (c:loop_for_jobs)
Command: (c:loop_for_jobs)
Command: (c:loop_for_jobs)
...

For a long time loop now I run into a cosmetic problem with a full log-file  ...
Is there a way to run it in a "silent mode", to suppress the message?

Thanks

Peter
Title: Re: Silent work of DelayedInvoke?
Post by: Fred Tomke on March 31, 2014, 04:43:12 AM
Hi, Peter, since dcl_DelayedInvoke invokes a sendCommand you will ever see the command in the history and in the protocol.
I'm not sure if it is possible to use CommandFlags.NoHistory in OpenDCL (@Owen: what's your opinion?).
Regards, Fred
Title: Re: Silent work of DelayedInvoke?
Post by: owenwengerd on March 31, 2014, 07:19:31 AM
For now there is no way to suppress this from the log if you use (dcl-DelayedInvoke). If you're using OpenDCL 8.0, you may work around the problem by using a timer (i.e. dcl-Form-StartTimer) instead.
Title: Re: Silent work of DelayedInvoke?
Post by: Peter2 on March 31, 2014, 07:22:47 AM
Thanks to both of you

at the moment I will stay with version 7. As said above, it is not dramatic, more cosmetic ...